verification-before-completion

Verification before completion works by requiring a verification command to run on the latest changes, capturing command outputs and exit codes. This enforces a robust verification gate, ensuring truthful status reporting by preventing premature success statements.

A verification gate in QA is a checkpoint that requires fresh verification evidence before any completion claim is made. It captures command outputs and failures to support auditable claims, preventing premature success statements during software development.

You report test results with evidence by running the verification command on the latest changes and reporting the full outputs. This captures command outputs, exit codes, and failures to support auditable claims during code reviews and QA gates.

Yes, this verification approach works for QA gates and builds by requiring fresh verification evidence before reporting success. It is designed for QA teams and developers to ensure builds, tests, and checks pass before making any completion claims.

Reporting completion without evidence causes problems because it allows premature success statements. A verification gate solves this by enforcing honest status reporting, capturing command outputs and exit codes to ensure builds and tests actually pass before claiming success.