test-evidence-review

Name: test-evidence-review
Availability: InStock
Author: kay6198835

Assess test evidence quality across stories, sprints, or systems.

Updated Feb 8, 2024

Search Tags:#edge-cases #qa-review #test-evidence #assertion-coverage #sign-offs #story-audit

Ready to run

npx skills add https://github.com/kay6198835/Game-RPG --skill test-evidence-review-kay6198835

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill test-evidence-review-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes test files and manual evidence documents to ensure they are thorough, correctly scoped, and ready for QA sign-off, not merely present.

Core Features & Use Cases

Automated assessment of assertion coverage, edge-case handling, and naming quality for unit and integration tests.
Review of manual evidence with sign-offs and artefact completeness.
Scope-aware evaluation across single stories, sprints, or entire systems.

Quick Start

Run this skill to generate a comprehensive quality assessment for test evidence related to a given story.

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema

How do I review test evidence and QA artifacts for sprint readiness?▼

You can review test evidence by running an automated assessment that analyzes test files and manual artifacts for assertion coverage, edge-case handling, naming quality, and sign-off completeness. It evaluates scope across single stories, sprints, or entire systems to confirm evaluation criteria are thoroughly met.

What is assertion coverage and how does it impact QA sign-offs?▼

Assertion coverage measures the presence and quality of validation statements within test files. It impacts QA sign-offs by verifying that test evidence is thorough, correctly scoped, and actively asserts expected behaviors rather than merely executing code without validating outcomes.

Can I audit test evidence for an entire system or just a single story?▼

You can audit test evidence at multiple scopes. This skill applies scope-aware evaluation to single stories, current sprints, or entire systems, generating a comprehensive quality assessment that reports on edge cases, naming quality, and sign-off completeness for the selected scope.

How do I assess edge-case handling in unit and integration tests?▼

Assessing edge-case handling requires analyzing test files to identify whether boundary conditions and unexpected inputs are covered. This skill automates that review by evaluating test evidence to ensure edge cases are explicitly addressed alongside standard assertion coverage before sign-off.

What's the best way to check manual evidence and artifact completeness for QA?▼

The best way to check manual evidence completeness is to review artifacts for required sign-offs and documentation scope. This skill evaluates manual evidence documents to ensure they are thorough, correctly scoped, and ready for QA sign-off rather than just confirming their presence.

Why does my test evidence pass execution but fail QA story audit sign-offs?▼

Test evidence can pass execution but fail sign-offs when assertion coverage is insufficient, edge cases are unhandled, or naming quality is poor. A story audit evaluates whether evidence is thorough and correctly scoped, ensuring required sign-offs and evaluation criteria are fully met.