Open Source C++ Code Coverage Tools

Javelina is an advanced code coverage tool that uses dynamic instrumentation to minimize the overhead for collecting coverage data. Additionally, Javelina allows the application of logical operations to code coverage data.

xCover is a C/C++ library that uses low-impact syntactic signalling to detect code coverage in a code base at runtime

A cross platform Http web server developed using C++. Agile methodology with emphasis on :- 1. Good Design 2. Object Oriented Programming 3. Refactoring 4. Static/Dynamic Analysis, Unit-testing, Code Coverage 5. Software Engineering best practices.

A quick C++ template for modern CMake projects aimed to be an easy-to-use starting point. This is my personal take on such a type of template, thus I might not use the best practices or you might disagree with how I do things. Any and all feedback is greatly appreciated! Modern CMake configuration and project, which, to the best of my knowledge, uses the best practices. An example of a Clang-Format config, inspired from the base Google model, with minor tweaks. This is aimed only as a starting point, as coding style is a subjective matter, everyone is free to either delete it (for the LLVM default) or supply their own alternative. Static analyzers integration, with Clang-Tidy and Cppcheck, the former being the default option. Doxygen support, through the ENABLE_DOXYGEN option, which you can enable if you wish to use it. Unit testing support, through GoogleTest (with an option to enable GoogleMock) or Catch2. Code coverage, enabled by using the ENABLE_CODE_COVERAGE op.

Setting up a new C++ project usually requires a significant amount of preparation and boilerplate code, even more so for modern C++ projects with tests, executables and continuous integration. This template is the result of learnings from many previous projects and should help reduce the work required to setup up a modern C++ project. Installable target with automatic versioning information and header generation via PackageProject.cmake. Automatic documentation and deployment with Doxygen and GitHub Pages. Eventually, you can remove any unused files, such as the standalone directory or irrelevant github workflows for your project. Feel free to replace the License with one suited for your project. To keep the template modular, all subprojects derived from the library have been separated into their own CMake modules. This approach makes it trivial for third-party projects to re-use the projects library code.

bcov is a code coverage tool similar to gcov. Unlike gcov, it does not require recompiling the project for coverage. Coverage is determined by using temporary breakpoints, which causes minimal overhead. gcov produces a lcov style coverge report.