~3x test execution speedup from updating to jest@30 and moving from ts-jest to @swc/jest
#916
+2,318
−1,213
Conversation
This file contains hidden or 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
Reasons: * Allows update to latest `jest` * Cut test run time in half Before: ``` Test Suites: 34 passed, 34 total Tests: 669 passed, 669 total Snapshots: 0 total Time: 3.742 s ``` after: ``` Test Suites: 34 passed, 34 total Tests: 669 passed, 669 total Snapshots: 0 total Time: 1.277 s, estimated 3 s ```
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.
Jest v30 has performance improvements. However, while
ts-jestclaims it works withjest@30as a peer dependency, it requires a number of changes to the project tsconfig to get it working. Whereas, switching to@swc/jestworks withjest@29andjest@30and it's ~2x as fast asts-jesteven before updating tojest@30.Current test execution time:
Moving to
@swc/jest:Moving to
@swc/jestand updating tojest@30:Motivation and Context
Much faster test execution
How Has This Been Tested?
Running the test suite, confirming the same number of tests ran, the same number passed, and the execution time was significantly less.
Breaking Changes
None.
Types of changes
Checklist
Additional context