test-evidence-review

To verify automated tests before QA sign-off, evaluate assertion coverage, edge-case handling, and naming quality against the story's acceptance criteria. This review process ensures test files actually verify required behaviors and produces ADEQUATE, INCOMPLETE, or MISSING verdicts for each story.

Manual test evidence review verifies criterion linkage, required sign-offs, referenced artifacts like screenshots, and evidence freshness within documentation. It ensures manual evidence documents adequately verify a story's acceptance criteria before reaching QA sign-off by inspecting the provided files.

To audit test evidence quality across a sprint or system epic, perform scope-based auditing on all included stories. The review analyzes assertion coverage and evidence completeness per story, generating a dated evidence-review report with ADEQUATE, INCOMPLETE, or MISSING verdicts for the entire batch.

Yes, you can review test evidence for Logic, Integration, Visual/Feel, UI, and Config/Data story types. The review evaluates specific requirements for each type, such as formula traceability for Logic stories, ensuring automated tests and manual evidence adequately verify the required behavior.

The best way to check edge case coverage in automated tests is via read-only inspection of the test files. The review evaluates assertion quality and edge-case handling against the story's acceptance criteria to determine if the tests adequately verify required behaviors.

No, the test evidence review process does not modify existing test files. It performs a read-only inspection of automated tests and manual evidence documents to analyze assertion and coverage quality, producing verdicts and an optional dated report without altering your source files.