chore(workspace): convert jest over to vitest #2817
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JoviDeCroock
force-pushed
the
migrate-to-vitest
branch
from
3143dbc to
ee50a73
Compare
JoviDeCroock
force-pushed
the
migrate-to-vitest
branch
from
1f7274e to
5f72d21
Compare
JoviDeCroock
force-pushed
the
migrate-to-vitest
branch
from
b61d16c to
5fa89b1
Compare
kitten
approved these changes
Nov 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is very much a work in progress, I have done an initial pass of converting our repo over to vitest from jest.
TODO:
moduleNameMapperconfigurationThe typings are a bit hard currently due to an exclusion we have in our tsconfig
The performance is now comparable to jest but we are still missing the running tests in parallel so we can add
describe.concurrent/... in follow-ups to resolve that.