test-evidence-review

To audit test evidence before a sprint sign-off, review automated tests and manual QA artifacts to evaluate assertion coverage, edge cases, and evidence freshness, ensuring story verification is sufficient for release readiness.

Adequate test evidence for QA sign-off on Visual and UI stories requires manual evidence review, checking acceptance-criterion linkage, required sign-offs, screenshots, walkthroughs, and evidence freshness to produce an ADEQUATE verdict.

Checking automated tests for edge case coverage involves reviewing test quality analysis to evaluate assertion coverage, naming quality, and formula traceability in Logic and Integration tests to identify gaps blocking story verification.

Yes, you can audit test quality across multiple stories by applying scope-based reporting to the current sprint, reviewing assertion coverage and manual evidence to assign ADEQUATE, INCOMPLETE, or MISSING verdicts for system-level audits.

The best way to identify missing acceptance criteria linkage is through manual evidence review, checking required sign-offs, screenshots, and walkthroughs to surface blocking gaps for QA follow-up before closing a sprint.

A passing automated test results in an incomplete story verification verdict when test quality analysis reveals missing assertion coverage, poor naming, lack of formula traceability, or outdated manual evidence that fails sign-off requirements.