verification-before-completion

To prevent premature code completion claims, enforce an evidence-before-assertions protocol requiring developers to run verification commands and present their output before declaring any task complete.

The evidence before assertions principle in quality assurance mandates executing specific verification steps and reviewing their outputs before making any success claims, combating dishonesty by ensuring actual test results precede completion statements.

Verify code correctness before committing by running your test suite, reading the command outputs, and confirming all tests pass. You must present this output as evidence before stating the code is ready.

Your testing workflow allows false claims if it lacks a strict verification gate. Without a protocol requiring the execution and reading of test command outputs, developers may rely on rationalizations instead of actual evidence.

Yes, you can use this verification protocol for all stages of software development. It applies universally to any task completion stage, ensuring identification, execution, and verification of commands precede any status claims.

Common red flags when claiming a software task is complete include rationalizing skipped tests or asserting success without presenting command outputs. A strict verification protocol helps identify and avoid these false claims.