Code quality platforms
What is Coveralls? An introduction to the code coverage analytics service
Coveralls is a test coverage analytics service that tracks and reports code coverage history and statistics across CI services. It measures, tracks and helps improve code coverage across an engineering organization. It also shows which parts of code are not covered by tests.
- Tool
- Coveralls
- Made by
- Coveralls
- Official site
- coveralls.io
- Category
- Code quality platforms
Who makes Coveralls
Coveralls is made by Coveralls. The official website is linked below, and it is the place to check current documentation and integration details.
Official website: coveralls.io
What Coveralls is for
Coveralls is for understanding how much of a codebase is exercised by its tests, and how that changes over time. It works with the user's CI server and analyzes the coverage data produced by CI runs, so the numbers come from the same pipeline that already builds and tests the code.
Because it shows which parts of code are not covered by tests, it gives teams a concrete list of gaps rather than a single percentage. Coverage history is retained without limit, so every detail of past coverage can be inspected later.
Who Coveralls is for
The vendor names three audiences: engineering organizations, open source maintainers and teams with private repos. Sign-in is available through GitHub, Bitbucket or GitLab, so accounts map onto the code hosting services these teams already use.
Teams with large repositories are covered as well. Coveralls offers monorepo features such as Carryforward Flags and Monorepo Layout Settings, and it can be run on the customer's own servers for organizations that want to keep the service in their own infrastructure.
Notable capabilities
Coveralls combines reporting views, pull request feedback and automation hooks around coverage data. The capabilities below are the ones the vendor documents.
- Repo pages report coverage from the aggregate level down to individual lines, so a reader can move from a project-wide figure to the exact code behind it.
- Source file pages provide color-coded line-by-line coverage, which makes untested lines easy to spot while reading a file.
- Build history tracks coverage changes per build on every branch, including pull requests.
- Summarized coverage reports appear directly in pull requests, and merges can be allowed or blocked based on coverage criteria that the user sets.
- Coverage change notifications can be sent to Slack or webhooks, and coverage badges can be displayed for repositories.
- Integration packages exist for many languages, including C/C++, Go, Java, JavaScript/Node, Python, Ruby, PHP and others.
- CI-specific integrations include a GitHub Action and a CircleCI Orb.
- Repos can be added and build stats retrieved programmatically, which allows coverage setup and reporting to be scripted.
How Coveralls fits code quality platforms
Within code quality platforms, Coveralls focuses on a single signal: test coverage. It does not inspect code for style problems or vulnerabilities. Instead, it reports how much of the code the test suite reaches, and it keeps that history across builds, branches and pull requests.
In the wider world of linters, static analysis and code quality that Linthelm covers, this makes it a companion to other tools rather than a substitute for them. Linters and static analyzers examine the code itself, while a coverage service reports on how well tests exercise it. Merge rules based on user-set coverage criteria let that signal act as a gate in the same review flow where other checks run.
Frequently asked questions
What is Coveralls used for?
Coveralls is used to measure, track and help improve code coverage across an engineering organization. It analyzes coverage data from CI runs and shows which parts of code are not covered by tests.
Who develops Coveralls?
Coveralls is developed by Coveralls. The official website is https://coveralls.io.
Which languages does Coveralls support?
Integration packages exist for many languages, including C/C++, Go, Java, JavaScript/Node, Python, Ruby, PHP and others.
Can Coveralls block a pull request based on coverage?
Yes. Merges can be allowed or blocked based on coverage criteria that the user sets, and summarized coverage reports appear directly in pull requests.
Can Coveralls run on my own servers?
Yes. Coveralls can be run on the customer's own servers.
Linthelm is independent and is not affiliated with Coveralls. Product names belong to their owners. Features change; confirm details on the official website.