Improve local "npm run test" speed from 2:28 to 1:11 #285
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
markreay
approved these changes
Mar 4, 2019
dbjorge
added
the
pr: auto-merge
|
Hello @dbjorge! Because this pull request has the |
waabid
approved these changes
Mar 4, 2019
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.
Pull request checklist
npm run test)<rootDir>/test-results/unit/coveragenpm run precheckin)Description of changes
A huge amount of
npm run test's time was being spent in console output that we don't need. Removing the verbose output per jestjs/jest#6694 (comment) cuts the total runtime on my dev box by more than half.Notes for reviewers
I also experimented with replacing the default reporter, per the same suggestion, but found that this had a negligible impact after the verbose change.