verification-before-completion

To enforce running tests before claiming code completion, apply a strict protocol requiring explicit execution of verification commands and review of their outputs. This prevents false assertions by ensuring demonstrable evidence precedes any success claims.

Evidence-based verification in software development is a protocol requiring explicit output or exit codes as proof of correctness. It prevents premature declarations of work completion by demanding fresh, verifiable evidence for all success claims during testing, linting, or building.

Developers make false assertions about bug fixes being complete when they declare success without fresh, verifiable evidence. This happens when verification commands are not explicitly executed and their outputs are not reviewed, leading to premature claims of correctness.

To verify a build passes before committing code in CI/CD, run the test suite and confirm zero failures, then present the output as evidence. This mandatory verification protocol ensures all success claims are backed by demonstrable proof.

Yes, this verification protocol works with agile testing and linting workflows. It applies to all stages of development, enforcing mandatory execution and review of verification commands to prevent false assertions across the entire CI/CD pipeline.

Claiming work completion without verification leads to false assertions and unverified code quality. Without explicit execution of testing and linting commands, developers risk integrating failures and bugs due to a lack of demonstrable evidence.