In CLion, you can run CMake applications and tests with code coverage measurements. Code coverage results provide the percentage of code lines executed during a run and the number of times a particular line was hit.
Compiler flags for code coverage
See below the options for the flags depending on your compiler and the coverage tooling you prefer.
In this case, the gcov tool will be used.
You have two options here:
Running CMake applications or tests with coverage
Run with Coverage is available from the toolbar next to the configuration switcher and from the gutter menu:
Reading coverage results
When coverage data is ready, the Coverage tool window opens up automatically. It shows the percentage of the files per folder and lines per file covered during the launch:
In any file, you can check the gutter indicator and click it next to a particular line to learn how many times it was hit:
A line executed fully is marked green. Yellow marker means that it was only partically executed.
To modify the colors of coverage highlighting, click or go to Line Coverage node.and expand the
CLion also shows coverage statistics in the Project view:
Merging results from several runs
When you rerun coverage analysis, CLion prompts you to choose how you prefer the new results to be presented:
Add to active suites – new results will be added to the previously collected statistics.
Replace active suites – the already collected data will be overwritten.
Do not apply collected coverage data – new results will be ignored.
Configure the coverage settings
Code coverage settings are gathered in the:
In the Tools section, you can provide custom paths to gcov / llvm-cov / llvm-profdata. By default, CLion takes the paths from the
PATH environment varible.
Troubleshooting and current limitations
If you get empty coverage reports, check whether your compiler version matches the version of gcov / llvm-cov tool (default or custom) that you are using.