-
Notifications
You must be signed in to change notification settings - Fork 213
Support --fail-under #13
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
Comments
👍 this feature would be great |
👍 |
yes! want:+1: |
@schlamar: Would you accept a pull request for this? |
Sure :-) |
Added the pull requests (had to fork cov-core too): schlamar/cov-core#8 |
Will be in 2.0 (#28). |
Is there any ETA on that? Cause if it's going to take a long time than I'd opt for using the patch for the 1.x series for the time being ;) |
2.0 is basically the next 1.x because it is fully backward compatible ;) (which means there won't be a next 1.x release) I have no concrete ETA, but it will be probably released before the end of the year. |
BTW, there is mainly documentation stuff left, so you can speed up a release if you help on open points in #28 :) |
The call to `coverage` is required until “fail under” is implemented in `pytest-cov`: pytest-dev/pytest-cov#13
The call to `coverage` is required until “fail under” is implemented in `pytest-cov`: pytest-dev/pytest-cov#13
coverage 3.6 introduced a
--fail-under
parameter to exit non-zero if coverage is below a certain threshold. It'd be great if pytest-cov also supported this.The text was updated successfully, but these errors were encountered: