claw-ideas/ideas/dev-tooling/test-coverage-enforcer.md

Test Coverage Enforcer

Enforce coverage quality gates in pull requests, and provide concrete suggestions on untested code paths before changes are merged.

Problem

Coverage drifts over time because teams notice regression too late, and raw percentages rarely tell contributors what to test next.

Core capabilities

• Track global and per-module coverage thresholds.
• Fail checks or post PR comments when coverage regresses.
• Map changed lines to missing tests and suggest test targets.
• Maintain allowlists for generated code and low-value files.

MVP scope

• GitHub/Gitea status checks with configurable thresholds.
• PR comment bot showing delta coverage and top uncovered files.
• Optional soft mode (warn only) before strict enforcement.

Success criteria

• Coverage regressions are caught before merge.
• Test additions increase specifically around changed business logic.

Stretch ideas

• Suggest concrete test skeletons using project conventions.
• Score tests by mutation-testing signals, not only line coverage.