verification-before-completion

To enforce evidence-based completion, you must run fresh verification commands like tests or builds and validate the exact outputs before making any success claims. This structured verification flow prevents premature or unverified assertions about bug fixes.

Backing continuous integration claims involves identifying a specific validation command, executing it to capture fresh outputs, and verifying the results. This process ensures that quality assurance assertions are fully traceable and audit-friendly before task completion.

You create traceable verification records for QA audits by executing exact validation commands and reporting their raw outputs prior to completion. This evidence-based approach guarantees that every test success or performance improvement claim is backed by fresh, reviewable data.

Pytest works effectively within structured verification flows by serving as the fresh verification command. You run the pytest suite, read the outputs, and validate the results, ensuring your continuous integration process prevents premature success claims before final reporting.

You need fresh verification evidence before asserting task completion to prevent unverified success claims. Requiring fresh test or build outputs ensures that quality assurance standards are met and creates traceable, audit-friendly records for subsequent reviews.

Relying on previous test runs for completion validation risks stale evidence and missing recent code changes. By enforcing fresh verification command execution, you ensure that continuous integration outputs accurately reflect the current state before any task success is claimed.