skills.rest
emcconnell
emcconnellCOMMUNITY
Explore all skills by this author →
GitHub

test-evidence-review

Evaluate test coverage and evidence to issue ADEQUATE, INCOMPLETE, or MISSING verdicts.

Updated Apr 10, 2026
Search Tags:#automation#qa#evidence#review#sign-off#coverage#test
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill test-evidence-review-emcconnell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/emcconnell/nova-scout --skill test-evidence-review-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured methodology for evaluating the quality of test files and manual evidence documents, ensuring that each story's test coverage, edge-case handling, naming quality, and evidence completeness meet project QA standards and produce a clear verdict (ADEQUATE, INCOMPLETE, or MISSING) before sign-off.

Core Features & Use Cases

  • Automated analysis of test assertions, edge-case coverage, naming quality, and formula traceability for Logic and Integration stories.
  • Manual evidence evaluation for Visual/Feel and UI stories, including criterion linkage, sign-offs, artefact completeness, and freshness.
  • Generates a consolidated review report per sprint or system scope to guide QA and development teams.

Quick Start

Run the review on a single story path or an entire sprint to begin automated and manual evidence evaluation.

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema
How do I evaluate test coverage and evidence quality for sprint sign-off?▼

The review process analyzes test assertions, edge-case handling, and manual evidence completeness to generate an ADEQUATE, INCOMPLETE, or MISSING verdict for sprint sign-off.

What is test evidence review and how does it work for QA automation?▼

Test evidence review is a QA automation process that identifies and evaluates the quality of test files and manual evidence documents across stories to determine a structured decision verdict before project sign-off.

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

Review manual evidence for Visual and UI stories by evaluating criterion linkage, sign-offs, artefact completeness, and freshness to ensure documentation meets project QA standards before final approval.

Does test evidence review work for Logic and Integration story types?▼

Yes, the review applies to Logic and Integration stories by performing automated analysis of test assertions, edge-case coverage, naming quality, and formula traceability to assess test coverage quality.

What's the best way to generate a consolidated QA review report for a sprint?▼

Generate a consolidated QA review report by running the evaluation across an entire sprint scope, producing structured assessments that outline test coverage, evidence criteria, and identified gaps.

Why does my test evidence get an INCOMPLETE verdict during coverage review?▼

An INCOMPLETE verdict occurs when test evidence review identifies gaps in test coverage, missing edge-case handling, poor naming quality, or insufficient manual artefact completeness that fail to meet QA standards.

Related Skills

Explore More Software Engineering Skills→
XGanQAQXGanQAQ
1

test-evidence-review

Validate game test files and manual evidence against story acceptance criteria.

Community
Advanced
Negentropy-LabyNegentropy-Laby
3

test-evidence-review

Evaluate test evidence and manual artefacts with per-story verdicts.

Official
Advanced
Euraika-LabsEuraika-Labs
14

test-evidence-review

Review test files and manual evidence documents for quality and completeness.

Official
Intermediate
raiichraiich
1

doc-reviewer

Review Markdown files for naming, conciseness, consistency, and completeness.

Community
Basic