You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My suspicion is that vitest would let us clean up a lot of the test infrastructure using their fixtures. I have strange issues with jest that I consistently cannot explain and it is definitely verrrry slow. I'll attach a PR to this issue so that some numbers can be put alongside this musing.
The text was updated successfully, but these errors were encountered:
My experience with vitest has always been that it's a drop-in replacement for jest. Config is a little different (it uses the vite config style), but api is otherwise identical to jest/node test/bun test.
Vite is not required to use vitest. Vitest uses vite under the hood and is part of that same ecosystem.
I have a pretty specific idea in connection with adopting vitest, and my hope is that I can speed up the tests a lot. I'll create a PR for it at some point to explain my idea - I like to run tests as I code so speed is a big priority when I build test suites
My suspicion is that vitest would let us clean up a lot of the test infrastructure using their fixtures. I have strange issues with jest that I consistently cannot explain and it is definitely verrrry slow. I'll attach a PR to this issue so that some numbers can be put alongside this musing.
The text was updated successfully, but these errors were encountered: