Add pytest-cov

[DevVettel]

Project

pytest-cov

Checklist

• I read CONTRIBUTING.md - awesome-python is a shortlist, not a catalog
• One project per PR
• PR title format: Add project-name
• Entry format: - [pypi-name](https://github.com/owner/repo) - Description ending with period.
• Display name is the PyPI package name
• Placed in an existing use case (new sections and subcategories are maintainer-only)
• Meets all Quality Requirements: active, stable, documented, at least 1 month old

Which Tier

• Obvious choice - a tool an experienced Python developer would name when asked "what do I use for this?"
• Challenger

Explain: pytest --cov is the usual way to measure coverage in pytest projects. It runs coverage.py inside the pytest process, which keeps pytest's sys.path behavior, and it combines data from pytest-xdist workers without extra steps.

• 204.4M downloads/month. For comparison, coverage has 282.4M. pytest-cov hard-depends on coverage, so part of coverage's count comes from pytest-cov installs.
• Maintained under the pytest-dev org, 2.1k stars, last push 2026-09-21, not archived, created 2014
• PyPI classifier is Production/Stable (v7.1.0, released 2026-03-21)

This is a wrapper around coverage, not a replacement for it. I think it is still worth its own entry because many projects use it as their main coverage tool. If you see it as a pytest companion that belongs under awesome-pytest instead, that is a fair call.

Displacement

Not needed. Testing > Code Coverage currently has 1 entry. It is placed after coverage following the downloads ordering.

Note: an earlier PR (#1138, 2018) was closed by the stale bot, not on its merits.

Evidence fetched 2026-10-12: downloads from pypistats.org recent (last_month), repo state from the GitHub API, metadata from PyPI JSON. make test passes (142 passed).

🤖 Generated with Claude Code