Coverage.py
7.3#3 in test coverage toolsFree planFree planAPILinuxmacOSSelf-hosted
VisitCoverage.py vs Microsoft Code Coverage
Microsoft Code Coverage
6.1#13 in test coverage toolsFree planFree planLinuxmacOSWindows
VisitWhat both publish
| Fact | Coverage.py | Microsoft Code Coverage |
|---|---|---|
| Configuration | Settings can live in .coveragerc, TOML, setup.cfg, tox.ini, or pyproject.toml files. | Coverage settings can control output, inclusion and exclusion rules, and instrumentation options using runsettings or dedicated coverage settings files. |
| Intended users | The documentation presents Coverage.py as a tool for people measuring Python test effectiveness by seeing which code tests exercise and which they miss. | The documented workflows cover .NET test projects and other .NET applications that users want to measure for code coverage. |
| Purpose | Coverage.py measures which parts of Python programs ran and identifies executable code that did not run, commonly to gauge test effectiveness. | Measures what proportion of a project's code is exercised by coded tests such as unit tests. |
| Report formats | Reports can be emitted as text, HTML, XML, LCOV, or JSON. | The MTP coverage extension supports coverage, XML, and Cobertura output formats. |
| Security | The project directs vulnerability reports to Tidelift, which it says will coordinate the fix and disclosure. | The repository links to a security policy, but its README describes this repository as documentation and samples for closed-source coverage functionality. |
Coverage.py plans
- Coverage.pyFree
- FreeFree
Microsoft Code Coverage plans
- Microsoft Code CoverageFree
Pick Coverage.py if…
Coverage.py is for developers measuring how much of their Python code their tests exercise. Its report formats and dynamic contexts can help teams inspect coverage in different ways.
Pick Microsoft Code Coverage if…
Microsoft Code Coverage suits developers measuring coverage in .NET test projects or other .NET applications. It is relevant to teams using supported test runners and operating systems, provided they account for instrumentation requirements.