Code coverage measurement for Python
http://pypi.python.org/coverage
Coverage.py measures code coverage, typically during test execution. It uses
the code analysis tools and tracing hooks provided in the Python standard
library to determine which lines are executable, and which have been executed.
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
12
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/python-coverage && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
coverage-7.6.4.tar.gz | 0000798716 780 KB | |
python-coverage.changes | 0000067270 65.7 KB | |
python-coverage.spec | 0000003955 3.86 KB |
Latest Revision
Ana Guerrero (anag+factory)
accepted
request 1217070
from
Dirk Mueller (dirkmueller)
(revision 65)
- update to 7.6.4: * fix: multi-line with statements could cause contained branches to be incorrectly marked as missing (issue 1880). This is now fixed. * Fix: nested context managers could incorrectly be analyzed to flag a missing branch on the last context manager, as described in issue 1876. This is now fixed. * Fix: the missing branch message about not exiting a module had an extra "didn't," as described in issue 1873. This is now fixed. * Dropped support for Python 3.8 and PyPy 3.8. * Fix: a final wildcard match/case clause assigning to a name (case _ as value) was incorrectly marked as a missing branch. This is now fixed, closing issue 1860. * Fewer things are considered branches now. Lambdas, comprehensions, and generator expressions are no longer marked as missing branches if they don't complete execution. Closes issue 1852. * Fix: the HTML report didn't properly show multi-line f-strings that end with a backslash continuation. This is now fixed, closing issue 1836, thanks to LiuYinCarl and Marco Ricci. * Fix: the LCOV report now has correct line numbers (fixing issue 1846) and better branch descriptions for BRDA records (fixing issue 1850). There are other changes to lcov also, including a new configuration option :ref:`line_checksums <config_lcov_line_checksums>` to control whether line checksums are included in the lcov report. The default is false. To keep checksums set it to true. All this work is thanks to Zack Weinberg (pull 1849 and pull 1851).
Comments 0