-
Notifications
You must be signed in to change notification settings - Fork 214
Add option to prevent coverage erase #5
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
Then it would also make sense to allow specifying suffix of the coverage file, e.g. |
See #16 how you can specify data files for different tox environments. I guess you might even do not need an option to prevent erasing. If you result to |
Didn't know about |
Will work as expected in 2.0 release, see for details: http://lists.idyll.org/pipermail/testing-in-python/2014-November/006224.html |
# This is the 1st commit message: Add Python 3.11 and PyPy 3.9 to the testing # The commit message pytest-dev#2 will be skipped: # tox.ini: Add py311 and pypy39 # The commit message pytest-dev#3 will be skipped: # pytest72 # The commit message pytest-dev#4 will be skipped: # xdist302 # # Co-authored-by: Mason Lin <[email protected]> # The commit message pytest-dev#5 will be skipped: # coverage65 # # Co-authored-by: Mason Lin <[email protected]> # The commit message pytest-dev#6 will be skipped: # Drop py36 and upgrade to pytest-xdist==3.1.0
This is useful if you have multiple test runs, e.g. with tox, and want to combine the results at the end of all runs.
The text was updated successfully, but these errors were encountered: