Code coverage measures how much source code or how many execution paths tests exercise. In review, it helps teams decide whether testing is sufficient for the change. section 3.3.2
Make coverage part of an explicit review agreement:
- Decide whether missing tests block approval. section 3.3.2
- Question tests that exist only to increase coverage without protecting meaningful behavior. section 3.3.2
- Check that new functionality and significant use cases are covered by unit tests. section 4.4.4
- Allow exceptions only when reviewers understand why accompanying tests are unnecessary. section 3.3.2
A practical review question
Instead of treating a coverage percentage as an automatic approval gate, ask: “Are the important behaviors and significant use cases tested?” This keeps review attention on risk rather than superficial numbers. section 3.3.2 section 4.4.4
