[test] Simplify usage of yarn mocha
#22899
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
|
No bundle size changes comparing 3e0ce3e...84461ad |
eps1lon
changed the title
yarn mocha
oliviertassinari
approved these changes
Oct 5, 2020
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.
Just collects all
--excludepatterns into.mocharc.js. They don't do all that much at the moment but it reduces I/O a bit.The bulk of the startup is still due to
babel. So if that's a problem something likeyarn cross-env NODE_ENV=test mocha '**/Autocomplete.test*'is the "fastest" option.I experimented with a custom CLI in the past and will try to throw something together so that we have a better tool that acts like a "dumb jest-cli" and enables
yarn test Autocomplete.test