proportional-testing

Bucket: discipline · Invocation: automatic

Prevents small changes from accumulating broad, redundant, or implementation-coupled test suites.

Before adding a test, the agent identifies the changed observable behavior, searches existing coverage, and names a realistic regression the new test would catch. If there is no clear answer, the test is not added. Existing or table-driven tests are extended when practical, and the cheapest sufficient test level is preferred.

For a confirmed bug, one reproducing regression check is established when practical, shown to fail for the expected reason, and rerun after the fix. Relevant affected tests follow; broader suites are reserved for uncertain blast radius, shared infrastructure, or required repository gates.

This discipline does not weaken project-defined CI or delivery checks. See the full Proportional testing strategy.