pytest-cov
pytest-cov copied to clipboard
Coverage plugin for pytest.
https://github.com/nedbat/coveragepy/issues/664 (+ later fixes) Signed-off-by: Stavros Ntentos
cc @graingert as requested! ## Background Hello there! The Python packaging ecosystem has standardized on the interface for build backends ([PEP 517](https://peps.python.org/pep-0517/)/[PEP 660](https://peps.python.org/pep-0660/)) and the format for metadata declaration ([PEP...
using pytest ipynb plugin notebooks can be run as unittests. Would it be possible to collect coverage from the notebook tests
My repo contains 3 Python projects in a "projects" dir, and I'm running `pytest --cov=packageA projects/packageA/tests` (for each of the 3 projects). The 2nd project in the test sequence (so...
If `--cov` is passed relative, not absolute, and a subprocess is run in a different directory, then the subprocess coverage will be silently ignored. Example: `test_subprocess_coverage.py` ```python import os import...
I'm using v2.6 and I have a file with a single function marked with this @pytest.mark.no_cover decorator and in the html report it still says the file is 0% covered.
When defining a coverage threshold (88.45 for example) and the actual coverage is very close (88.449 for example) we will get a failure message. However, the message will be: "FAIL...
# Summary First of all sorry for this incomplete bug report (no reproducer). Feel free to close it, but I figured it might still help somebody. The problem is that...
If `usedevelop=True` is not set, coverage for `tox` tests show up as "0%" because `tox` runs the tests in a virtualenv. (See https://stackoverflow.com/questions/58696476/tox-0-coverage)
# Summary This issue is related to https://github.com/pytest-dev/pytest-cov/issues/557 which is closed. The `rsyncdir` argument is deprecated and will be removed in pytest-xdist 4.0. It's currently used in the line below:...