We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating vitest to version 0.25.7 breaks unit tests for Svelte-based website.
pnpm
yarn
npm
pnpm test:unit
yarn test:unit
npm run test:unit
vitest
Expected behavior: In both cases, the unit test succeeds.
Actual behavior: The unit tests succeeds only with vitest@0.25.6. It fails with vitest@0.25.7.
Later versions of Vitest: The test fails with 0.28.4 (latest) as well.
Notable changes from 0.25.6 to 0.25.7:
System: OS: Linux 6.1 Arch Linux CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics Memory: 1.67 GB / 15.02 GB Container: Yes Shell: 5.1.16 - /bin/bash Binaries: Node: 18.13.0 - /usr/bin/node Yarn: 1.22.19 - /usr/bin/yarn npm: 8.19.2 - /usr/bin/npm Browsers: Chromium: 110.0.5481.77 npmPackages: @testing-library/dom: ^8.20.0 => 8.20.0 @testing-library/svelte: ^3.2.2 => 3.2.2 vite: ^4.0.0 => 4.1.1 vitest: 0.25.7 => 0.25.7
The text was updated successfully, but these errors were encountered:
Checked for duplicates before beginning to write this issue, none found. Checked again after posting, found #2834 as a potential dupe.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Updating vitest to version 0.25.7 breaks unit tests for Svelte-based website.
Reproduction
pnpm
,yarn
ornpm
.pnpm test:unit
,yarn test:unit
,npm run test:unit
)vitest
from 0.25.6 to 0.25.7Expected behavior: In both cases, the unit test succeeds.
Actual behavior: The unit tests succeeds only with vitest@0.25.6. It fails with vitest@0.25.7.
Later versions of Vitest: The test fails with 0.28.4 (latest) as well.
Notable changes from 0.25.6 to 0.25.7:
System Info
Used Package Manager
pnpm
Validations
The text was updated successfully, but these errors were encountered: