Return exit code 1 if coverage threshold requirements are not met #1974
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.
First of all thanks for this tool!
I'm very new to Jest so please forgive any stupid error or incorrect assumption.
I'm very open to adapt this to the project / community needs, in fact I am trying to understand how to add an integration test for this, any suggestion is more than welcome.
Summary
Whenever the
--coverage
flag is passed, jest exits with0
even if the threshold requirements are not met.Seems like the solution is to determine if a run is successful after
onRunComplete
is called, because in that functionaggregatedResults
is populated with the required values.Test plan
I've written a small POC which has a 100% coverage requirement which is not met.
With the change after you run
npm test
in this POC you will get1
as a result fromecho $?
.