# Coverage Also: code/test coverage; statement, line, branch, condition coverage. - Expected path unexecuted → investigate against intent and risk. - Confirm source/test scope, exclusions, instrumentation, source maps, freshness. Wrong selection or mapping can mislead. - Execution ≠ assertion quality. Covered code can still have missing cases or incorrect expectations. - Not every path needs testing; prioritize meaningful gaps, not percentages or boilerplate. - Missing implementation cannot appear as uncovered code. Requirements and consumer scenarios remain independent evidence. During curation, use existing scoped reports to investigate missing input classes, early rejection, wrong entry points, unreachable code, or report errors. Improve behavioral protection where justified, not one assertion per uncovered line. Report scope and significant omissions. Respect required thresholds without inventing new numeric gates. ## Source - [Fowler: Test Coverage](https://martinfowler.com/bliki/TestCoverage.html)