Coveralls

Coveralls analyzes test coverage so developers can see which parts of their code lack tests. Its dashboard shows current project coverage percentages and how they change over time. Repository views let users inspect coverage by sub-project, file, and individual line; build history tracks changes across branches, including pull requests. Coveralls can add coverage summaries to pull requests and send status updates that apply coverage criteria to merge decisions. Notifications can go to Slack or webhooks. It supports line and branch coverage, and lists languages including C/C++, Go, Java, JavaScript, .NET, PHP, Python, Ruby, and Scala. The service says it works with any CI service and offers more than 30 community-created integrations, a GitHub Action, and a CircleCI Orb. Open-source and public repositories are free. The Starter plan is $10/mo for one private repository and includes a 30-day free trial. Self-hosted deployment is available; its enterprise installation can run within existing security controls without outbound network access.

Coveralls combines coverage dashboards and build history with pull-request reporting and coverage gates. Its free offering covers open-source and public repositories, while the listed Starter plan is $10/mo for one private repository.

Coveralls suits development teams that want coverage details across projects and builds, including in pull requests. It may also suit teams that need self-hosted deployment or free coverage for open-source and public repositories.

Coveralls is a test-coverage service that shows where code lacks tests and how coverage changes across builds. It suits teams that want coverage results in pull-request review and merge decisions. Its strongest fit is a CI-connected view of coverage over time; teams choosing a private-repository plan need to match its repo limits to their needs.

Overview

Coverage dashboards pair current project percentages with historical graphs, and repository pages drill into sub-projects, files, and individual lines. That makes the service useful both for tracking a broad trend and for finding specific gaps. Line and branch coverage are supported, with reports accepted in formats including LCOV, SimpleCov, Cobertura, JaCoCo, Gcov, and Pytest-Cov.

Key features

Build history tracks coverage across builds and branches, including pull requests. Pull-request summaries and annotations put results into code review, while coverage criteria can allow or block merges. Slack and webhook notifications can flag coverage changes. Together, these features suit teams that want coverage to inform review decisions, not just produce a report.

Coveralls says it works with any CI service and offers more than 30 community integrations, plus a GitHub Action and CircleCI Orb. Supported languages span .NET, C/C++, Go, Java, JavaScript, PHP, Python, Ruby, Scala, and others. Its API can add repositories programmatically and return recent-build statistics, useful for teams automating setup or reporting.

For cloud use, Coveralls reads code through the SCM OAuth token, accesses repositories read-only, and says it does not store or cache private code. Detailed file coverage is retained for 12 months on paid repositories and six months on public repositories; aggregated build-level coverage is retained indefinitely. Enterprise on-premises installations run within a customer's existing security controls and can operate without outbound network access, an option for organizations that cannot send coverage analysis through the cloud.

Pricing

Open Source is free for open-source projects, and Coveralls says public repositories are always free. The free offering is the clearest fit for public projects; teams needing private-repository capacity must choose a paid Cloud plan.

Starter costs $10/mo for one private repository and includes a 30-day free trial. It is a low-cost starting point for an individual project, but its single-repository limit is restrictive for teams managing several private codebases. Org is $50/mo for 10 private repositories and unlimited users; Org+ is $100/mo for 20; Pro is $200/mo for 40. These tiers suit teams that need more private repositories without a per-seat charge.

Unlimited costs $400/mo for unlimited private repositories and users. Cloud Premium is $800.00/mo for unlimited private repositories, premium support, custom SLA terms, and multi-org billing. Enterprise Cloud is $35/user/mo, with unlimited organizations, repositories, and users, secure private infrastructure, guaranteed performance, and premium support; its 40-seat minimum makes the entry cost $1,400/mo, so it is aimed at larger organizations rather than small teams.

Two add-ons can extend Cloud plans: the Usage add-on is $30/mo for 3,000 additional uploads per month, priority processing, and repo-scoped use; Support is $200/mo for premium support, priority response, and live chat. Both combine with any Cloud plan. The paid tiers primarily trade higher monthly cost for more private repositories, upload capacity, support, or enterprise controls.

Platforms

Coveralls supports API, Linux, self-hosted, and web use. The breadth gives teams several deployment and integration paths, while self-hosting is particularly relevant to organizations that need coverage analysis to remain inside their own security controls.

Who it's for

Coveralls is a strong fit for teams already using CI who want coverage trends, line-level detail, and pull-request checks in one workflow. Public and open-source projects can use it without a subscription; private-code teams should compare repository needs against the paid tiers. It is less compelling for a lone private project that does not need review automation or history, since Starter's main value is that integrated workflow rather than broad capacity.

Pros and cons

• Pros: Pull-request summaries, annotations, and merge gates put coverage into code review rather than leaving it in a separate dashboard.
• Pros: Historical graphs and drill-down from project totals to individual lines help teams follow trends and locate gaps.
• Pros: Public and open-source repositories are free, while cloud, self-hosted, and enterprise options cover different deployment needs.
• Cons: Starter covers only one private repository, so teams with multiple private projects must move to a higher tier.
• Cons: Enterprise Cloud's 40-seat minimum sets a $1,400/mo starting commitment, which is a substantial threshold for smaller organizations.
• Cons: Detailed file-level coverage expires after six months for public repositories and 12 months for paid repositories, even though aggregate build coverage remains indefinitely.

Alternatives

Test Coverage Tools is the broader category directory for readers comparing coverage software. Choose Codecov instead if its freemium model and Developer plan's 250 private-repository uploads, unlimited public repositories, and one-user open-source cap or unlimited private users better match your usage.

gcov is a free option for users on Linux, macOS, or Windows whose code is compiled with GCC and instrumented to generate coverage data. MozJPEG is a free, open-source JPEG encoder library rather than a test-coverage service.

ReportGenerator may suit readers seeking a report-focused tool with a free basic open-source tier and a 10-day full-access trial. Coverage.py is a free open-source Python coverage tool, while Coverlet is a free MIT-licensed option for modern .NET SDK-style projects.

EclEmma is a free Eclipse plug-in for Java code coverage. gofmt is a free command-line executable included with Go installation.

Verdict

Choose Coveralls if you want coverage history, detailed repository views, and pull-request checks that can influence merges, especially for public projects or teams with several private repositories and a suitable plan. Look elsewhere if your needs are limited to a free single-language tool, or if the private-repository caps and higher-tier commitments outweigh the value of its integrated review workflow.