You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without the reset option, tox runs will include coverage on both the installed package and local copy (which is always zero).
As a bonus, such a simple implementation of --cov-reset could even be used to replace --no-cov altogether (the only requirement being that --cov-reset has to go after all the --cov options), so it's more flexible and a much simpler implementation. However, one would have to think carefully about all the use cases for no-cov (debuggers are mentioned)
Here's a pull request if you think this is worthwhile: #459
The text was updated successfully, but these errors were encountered:
It is sometimes useful to "reset" all the --cov=X options passed in "so far", eg.
would only check for coverage on
app/module
instead of checking the coverage on all modules inapp
.My particular use case is to allow getting coverage from both local pytest and tox runs (tox is slower :)), yet keep tox using the installed package:
pytest.ini:
tox.ini:
Without the reset option, tox runs will include coverage on both the installed package and local copy (which is always zero).
As a bonus, such a simple implementation of --cov-reset could even be used to replace --no-cov altogether (the only requirement being that --cov-reset has to go after all the --cov options), so it's more flexible and a much simpler implementation. However, one would have to think carefully about all the use cases for no-cov (debuggers are mentioned)
Here's a pull request if you think this is worthwhile: #459
The text was updated successfully, but these errors were encountered: