/qa-test-planner

name: qa-test-planner
description: Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
trigger: explicit

QA Test Planner

A comprehensive skill for QA engineers to create test plans, generate manual test cases, build regression test suites, validate designs against Figma, and document bugs effectively.

> **Activation:** This skill is triggered only when explicitly called by name (e.g., `/qa-test-planner`, `qa-test-planner`, or `use the skill qa-test-planner`).

---

Quick Start

**Create a test plan:**

"Create a test plan for the user authentication feature"

**Generate test cases:**

"Generate manual test cases for the checkout flow"

**Build regression suite:**

"Build a regression test suite for the payment module"

**Validate against Figma:**

"Compare the login page against the Figma design at [URL]"

**Create bug report:**

"Create a bug report for the form validation issue"

---

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, discrepancy list | 10-15 min | | Bug Report | Reproducible steps, environment, evidence | 5 min |

---

How It Works

Your Request
    │
    ▼
┌─────────────────────────────────────────────────────┐
│ 1. ANALYZE                                          │
│    • Parse feature/requirement                      │
│    • Identify test types needed                     │
│    • Determine scope and priorities                 │
├─────────────────────────────────────────────────────┤
│ 2. GENERATE                                         │
│    • Create structured deliverables                 │
│    • Apply templates and best practices             │
│    • Include edge cases and variations              │
├─────────────────────────────────────────────────────┤
│ 3. VALIDATE                                         │
│    • Check completeness                             │
│    • Verify traceability                            │
│    • Ensure actionable steps                        │
└─────────────────────────────────────────────────────┘
    │
    ▼
QA Deliverable Ready

---

Commands

Interactive Scripts

| Script | Purpose | Usage | |--------|---------|-------| | `./scripts/generate_test_cases.sh` | Create test cases interactively | Step-by-step prompts | | `./scripts/create_bug_report.sh` | Generate bug reports | Guided input collection |

Natural Language

| Request | Output | |---------|--------| | "Create test plan for {feature}" | Complete test plan document | | "Generate {N} test cases for {feature}" | Numbered test cases with steps | | "Build smoke test suite" | Critical path tests | | "Compare with Figma at {URL}" | Visual validation checklist | | "Document bug: {description}" | Structured bug report |

---

Core Deliverables

1. Test Plans

• Test scope and objectives
• Testing approach and strategy
• Environment requirements
• Entry/exit criteria
• Risk assessment
• Timeline and milestones

2. Manual Test Cases

• Step-by-step instructions
• Expected vs actual results
• Preconditions and setup
• Test data requirements
• Priority and severity

3. Regression Suites

• Smoke tests (15-30 min)
• Full regression (2-4 hours)
• Targeted regression (30-60 min)
• Execution order and dependencies

4. Figma Validation

• Component-by-component comparison
• Spacing and typography checks
• Color and visual consistency
• Interactive state validation

5. Bug Reports

• Clear reproduction steps
• Environment details
• Evidence (screenshots, logs)
• Severity and priority

---

Anti-Patterns

| Avoid | Why | Instead | |-------|-----|---------| | Vague test steps | Can't reproduce | Specific actions + expected results | | Missing preconditions | Tests fail unexpectedly | Document all setup requirements | | No test data | Tester blocked | Provide sample data or generation | | Generic bug titles | Hard to track | Specific: "[Feature] issue when [action]" | | Skip edge cases | Miss critical bugs | Include boundary values, nulls |

---

Verification Checklist

**Test Plan:**

• [ ] Scope clearly defined (in/out)
• [ ] Entry/exit criteria specified
• [ ] Risks identified with mitigations
• [ ] Timeline realistic

**Test Cases:**

• [ ] Each step has expected result
• [ ] Preconditions documented
• [ ] Test data available
• [ ] Priority assigned

**Bug Reports:**

• [ ] Reproducible steps
• [ ] Environment documented
• [ ] Screenshots/evidence attached
• [ ] Severity/priority set

---

References

• [Test Case Templates](references/test_case_templates.md) - Standard formats for all test types
• [Bug Report Templates](references/bug_report_templates.md) - Documentation templates
• [Regression Testing Guide](references/regression_testing.md) - Suite building and execution
• [Figma Validation Guide](references/figma_validation.md) - Design-implementation validation

---

<details> <summary><strong>Deep Dive: Test Case Structure</strong></summary>

Standard Test Case Format

## TC-001: [Test Case Title]

**Priority:** High | Medium | Low
**Type:** Functional | UI | Integration | Regression
**Status:** Not Run | Pass | Fail | Blocked

### Objective
[What are we testing and why]

### Preconditions
- [Setup requirement 1]
- [Setup requirement 2]
- [Test data needed]

### Test Steps
1. [Action to perform]
   **Expected:** [What should happen]

2. [Action to perform]
   **Expected:** [What should happen]

3. [Action to perform]
   **Expected:** [What should happen]

### Test Data
- Input: [Test data values]
- User: [Test account details]
- Configuration: [Environment set