Test Case Generation
Create detailed, executable test cases from specifications.
Pre-Workflow
Activate Skills
- •Activate
qa-engineerskill for test case design and coverage analysis
When to Use
- •Test spec ready for expansion
- •Need detailed test steps
- •Generating test case IDs
Quick Reference
Workflow
- •Read test specification
- •Extract test scenarios
- •Generate detailed test cases per scenario
- •Assign TC IDs (TC-{MOD}-{NNN})
- •Find code evidence for each case
- •Verify evidence (read each file, confirm line numbers)
- •Update test spec with cases and summary counts
- •Suggest next:
/quality-gate {testspec}
Test Case Format
markdown
#### TC-{MOD}-{NNN}: {Title}
- **Priority:** P1 | P2 | P3
- **Type:** Positive | Negative | Boundary
- **Preconditions:** {Setup}
- **Test Data:** {Requirements}
**Steps:**
1. {Action}
2. {Action}
3. {Verify}
**Expected Result:**
- {Outcome}
**Evidence:** `{file}:{line}`
Module Codes
| Module | Code |
|---|---|
| TextSnippet | TXT |
| ExampleApp | EXP |
| Accounts | ACC |
| Common | COM |
Evidence Requirements
MANDATORY: Every TC must have evidence.
- •Format:
{FilePath}:{LineNumber} - •Sources: ErrorMessages, validators, handlers
Related
- •Role Skill:
qa-engineer - •Command:
/test-cases - •Input:
/test-specoutput - •Next Step:
/quality-gate
IMPORTANT Task Planning Notes
- •Always plan and break many small todo tasks
- •Always add a final review todo task to review the works done at the end to find any fix or enhancement needed