You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
minor #3010 Configure Vitest for unit and browser tests (Kocal)
This PR was merged into the 2.x branch.
Discussion
----------
Configure Vitest for unit and browser tests
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no <!-- please update src/**/CHANGELOG.md files -->
| Docs? | no <!-- required for new features -->
| Issues | Fix#3008 <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License | MIT
<!--
Replace this notice by a description of your feature/bugfix.
This will help reviewers and should be a good start for the documentation.
Additionally (see https://symfony.com/releases):
- Always add tests and ensure they pass.
- For new features, provide some code snippets to help understand usage.
- Features and deprecations must be submitted against branch main.
- Update/add documentation as required (we can help!)
- Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
- Never break backward compatibility (see https://symfony.com/bc).
-->
Moved all existing assets unit tests under `assets/test/unit`, in order to introduce `assets/test/browser` for pure E2E tests using a real Symfony app (in a future PR) and real browsers.
I slightly improved the `test_package.sh` for peerDependencies/importmap versions checks.
Next steps are [#3009](#3009)
Commits
-------
01bea65 Configure Vitest for unit and browser tests (use `@puppeteer`/browsers and webdriverio)
0 commit comments