Releases: quasarframework/quasar-testing
@quasar/testing v2.2.0
THIS PACKAGE HAS BEEN DEPRECATED
See here the deprecation notice, reasons behind it and how to migrate away from this package
@quasar/testing-e2e-cypress v5.1.1
We had to do an emergency release to fix a problem with latest @quasar/app-vite
and this resulted in a new feature from v5.2.0 dripping into v5.1.1
Unluckily, since alphas for v5.2.0 were already out, reverting that change now may cause even more problems
We're sorry for the inconvenient, we usually strictly adhere to semver rules
What's Changed
- [BREAKING CHANGE] Cypress AE now enforces the usage of port 8080 for Cypress tests for all platforms, build targets and bundlers (both Webpack and Vite). It previously varied for each combination and Vite-based projects used "9000" port by default.
Suggested migration path
Update test:e2e
and test:e2e:ci
scripts to use port "8080"
OR
Upgrade to latest v5.2.x which supports specifying the port to which the app will be forced when running e2e tests
@quasar/testing-unit-vitest v0.3.0
This AE is in alpha phase, let us know if you bump in any problem
Install it by running quasar ext add @quasar/testing-unit-vitest
Check out the docs
What's Changed
Full Changelog: unit-vitest-v0.2.1...unit-vitest-v0.3.0
@quasar/testing-unit-vitest v0.2.1
This AE is in alpha phase, let us know if you bump in any problem
Install it by running quasar ext add @quasar/testing-unit-vitest
Check out the docs
What's Changed
- chore: updated deps and peerDeps
- refactor(vitest): rename installQuasar in installQuasarPlugin
@quasar/testing-e2e-cypress v5.1.0
@quasar/testing v2.1.0
New Cypress AE v5 is installed when Cypress testing is selected into the harness manager prompts
The option to install Cypress AE v4 has been removed
@quasar/testing-e2e-cypress v5.0.0
Package promoted to stable, there're no changes from previous beta release
Install it by running quasar ext add @quasar/testing-e2e-cypress
Check out the updated docs and the related migration guide
@quasar/testing-e2e-cypress v5.0.0 beta 11 - Cypress 12 support
We switched to Cypress 12, which is a breaking change (see their migration guide).
We tested against Cypress 11 too, but we won't test against that Cypress version for future releases.
We are sorry for continuously bumping Cypress peer dependency during the beta phase, but Cypress team released 3 major versions in a 6 months time span and we cannot afford to maintain too many major versions of this AE.
Full Changelog: e2e-cypress-v5.0.0-beta.10...e2e-cypress-v5.0.0-beta.11
@quasar/testing-e2e-cypress v5.0.0 beta 10
What's Changed
- fix(cypress): do not override coverage exclude by @yusufkandemir in #304
Full Changelog: e2e-cypress-v5.0.0-beta.9...e2e-cypress-v5.0.0-beta.10
@quasar/testing-e2e-cypress v5.0.0 beta 9 - Cypress 11 support and fixes
We skipped some release notes, this one packs changes from all beta releases since beta.1
In beta.7 we switched to Cypress 11, which is breaking change but won't affect the vast majority of the projects.
It avoids us to release a new major version right after releasing v5 as stable
There's an outstanding issue with code coverage in Vite projects due to an upstream dependency, we probably won't go stable until that one is solved
What's Changed
- feat(cypress): allow code coverage on builds by @yusufkandemir in #281
- fix(cypress): restore code coverage capability with dev server by @cailloumajor in #300
- fix(cypress): import styles in correct order by @devidw in #303
- fix(cypress): fix support file extension in JS config
- fix(cypress): use CJS syntax for JS config file
- fix(cypress): fix some test files naming and extension
- chore(cypress): bump Cypress to v11
- feat(cypress): autodetect Cypress version from peerDependencies
- docs(cypress): add instructions for projects without a CSS preprocessor
New Contributors
- @yusufkandemir made their first contribution in #281
- @cailloumajor made their first contribution in #300
Full Changelog: e2e-cypress-v5.0.0-beta.1...e2e-cypress-v5.0.0-beta.9