test-evidence-review

Evaluate automated test quality and manual evidence completeness for game stories.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill test-evidence-review-imgamer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/imgamer/AILearn --skill test-evidence-review-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents stories from reaching QA sign-off with tests that merely exist or evidence that is incomplete, by evaluating both automated test quality and manual evidence completeness.

Core Features & Use Cases

  • Automated test quality review: Checks assertion coverage, edge-case handling, naming quality, and formula traceability for Logic/Integration stories.
  • Manual evidence review: Verifies criterion linkage, sign-off completeness, artefact presence (screenshots/walkthrough), and evidence freshness for Visual/Feel and UI stories.
  • Scoped reporting: Runs for a single story, an entire sprint, or all stories within a system/epic, producing an ADEQUATE/INCOMPLETE/MISSING verdict per story.

Quick Start

Run /test-evidence-review for a specific story-path to get a quality report on the linked tests and manual evidence.

Frequently Asked Questions about test-evidence-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify test quality and evidence completeness before QA sign-off?

You can verify test quality before QA sign-off by evaluating assertion coverage, edge-case handling, and manual evidence presence rather than just checking that tests pass, producing ADEQUATE, INCOMPLETE, or MISSING verdicts per story.

What is assertion coverage analysis for game story logic tests?

Assertion coverage analysis for game story logic tests evaluates automated test quality by scanning expected evidence locations, checking formula traceability, and validating edge-case handling heuristics to ensure tests are robust.

How do I review manual evidence for Visual and UI game stories?

Review manual evidence for Visual and UI game stories by verifying criterion linkage, validating required sign-offs, and checking artefact presence such as screenshots or walkthroughs to ensure evidence freshness and completeness.

Can I run test evidence reviews across an entire sprint or epic?

Yes, you can run test evidence reviews across a single story, an entire sprint, or all stories within a system or epic, producing scoped quality verdicts for Logic, Integration, Visual, UI, and Config/Data stories.

Why do passing automated tests still fail QA sign-off?

Passing automated tests can fail QA sign-off because they may lack sufficient assertion coverage, miss edge-case handling, or have incomplete manual evidence like missing screenshots, walkthroughs, or required sign-offs.

Does test evidence review work for Config and Data game stories?

Yes, test evidence review works for Config/Data game stories alongside Logic, Integration, Visual/Feel, and UI stories, analyzing assertion coverage and validating criterion linkage to produce per-story quality verdicts.