-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Failure when coverage threshold not met #3554
Failure when coverage threshold not met #3554
Conversation
See: jestjs#3520 Fixed async calls to each reporter onRunComplete method
This is great! Could you add an integration test in the integration_tests folder. |
Sure, I will look into it. |
Codecov Report
@@ Coverage Diff @@
## master #3554 +/- ##
=======================================
Coverage 62.28% 62.28%
=======================================
Files 181 181
Lines 6714 6714
Branches 6 6
=======================================
Hits 4182 4182
Misses 2529 2529
Partials 3 3
Continue to review full report at Codecov.
|
this is awesome! thank you! |
* Return failure when coverage threshold isn’t met See: jestjs#3520 Fixed async calls to each reporter onRunComplete method * Run prettier
* Return failure when coverage threshold isn’t met See: jestjs#3520 Fixed async calls to each reporter onRunComplete method * Run prettier
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #3520
Fixed async calls to each reporter onRunComplete method
Summary
Whenever the
coverage
is enabled, jest exits with 0 even if the threshold requirements are not met.The Coverage reporter will not return a resolved promise when
collectCoverageFrom
matches files and consequently the Dispatcher will resolve theonRunComplete
promise before collecting the result from reporter.