Test Case Review: Find coverage gaps, ambiguous assertions, and high-risk scenarios
Having many test cases does not mean they cover the right things. A core journey may be written three times while refund is untouched; a precondition may be impossible to prepare, and an expected result may say only “displays correctly.” These problems slow execution, but case count often hides them.
The Test Case Review Skill does not rewrite an entire suite. It identifies the specific defect that affects execution or coverage: which risk is absent, which step is duplicated, and which assertion is vague. Every finding includes a location, impact, and practical revision so the review can return to the original case.
Using order-case review, this guide shows how to identify coverage gaps, duplicated steps, impossible preconditions, and vague expectations, then verify that the fixes work.
Awesome QA Skills organizes Skills by language and testing stage. The series overview covers repository structure and shared installation options; this guide stays with Test Case Review.
Read the source Skill first
The main prompt covers Quality Bar, Workflow, Core Constraints, Progressive Disclosure, Pre-delivery Checklist. Those headings are navigation; the project artifacts still provide the facts.
The source directory contains 18 script entries. Start with Template conversion script.
Findings need a location
Review order cases for coverage gaps, duplicated steps, impossible preconditions, and vague expectations
“This could be better” gives the author nothing to act on.
| Severity | Location | Finding | Fix |
|---|---|---|---|
| P1 | Input contract | Source priority is undefined | Add conflict and degradation rules |
| P2 | Output contract | Conclusions have no evidence field | Add source, status, and owner |
Every finding needs a location, impact, and practical fix. Otherwise it is review noise.
Compare one finding before and after revision
For Review order cases for coverage gaps, duplicated steps, impossible preconditions, and vague expectations, the first draft often contains a broad quality request.
Before: Check output quality and make the result accurate and complete.
After: Every conclusion carries source, status, and owner.
Use assumption when no source exists. Do not use passed without a run record.The second contract is testable. During a Quality Bar and Workflow review, also inspect trigger overlap, degraded behavior for missing input, and examples that imply execution without evidence.
| Recheck | Method | Passing signal |
|---|---|---|
| Trigger | Run positive and neighboring negative requests | Correct activation boundary |
| Contract | Try input with missing fields | Missing facts are named |
| Example | Trace each claim to a source | No invented files or results |
| Scope | Read the diff | Unrelated rules remain untouched |
A prompt you can adapt
Replace the bracketed fields with project facts. Specific material leaves less room for guessing.
Use the test-case-reviewer Skill.
Task: Review order cases for coverage gaps, duplicated steps, impossible preconditions, and vague expectations
Version and environment: [requirement / build / environment]
Inputs: [file paths or links]
Scope: [included and excluded journeys]
Constraints: [accounts, data, time, compliance]
Give location, severity, impact, and a proposed edit for every finding. Separate contract gaps, factual defects, and preference; include a recheck method.
Finish with open questions. Do not invent missing facts.Use the first pass to inspect structure and gaps. Supply missing material before asking for the handoff-ready artifact.
Advanced use, from one call to a maintained flow
Turn representative findings into regression examples. After a Test Case Review edit, run expected-pass, expected-reject, and missing-input checks.
A three-Skill chain
test-case-writing → test-case-reviewer → test-reporting
| Handoff | Payload | Receiver check |
|---|---|---|
| Upstream to test-case-reviewer | Source versions, scope, risks, open questions | Test Case Review staleness and conflicts |
| test-case-reviewer to downstream | Primary artifact, evidence index, unfinished work | Test Case Review executability and owners |
| Feedback to test-case-reviewer | Runs, defects, new risks | Test Case Review baseline and regression update |
Do not paste three complete outputs into one large prompt. Give Test Case Review a structured summary and accessible source artifacts. It saves context and makes defects traceable.
Team gates
| Gate | Check | Failure action |
|---|---|---|
| test-case-reviewer input | Version, environment, owner, accessible sources | Stop Test Case Review and list gaps |
| test-case-reviewer artifact | Material claims carry basis and status | Return Test Case Review for evidence |
| test-case-reviewer execution | Command, exit status, report are reproducible | Classify infrastructure or test failure |
| test-case-reviewer decision | Residual risks have accepter and date | Do not enter the next stage |
Review Test Case Review adoption, human edit rate, unsupported claims, and failure-to-diagnosis time each sprint. Record a baseline for several cycles before setting targets.
Keep the original text and evidence in the review
Quote a location before describing the problem. Separate contract gaps, wording defects, and personal preference. Findings related to Quality Bar should explain the behavioral drift they can cause. Recheck behavior after the edit.
Install and invoke
Install the individual Skill. The series overview carries the longer installation explanation.
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/test-case-reviewer -gInvoke it with “Use the test-case-reviewer Skill,” then attach the real artifacts.
Two practical questions
Must every review finding be accepted?
No. Use severity and contract impact. A preference can be declined if the choice is recorded.
Does shorter prose mean a better Skill?
No. Triggers, inputs, outputs, and risk boundaries still need to survive the edit.
When is human review mandatory?
Require an accountable person for scope trade-offs, risk acceptance, release decisions, and source conflicts.
What should be archived?
Keep the input version, Skill output, human edits, and final evidence so the conclusion can be reconstructed.
Run Test Case Review against one real artifact and keep the input, output, and review notes. The fragments here establish structure; project evidence must still come from the project.
References
- Awesome QA Skills project:https://github.com/naodeng/awesome-qa-skills
- Awesome QA Skills series overview:https://inaodeng.com/en/blog/ai-testing/introduction_of_awesome_qa_skills/
- Test Case Review helper script: batch_convert_templates.py:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/test-case-reviewer/scripts/batch_convert_templates.py
- Awesome QA Skills: Test Case Review Skill source:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/test-case-reviewer
- Test Case Review Skill details:https://inaodeng.com/en/qaskills/test-case-reviewer/