forked from jestjs/jest
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge facebook's master into local master #1
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
* Nice & fast fix * Create a real global
We added this to Flow in v0.25 (about 2 years ago), but never actually deprecated the legacy `declare var exports` syntax. Hoping to do that soon, so clearing up uses that I can find. Test Plan: flow
* add only-failures mode Signed-off-by: Łukasz Sentkiewicz <[email protected]> lint fixes Signed-off-by: Łukasz Sentkiewicz <[email protected]> fix tests Signed-off-by: Łukasz Sentkiewicz <[email protected]> fix tests Signed-off-by: Łukasz Sentkiewicz <[email protected]> * replace 'only-failures' message Signed-off-by: Łukasz Sentkiewicz <[email protected]>
This will fix the false warnings on using the Global Setup/Teardown options
* chore: add support file * chore(support.md): link to SO tag * style(support.md): format with prettier
* fix(jest-message-util): handle expectation being in another file from the test * fix(jest-message-util): exclude codeframes from node_modules * style: flow fixes * test: update snapshots * fix(jest-message-util): don't try to read relative paths * fix(jest-message-util): strip `next (native)` from stack * fix(jest-message-util): don't try to read non-existent files Also fix integration test which worked differently depending on if the test had been run before or not * fix(jest-message-util): make sure the frame chosen has a filename in it
* Use module.builtinModules when it exists * Update CHANGELOG * Add FlowFixMe for module.builtinModules
* chore: add Jest 22 blog post * stye(docs): run prettier on md * docs: fix header * docs: add images * docs(changelog): update for jest 22 * docs(blog): add fbID * docs(blog): fix backticks in links * docs(blog): repo -> org
* Fix backticks * Fix typo
Add section to the docs that showcases the various npm packages that jest publishes.
Add forceCoverageMatch config option to allow collecting coverage even if the file is ignored. This way you can collect coverage from the source files with tests or specific files you ignored manually.
…ue` (#5117) * fix(jest-runtime): only write map files to disk when `mapCoverage: true` * docs: update changelog and run prettier
* test: handle both `ms` and `s` in test timings * test: add `$` to only match end of string
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
Test plan