-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
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
Try Vitest test runner on this repository #21301
Comments
@zharinov sped up the tests massively. 🥳 My latest docs PR got automerged by GitHub via Merge Queue in about 10 minutes, compared to about 25 minutes before the changes. 😱 Do the maintainers still want to try Vitest, or are we happy with our current test speed? |
yes, would like to try it. |
i think I've not enough time to make it alone 🙃 |
I would be happy to contribute here too☺ |
not sure about the best way to start. does vitest have something like the jest.mock functions? so we can try to create some compabillity stuff? |
Describe the proposed change(s).
I think we want to try the Vitest test runner, to see if it's faster then Jest? I've created this issue to discuss things, and so I can link to other relevant issues.
Vitest says that: 1
Todos to migrate to Vitest
These todos come from the Vitest guide to migrate from Jest:
globals
configuration setting or update code to useimports
from thevitest
module insteadbeforeAll
/beforeEach
hooksDiscussion
Some things to think about:
v0.32.2
.v8
(default) and instrumental code coverage viaistanbul
3Related issues:
@swc/jest
#20477--shard
option to speed up tests #14572Is this a feature you are interested in implementing yourself?
No, I'll let somebody else test Vitest. 😉
Footnotes
https://vitest.dev/guide/migration.html#migrating-from-jest ↩
https://vitest.dev/guide/features.html#running-tests-concurrently ↩
https://vitest.dev/guide/coverage.html ↩
https://vitest.dev/guide/comparisons.html ↩
The text was updated successfully, but these errors were encountered: