This article explains what code coverage is, why it matters, the different coverage metrics, how coverage measurement works, and reviews several mainstream tools across various programming languages.
The article explains how to instrument code for coverage using LLVM’s modular compiler infrastructure—adding compile‑time probes that generate .gcno files, runtime counters that produce .gcda files, and then parsing these with GCOV, while detailing LLVM IR, basic blocks, flow graphs, and extensions for custom plugins.
This article provides a step‑by‑step tutorial on performing C++ code‑coverage testing using gcov, covering compilation flags, running the instrumented program, generating gcov reports, and creating detailed HTML reports with lcov, including command examples and configuration details.
To meet strict quality goals for iOS projects, the article describes adopting intermediate‑file code‑coverage instrumentation, generating gcno/gcda files, using lcov for full and incremental analysis, and integrating the process into builds and CI to enforce coverage thresholds and guide test‑case design.
This article explains gcov, the GCC‑bundled C/C++ code coverage tool, covering its basic concepts, the workflow for generating coverage data, and the instrumentation technique using basic blocks and arcs to record execution counts.
This article explores the challenges of iOS code coverage, explains the generation of .gcno and .gcda files using LLVM, and presents a transparent, Git‑aware incremental coverage solution that integrates into the development workflow with minimal overhead.
This article explains how to set up gcov and lcov on Ubuntu, write a simple C++ program, compile it with coverage flags, generate .gcno and .gcda files, use lcov to create an HTML coverage report, and interpret the resulting line and function coverage percentages.
This article explains the concepts of code coverage, describes different coverage metrics such as statement, branch, and function coverage, introduces BullseyeCoverage and gcov/lcov tools, and provides detailed step‑by‑step procedures for measuring coverage in both executable binaries and dynamic libraries for C/C++ projects.
