QA Test Planner
Quick Reference
| Task |
What You Get |
Time |
| Test Plan |
Strategy, scope, schedule, risks |
10-15 min |
| Test Cases |
Step-by-step instructions, expected results |
5-10 min each |
| Regression Suite |
Smoke tests, critical paths, execution order |
15-20 min |
| Figma Validation |
Design-implementation comparison |
10-15 min |
| Bug Report |
Reproducible steps, environment, evidence |
5 min |
Test Case Format
## TC-001: [Test Case Title]
**Priority:** High | Medium | Low
**Type:** Functional | UI | Integration | Regression
### Preconditions
- [Setup requirement]
### Test Steps
1. [Action]
**Expected:** [Result]
2. [Action]
**Expected:** [Result]
Bug Report Template
# BUG-[ID]: [Clear, specific title]
**Severity:** Critical | High | Medium | Low
## Environment
- OS, Browser, Build, URL
## Steps to Reproduce
1. [Step]
2. [Step]
## Expected Behavior
[What should happen]
## Actual Behavior
[What happens]
## Evidence
- Screenshot, console errors
Severity Definitions
| Level |
Criteria |
Examples |
| Critical (P0) |
System crash, data loss, security |
Payment fails, login broken |
| High (P1) |
Major feature broken, no workaround |
Search not working |
| Medium (P2) |
Feature partial, workaround exists |
Filter missing option |
| Low (P3) |
Cosmetic, rare edge cases |
Typo, minor alignment |
Regression Suite Types
| Suite |
Duration |
When |
| Smoke |
15-30 min |
Daily |
| Targeted |
30-60 min |
Per change |
| Full |
2-4 hours |
Weekly/Release |
| Sanity |
10-15 min |
After hotfix |
Pass/Fail Criteria
PASS: All P0 pass, 90%+ P1 pass, no critical bugs open
FAIL: Any P0 fails, critical bug, security vulnerability
Best Practices
- Be specific and unambiguous in test steps
- Include expected results for each step
- Test one thing per test case
- Provide clear reproduction steps in bug reports
- Include screenshots/videos as evidence
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: qa-test-planner3description: QA test planning patterns. Use when creating test plans, writing test cases, building regression suites, validating designs against Figma, or documenting bugs. Use when this capability is needed.4---56# QA Test Planner78## Quick Reference910| Task | What You Get | Time |11|------|-------------|------|12| Test Plan | Strategy, scope, schedule, risks | 10-15 min |13| Test Cases | Step-by-step instructions, expected results | 5-10 min each |14| Regression Suite | Smoke tests, critical paths, execution order | 15-20 min |15| Figma Validation | Design-implementation comparison | 10-15 min |16| Bug Report | Reproducible steps, environment, evidence | 5 min |1718## Test Case Format1920```markdown21## TC-001: [Test Case Title]2223**Priority:** High | Medium | Low24**Type:** Functional | UI | Integration | Regression2526### Preconditions27- [Setup requirement]2829### Test Steps301. [Action]31 **Expected:** [Result]32332. [Action]34 **Expected:** [Result]35```3637## Bug Report Template3839```markdown40# BUG-[ID]: [Clear, specific title]4142**Severity:** Critical | High | Medium | Low4344## Environment45- OS, Browser, Build, URL4647## Steps to Reproduce481. [Step]492. [Step]5051## Expected Behavior52[What should happen]5354## Actual Behavior55[What happens]5657## Evidence58- Screenshot, console errors59```6061## Severity Definitions6263| Level | Criteria | Examples |64|-------|----------|----------|65| Critical (P0) | System crash, data loss, security | Payment fails, login broken |66| High (P1) | Major feature broken, no workaround | Search not working |67| Medium (P2) | Feature partial, workaround exists | Filter missing option |68| Low (P3) | Cosmetic, rare edge cases | Typo, minor alignment |6970## Regression Suite Types7172| Suite | Duration | When |73|-------|----------|------|74| Smoke | 15-30 min | Daily |75| Targeted | 30-60 min | Per change |76| Full | 2-4 hours | Weekly/Release |77| Sanity | 10-15 min | After hotfix |7879## Pass/Fail Criteria8081**PASS:** All P0 pass, 90%+ P1 pass, no critical bugs open82**FAIL:** Any P0 fails, critical bug, security vulnerability8384## Best Practices8586- Be specific and unambiguous in test steps87- Include expected results for each step88- Test one thing per test case89- Provide clear reproduction steps in bug reports90- Include screenshots/videos as evidence9192---93> Converted and distributed by [TomeVault](https://tomevault.io/claim/arvoreeducacao) — claim your Tome and manage your conversions.94<!-- tomevault:4.0:skill_md:2026-04-13 -->