Open HonkingGoose opened 1 year ago
@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 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: ^quote
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
^coverageRelated issues:
20477
14572
Is this a feature you are interested in implementing yourself?
No, I'll let somebody else test Vitest. 😉