verification-before-completion

To verify code changes with evidence, execute tests, linting, and builds directly, then capture their full output. You evaluate these results to produce evidence-backed status updates, preventing unverified completion claims in software development.

Evidence-driven verification in software QA is a workflow requiring fresh execution outputs from tests, linting, and builds before making any completion assertions. It ensures claims are backed by verifiable evidence, avoiding false positives during code reviews.

You need to run build verification before a pull request whenever you intend to update task statuses or claim work is complete. This structured gate requires running verification commands and capturing outputs to prevent unverified claims.

The best way to prevent false positives in testing and linting is to enforce a structured verification workflow. This involves executing verification commands, reviewing the full output, and reporting claims only with verifiable evidence.

No, evidence-driven verification does not require specific testing frameworks. It applies to any software development context by enforcing a five-step gate to execute verification commands, capture outputs, and evaluate results for evidence-backed statuses.