verification-before-completion

To enforce running tests before claiming code completion, you need a verification protocol that mandates executing test suites and reviewing their output. This ensures concrete evidence precedes any assertions of success, preventing false positives.

A verification protocol in test-driven development is a strict process requiring the execution and review of commands like linters, builds, or tests. It ensures work completion claims are backed by concrete evidence, mitigating risks of shipping incorrect work.

Your code completion process allows shipping incomplete work because it lacks mandatory verification steps. Without enforcing test execution and output review before making success claims, false positives occur and bugs slip through due to unverified assumptions.

To prevent false positives when fixing bugs, mandate a verification step where you reproduce the original symptom and confirm it no longer occurs. You must run relevant commands and review their output before declaring the bug fixed.

Yes, you can use process enforcement to mandate linter checks before success claims. This protocol ensures linters are executed and their output is reviewed, guaranteeing code quality standards are met before any work completion assertions are made.

Assuming tests pass without running them risks shipping incorrect or incomplete work due to false positives. This practice bypasses necessary evidence gathering, allowing hidden bugs and linter failures to reach production because verification was skipped.