Test Coverage Tools
Alternatives to Coveralls
Coveralls gives teams a central view of test coverage: dashboards show current percentages and trends, repository pages reach sub-projects, files, and lines, and build history follows changes across branches and pull requests. It can summarize coverage in pull requests, gate merges, notify Slack or webhooks, and connect with many CI services and languages. An API, Linux and web access, and self-hosted deployment support different operating models. Public and open-source repositories are free, while private cloud plans begin at $10 per month.
- 01
Codecov Codecov suits development teams that want coverage checks in pull requests alongside test and bundle analysis.
From $5/mo Free plan Open source Web · macOS · Linux · API9.4 Visit Specs - 02 Coverage.py
Coverage.py suits Python developers who want to see which code their tests execute and which executable code they miss.
Free plan Open source Windows · macOS · Linux · API8.9 Visit Specs - 03 BullseyeCoverage
It is aimed at C and C++ developers and testers, including those working on mission-critical systems and embedded devices.
Free plan Windows · macOS · Linux · Self-hosted8.5 Visit Specs - 04 gcov
gcov suits developers using GCC and test suites to find code that tests do not exercise.
Free plan Windows · macOS · Linux8.5 Visit Specs - 05 Avidemux Free plan Open source Web · Windows · macOS · Linux8.3 Visit Specs
- 06
dotCover From $50.75/mo Free trial Windows · macOS · Linux8.3 Visit Specs - 07 cargo-llvm-cov
It suits Rust developers who want coverage reports in a command-line workflow, including CI pipelines.
Free plan Windows · macOS · Linux8.1 Visit Specs - 08 EclEmma
EclEmma suits individual developers using Eclipse who want coverage views and reports for Java or Scala work.
Free plan Windows · macOS · Linux7.8 Visit Specs - 09 ReportGenerator
ReportGenerator suits developers and teams that need command-line coverage reports across Windows, Linux, or macOS.
Free plan Windows · macOS · Linux7.8 Visit Specs - 10 c8 Free plan Linux7.7 Visit Specs
- 11 Coverlet
It suits .NET teams that need automated line, branch, or method coverage on desktop or server operating systems.
Free plan Windows · macOS · Linux7.7 Visit Specs - 12 gcovr Windows · macOS · Linux7.6 Visit Specs
- 13 NCover Free trial Windows · Self-hosted · Browser extension7.6 Visit Specs
- 14 OpenClover
OpenClover suits teams working with Java, Groovy or AspectJ that need coverage metrics and test-selection support.
Free plan Web · Windows · macOS · Linux7.6 Visit Specs - 15 LCOV Free plan Linux · Self-hosted7.5 Visit Specs
- 16 LLVM llvm-cov
It suits developers and teams examining coverage from instrumented native-language programs.
Free plan Windows · macOS · Linux7.5 Visit Specs - 17 Microsoft Code Coverage
It suits .NET developers who want to measure test coverage for test projects or other .NET applications.
Free plan Windows · macOS · Linux7.5 Visit Specs - 18 Kover
Kover suits Kotlin or Java teams targeting JVM and Android that need report generation and enforceable coverage rules.
Free plan Linux7.4 Visit Specs - 19 SimpleCov
SimpleCov suits Ruby developers who want coverage reports, test mapping, or thresholds for changed lines.
Free plan Web · Windows · macOS · Linux7.4 Visit Specs - 20 Testwell CTC++ Free trial Windows · macOS · Linux · Self-hosted7.4 Visit Specs
- 21 JaCoCo Free plan API7.3 Visit Specs
- 22 Istanbul API6.9 Visit Specs
- 23 Tarpaulin Windows · macOS · Linux · Self-hosted6.9 Visit Specs
- 24 PHP_CodeCoverage Self-hosted6.7 Visit Specs
- 25 Go cover Windows · macOS · Linux5.8 Visit Specs
- 26 grcov Windows · macOS · Linux5.8 Visit Specs
Choosing instead of Coveralls
You may prefer another tool for local report generation, a narrower language focus, or coverage analysis beyond Coveralls’ centralized workflow. Coveralls’ cloud plans add cost for private repositories, and its documented platforms are API, Linux, self-hosted, and web. Before switching, compare supported languages, coverage types, report formats, build and test integrations, and whether you need pull-request controls or historical dashboards. A focused command-line utility may fit a single ecosystem better, while a hosted service may add developer-facing analysis around coverage.