gcovr is a production-grade command-line tool for analyzing C/C++ code coverage data produced by GCC's gcov or LLVM's llvm-cov. It reads intermediate coverage files (.gcda, .gcov, or LLVM JSON intermediates), applies configurable filters and exclusion markers (GCOVR_EXCL_* and LCOV_EXCL_*), merges results from multiple runs, and generates reports in over a dozen formats: HTML (with interactive sorting and line visibility), Cobertura, JaCoCo, Clover, Coveralls, SonarQube, LCOV, CSV, JSON, Markdown, and plain text. The core pipeline is structured as a set of independent modules: a data model with deduplication and merging logic, a filter chain for path inclusion/exclusion, an exclusion engine that operates on lines, functions, and branches, and a format dispatcher that delegates to per-format writer handlers. The architecture is cleanly layered with well-defined boundaries; configuration is unified through CLI args, config files, and environment variables. Although not a data research project, gcovr provides rich quantitative analysis through its built-in metrics (line, branch, condition/decision, and function coverage) and diff coverage comparison, which give it a light analytical character.
octocov is a Go CLI tool and GitHub Action for collecting, analyzing, and reporting code metrics. It measures code coverage (supporting Go cover, LCOV, SimpleCov, Clover, Cobertura, JaCoCo), code-to-test ratio, test execution time, and custom user-defined metrics. The tool integrates deeply with GitHub: it comments on pull requests, posts job summaries, generates SVG badges, uploads artifacts, and stores reports in configurable datastores (local, S3, GCS, BigQuery, GitHub artifacts, Mackerel). It also supports a central mode that aggregates reports from multiple repositories into a single index with per-repo badges. The architecture is a single Go binary with a Cobra CLI. Key entry points are the root command (cmd/root.go) which orchestrates the CI workflow, and subcommands for badge generation, diff comparison, report dump, and central aggregation. Configuration is via YAML (config/). The coverage package contains format-specific parsers that normalize reports into a common model. The datastore package provides a clean interface for storing/retrieving reports, with implementations for each backend. The badge package renders SVG badges using an embedded template and font. The internal page package serves a React-based viewer for coverage diffs. Primary data flow: Parse coverage files from CI (or local), compute metrics, optionally compare with previous report from a datastore, generate badges/comments/summaries, store the new report. Custom metrics are ingested via environment variable files and validated against a JSON schema. Acceptable conditions (using expr-lang) allow failing CI when metrics regress beyond thresholds. External dependencies include GitHub API (google/go-github), AWS SDK, GCP SDK, BigQuery client, Mackerel API, and a JS bundle for the viewer.