Test coverage
summary
Argues that test coverage must be honest: count only the functions a test actually verifies and exclude test code, frameworks, helpers and mocks, otherwise the number is misleading. Demonstrates tooling and workflow—run tests, merge coverage, genhtml reports with lcov/genhtml, or gather coverage without instrumentation using kcov. Calls the untested executed code collateral coverage and recommends carving out only exercised functions or writing dedicated unit tests for bar and baz.
AI-written summary · about
chapters (4)
related talks
07mHow code coverage can be used and abused to guide testing.
02h 46mThe Joy of Testing
10m99% is not enough - full test coverage and why it's awesome
26mImproving Coverage Analysis
19mTesting Your Tests With Code Coverage
37mClean Test Code
51mDebunking Myths Around Test Coverage
48mTest Coverage Myth Busted: Test-to-Code Mapping and Test Impact Analytics