gcovr
generate GCC code coverage reports
website and documentation • bugtracker • GitHub
Gcovr provides a utility for managing the use of the GNU gcov utility and generating summarized code coverage results. This command is inspired by the Python coverage.py package, which provides a similar utility for Python.
The gcovr command can produce different kinds of coverage reports:
CLI Option |
User Guide |
Description |
|---|---|---|
default, --txt |
compact human-readable summaries |
|
--html |
overview of all files |
|
--html-details |
annotated source files |
|
--html-template-dir |
use custom set of Jinja2 templates |
|
--csv |
CSV report summarizing the coverage of each file |
|
--json |
JSON report with source file structure and coverage |
|
--json-summary |
JSON summary coverage report |
|
--markdown |
Markdown coverage report |
|
--markdown-summary |
Markdown summary coverage report |
|
--clover |
machine readable XML reports in Clover format |
|
--cobertura |
machine readable XML reports in Cobertura format |
|
--coveralls |
machine readable JSON report in Coveralls format |
|
--jacoco |
machine readable XML reports in JaCoCo format |
|
--lcov |
machine readable report in LCOV info format |
|
--sonarqube |
machine readable XML reports in SonarQube format |
Thus, gcovr can be viewed as a command-line alternative to the lcov utility, which runs gcov and generates an HTML-formatted report. The development of gcovr was motivated by the need for text summaries and XML reports.
Example HTML summary:
Example HTML details:
Installation
Gcovr is available as a Python package that can be installed via pip.
Install newest stable gcovr release from PyPI:
pip install gcovrInstall development version from GitHub (needs at least version 21.3 of pip):
pip install git+https://github.com/gcovr/gcovr.gitQuickstart
GCC can instrument the executables to emit coverage data. You need to recompile your code with the following flags:
--coverage -g -O0
Next, run your test suite. This will generate raw coverage files.
Finally, invoke gcovr. This will print a tabular report on the console.
gcovr
You can also generate detailed or nested HTML reports:
gcovr --html-details coverage.html gcovr --html-nested coverage.html
Gcovr will create one HTML report per source file and for --html-nested also per directory next to the coverage.html summary.
You should run gcovr from the build directory. The -r option should point to the root of your project. This only matters if you have a separate build directory. For example:
cd build; gcovr -r ..
For complete documentation, read the manual.
Contributing
If you want to report a bug or contribute to gcovr development, please read our contributing guidelines first: https://gcovr.com/en/latest/contributing.html
License
This software is distributed under the 3-clause BSD License. See https://gcovr.com/en/latest/license.html#license-terms for details. See https://gcovr.com/en/latest/license.html#acknowledgements for the full list of contributors.
Release files for gcovr 8.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gcovr-8.8.tar.gz | 808.8 kB | With provenance | Details for gcovr-8.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gcovr-8.8-py3-none-any.whl | Python 3 | none | any | Details for gcovr-8.8-py3-none-any.whl |
Total release size: 1.7 MB
Release files / gcovr-8.8.tar.gz
| Download URL | gcovr-8.8.tar.gz |
|---|---|
| Size | 808.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0320230a432c033c1a41f34ba943082f450008c789bee05d414e532f380fd788
|
|
BLAKE2b-256 checksum How to use checksums |
845d75f6913653852720651790bf611e37355ee53cdd298c7f1561cde8773e02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / gcovr-8.8-py3-none-any.whl
| Download URL | gcovr-8.8-py3-none-any.whl |
|---|---|
| Size | 863.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5c3e3d4a9c8ab4a95aa8e4b072fcaec7962b1d9fb2add3f10645f649ef29545
|
|
BLAKE2b-256 checksum How to use checksums |
5389d70fe863ff3549aadd3eabde823796639f8d313912c990fe7dc26cba798d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for gcovr 8.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gcovr-8.8.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
