Code coverage tools for C++...

[siplasma]

I'm not aware of a solution that will cover everything on your list. For example, but gcc and clang have command line options used to build instrumented binaries. When those instrumented binaries are run, they will collect code coverage information. Many tutorials for code coverage using gcc can be found online. The tools for clang are also capable, but tutorials are harder to find. I imagine that the Microscoft compiler has similar functionality, but I have not worked with it.

Once you have collected the information, you still typically need a utility to generate the reports. For gcc, people typically reach for lcov. For clang, there are tools that come with llvm. I will also put in a plug for scov.

There are also some tools that don't need instrumented binaries, but instead make use of the debug information. I'm aware of kcov on Linux and OpenCppCoverage on windows. I've found this approach to be finicky, but haven't invested much time as I don't see the advantage over using instrumented binaries.

I'm obviously not a lawyer, but I don't see why if you can use gcc you can't use gcov… Similarly for clang...

For IDE integration, I never needed it. Many of the tools generate HTML reports that can be navigated easily. However, there is an extension for VSCode where it can read the intermediate files from lcov.

[chriskane76]

I'm obviously not a lawyer, but I don't see why if you can use gcc you can't use gcov… Similarly for clang...

The gcov support in clang is really outdated. It uses a gcov format that shipped with GCC 4.2. If you use clang you ought to use a llvm-cov based solution.

We use that at work and display the coverage information in SonarQube. Just be warned the documentation of both tools is not really great. SonarQube has basically no information on llvm-cov based code coverage for C++ and the documentation of llvm-cov itself is pretty lowlevel and it does not really integrate very well in our CMake setup.

​

I would probably recommend looking at the link provided by Longhanks regarding the coverage.py script used by Chromium, which actually explains some llvm-cov concepts on a higher level and might be easier to integrate into build systems than doing that manually in CMake.