Coverage check out-of-box

[ai]

Do you want to request a feature or report a bug?

Feature request

What is the current behavior?

It is awesome, that Jest have many tools out-of-box. For example, --coverage. But what is a point to have coverage if you can’t check it in CI? :)

What is the expected behavior?

Add --coverage --statements 100 options. And exit with non-zero exit code on smaller coverage results.

[ai]

Right now my workaround:

    "check-coverage": "istanbul check-coverage --statements 100",
    "test": "jest --coverage && npm run check-coverage && npm run lint && npm run docs"

But it requires extra istanbul dependency.

I agree that it is not big deal. But if we have build-in --coverage, I think we should have built-in coverage check.

[cpojer]

There is a coverageThreshold configuration option for this. http://facebook.github.io/jest/docs/api.html

[ai]

Wow. Thanks.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.