Analysis & detection
What is Test Coverage Tracking?
Ingesting coverage reports from your test runs and tracking which lines are exercised by tests.
The tool does not run your tests. Your CI does, and it ingests the report your test runner emits (lcov, Cobertura, JaCoCo and similar) and turns it into trends, gates and per-file views.
Coverage is a weak proxy for test quality: it tells you code was executed, not that anything meaningful was asserted. It is nonetheless useful as a floor, particularly when applied to new code rather than the repository total.
Top 6 Test Coverage Tracking tools
Every tool in the directory documented as supporting Test Coverage Tracking, with what its own documentation says.
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
- 1
Coverage Reporter CLI ingests Cobertura, JaCoCo, lcov, Clover, Istanbul and 8 more formats.
- 2CodeAnt AIPR Review
Coverage report upload with dashboard metrics, trend analysis and coverage-gap identification
- 3
Code coverage measurement alongside Code Health, added as a 2025-2026 platform improvement
- 4DeepSourceQuality Platform
Line, branch, condition, and composite coverage tracked; untested lines raised as actionable issues.
- 5
qlty coverage publish accepts lcov, cobertura, clover, jacoco, simplecov, coverprofile and a generic JSONL format
- 6SonarQubeQuality Platform
Coverage import for C/C++/Objective-C, Dart, .NET, Go, Java, JavaScript/TypeScript, PHP, Python.
What to look for
- Which report formats are supported for your language and runner
- Whether coverage can gate a merge, and at what granularity
- Handling of multi-module and monorepo report merging
- Historical trend retention
Related terms
FAQ
What is Test Coverage Tracking?
Ingesting coverage reports from your test runs and tracking which lines are exercised by tests.
How many tools support Test Coverage Tracking?
6 of the 20 tools tracked in this directory support Test Coverage Tracking, including Codacy, CodeAnt AI, CodeScene, DeepSource, Qlty. Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
What should you look for in Test Coverage Tracking?
Which report formats are supported for your language and runner. Whether coverage can gate a merge, and at what granularity. Handling of multi-module and monorepo report merging. Historical trend retention.