test-evidence-review

To check if automated tests cover acceptance criteria, evaluate assertion coverage, edge case handling, and naming quality against the required story criteria. This distinguishes between tests that pass and tests that genuinely verify the expected logic.

Manual test evidence review is the process of auditing criterion linkage, required sign-offs, and artefact completeness for Visual, Feel, and UI story types. You need it when manual documentation must prove specific visual and interface requirements were met.

To review test evidence for an entire sprint, locate the story files and evidence artifacts across Logic, Integration, Visual, UI, and Config/Data story types. The evaluation then produces an overall quality verdict with blocking and advisory issue flags.

Yes, you can trace formula logic during a test quality review specifically for logic stories. The evaluation checks for formula traceability alongside assertions and edge cases to verify the underlying mathematical or business logic.

The best way to audit QA sign-offs and artefact completeness is to run an automated evidence review that checks evidence freshness and required approvals. It yields a verdict of ADEQUATE, INCOMPLETE, or MISSING per story.

Test evidence review works without an automated testing framework by evaluating manual evidence documents for criterion linkage and sign-offs. It also assesses automated test quality by checking assertion coverage and edge case handling when test files exist.