What kind of change does this PR introduce? (check at least one)
[x] Bugfix
[ ] New test runner
[ ] Documentation
[x] Feature
[ ] Code style update
[x] Refactor
[ ] Build-related changes
[ ] Other, please describe:
Does this PR introduce a breaking change? (check one)
[x] Yes
[ ] No
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
[x] It's submitted to the dev branch and not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] It's been tested on Windows
[x] It's been tested on Linux
[ ] It's been tested on MacOS
[x] Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.
If adding a new feature, the PR's description includes:
[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)
Other information:
I plan to merge and release as beta next week
Code updates into test-app-* folders isn't that important, migration guide and files into packages/unit-jest are
I released the new version under beta tag, but I don't plan to advertise it before next week, any help to catch early bugs is appreciated
e.g. apparently I broke JS test files with ESM syntax somehow 👀
Run quasar ext add @quasar/testing-unit-jest@beta and yarn test:unit to initialise and run tests in an existing project
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch and not themasterbranchfix: #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: I plan to merge and release as beta next week Code updates into test-app-* folders isn't that important, migration guide and files into packages/unit-jest are
I released the new version under beta tag, but I don't plan to advertise it before next week, any help to catch early bugs is appreciated e.g. apparently I broke JS test files with ESM syntax somehow 👀
Run
quasar ext add @quasar/testing-unit-jest@betaandyarn test:unitto initialise and run tests in an existing project