What is test coverage tracking?

Ingesting coverage reports from your test runs and tracking which lines are exercised by tests.

By Cláudia FernandesUpdated

The tool does not run your tests; your CI does. The tool then 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.

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

Best 7 test coverage tools

Every tool in the directory whose documentation covers this. Shown in a random order that changes on every visit, so no tool gets an advantage from its position.

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.

FAQ

What is test coverage tracking?

Ingesting coverage reports from your test runs and tracking which lines are exercised by tests.

How many tools in the directory offer test coverage tracking?

7 of the 20 tools in this directory offer test coverage tracking:

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 check when comparing tools with test coverage tracking?

Four things:

  • 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