test-evidence-review

To audit test quality before QA sign-off, you need to evaluate assertion density, edge case handling, and verification completeness. This process identifies gaps in automated test files and manual evidence documents to generate per-story ADEQUATE, INCOMPLETE, or MISSING verdicts.

Story verification checks whether all acceptance criteria are fully tested by evaluating assertion coverage and evidence completeness. It audits automated test files and manual evidence documents for Logic, Integration, Visual/Feel, and UI story types to ensure no criteria are left unverified.

To review manual evidence completeness for a sprint, you evaluate documents for criterion linkage, sign-off completeness, and artefact freshness. This catches missing QA lead sign-offs or outdated evidence that would block story closure during the sprint review.

Yes, you can perform a test audit across an entire game system or full sprint. The review scope supports individual stories, full sprints, or entire game systems to identify thin test suites and ensure all acceptance criteria are verified.

Standard smoke checks only verify that test files exist and pass, leaving critical gaps in assertion coverage and edge case handling undetected. Deep test evidence review catches these missing criteria verifications and incomplete manual sign-offs that block QA sign-off.

Checking only test file existence ignores formula traceability, test naming conventions, and manual evidence freshness. Without auditing assertion density and criterion linkage, thin test suites and missing edge case handling will go undetected, leading to undiscovered bugs.