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
I have searched the existing issues (open and closed), and could not find an existing issue
What keywords did you use to search existing issues?
coverage
Please describe why your using this option
I'm running some tests locally and want to dive deep on a particular issue. I've found I can pass -k "Metadata-Version" to pytest to select out the test I want. If, however, I pass this option through tox, the tests fail even when they pass, because the downselecting of tests fails the test coverage:
In the skeleton approach, which uses pytest-cov to enact coverage and pytest-enabler to provide default parameters for a plugin when enabled, it becomes possible to easily disable coverage testing by disabling the plugin: tox -- -p no:cov -k 'Metadata-Version'.
Without this approach, I'm unable to use tox to run the tests without also invoking coverage (and getting the spurious failure). I have to instead run the tests manually.
I guess that's not horrible, but coming from a framework that makes running through tox easier, I thought I'd share this degraded experience.
Anything else you'd like to mention?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What keywords did you use to search existing issues?
coverage
Please describe why your using this option
I'm running some tests locally and want to dive deep on a particular issue. I've found I can pass
-k "Metadata-Version"
to pytest to select out the test I want. If, however, I pass this option through tox, the tests fail even when they pass, because the downselecting of tests fails the test coverage:In the skeleton approach, which uses
pytest-cov
to enact coverage andpytest-enabler
to provide default parameters for a plugin when enabled, it becomes possible to easily disable coverage testing by disabling the plugin:tox -- -p no:cov -k 'Metadata-Version'
.Without this approach, I'm unable to use tox to run the tests without also invoking coverage (and getting the spurious failure). I have to instead run the tests manually.
I guess that's not horrible, but coming from a framework that makes running through tox easier, I thought I'd share this degraded experience.
Anything else you'd like to mention?
No response
The text was updated successfully, but these errors were encountered: