maintaining-full-coverage

What problem does it solve?

Ensures engineers do not declare work complete until every line of production code in the repository is exercised by tests and recorded in a checked-in coverage report, preventing silent coverage regressions and "close enough" thinking.

Core Features & Use Cases

• Repository-wide coverage gate: Verifies 100% coverage across all languages and modules before allowing completion, commit, or merge.
• Checked-in reporting: Requires generating and committing a TEST-REPORT.md (or equivalent) with git hash, test counts, and coverage numbers so regressions are visible via git diff.
• Escalation ladder: Provides an ordered workflow from writing tests to heroic testing, asking a human, framework exclusions with approval, and documented exceptions as a last resort.
• Use case: When finishing a feature that touches backend and frontend code, run coverage for each language, fix uncovered lines, and commit a TEST-REPORT.md so CI and reviewers can immediately detect regressions.

Quick Start

Run the repository's coverage commands for all languages, confirm 100% statements coverage, write or update TEST-REPORT.md with the git short hash and test counts, and commit it before claiming the work is done.