Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

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: Generate test cases: Build regression suite: Validate against Figma: Create bug report: 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 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 Test Types Type Focus Example Functional Business logic Login with valid credentials UI/Visual Appearance, layout Button matches Figma design Integration Component interaction API returns data to frontend Regression Existing functionality Previous features still work Performance Speed, load handling Page loads under 3 seconds Security Vulnerabilities SQL injection prevented </details <details <summary <strong Deep Dive: Test Plan Template</strong </summary Test Plan Structure </details <details <summary <strong Deep Dive: Bug Reporting</strong </summary Bug Report Template 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 one option Low (P3) Cosmetic, rare edge cases Typo, minor alignment </details <details <summary <strong Deep Dive: Figma MCP Integration</strong </summary Design Validation Workflow Prerequisites: Figma MCP server configured Access to Figma design files Figma URLs for components/pages Process: 1. Get Design Specs from Figma 2. Compare Implementation 3. Create Bug if Mismatch What to Validate Element What to Check Tool Colors Hex values exact Browser color picker Spacing Padding/margin px DevTools computed styles Typography Font, size, weight DevTools font panel Layout Width, height, position DevTools box model States Hover, active, focus Manual interaction Responsive Breakpoint behavior DevTools device mode Example Queries </details <details <summary <strong Deep Dive: Regression Testing</strong </summary Suite Structure Suite Type Duration Frequency Coverage Smoke 15 30 min Daily Critical paths only Targeted 30 60 min Per change Affected areas Full 2 4 hours Weekly/Release Comprehensive Sanity 10 15 min After hotfix Quick validation Building a Regression Suite Step 1: Identify Critical Paths What can users NOT live without? What generates revenue? What handles sensitive data? What's used most frequently? Step 2: Prioritize Test Cases Priority Description Must Run P0 Business critical, security Always P1 Major features, common flows Weekly+ P2 Minor features, edge cases Releases Step 3: Execution Order 1. Smoke first if fails, stop and fix build 2. P0 tests next must pass before proceeding 3. P1 then P2 track all failures 4. Exploratory find unexpected issues Pass/Fail Criteria PASS: All P0 tests pass 90%+ P1 tests pass No critical bugs open FAIL (Block Release): Any P0 test fails Critical bug discovered Security vulnerability Data loss scenario CONDITIONAL: P1 failures with workarounds Known issues documented Fix plan in place </details <details <summary <strong Deep Dive: Test Execution Tracking</strong </summary Test Run Report Template Coverage Tracking </details <details <summary <strong QA Process Workflow</strong </summary Phase 1: Planning [ ] Review requirements and designs [ ] Create test plan [ ] Identify test scenarios [ ] Estimate effort and timeline [ ] Set up test environment Phase 2: Test Design [ ] Write test cases [ ] Review test cases with team [ ] Prepare test data [ ] Build regression suite [ ] Get Figma design access Phase 3: Execution [ ] Execute test cases [ ] Log bugs with clear steps [ ] Validate against Figma (UI tests) [ ] Track test progress [ ] Communicate blockers Phase 4: Reporting [ ] Compile test results [ ] Analyze coverage [ ] Document risks [ ] Provide go/no go recommendation [ ] Archive test artifacts </details <details <summary <strong Best Practices</strong </summary Test Case Writing DO: Be specific and unambiguous Include expected results for each step Test one thing per test case Use consistent naming conventions Keep test cases maintainable DON'T: Assume knowledge Make test cases too long Skip preconditions Forget edge cases Leave expected results vague Bug Reporting DO: Provide clear reproduction steps Include screenshots/videos Specify exact environment details Describe impact on users Link to Figma for UI bugs DON'T: Report without reproduction steps Use vague descriptions Skip environment details Forget to assign priority Duplicate existing bugs Regression Testing DO: Automate repetitive tests when possible Maintain regression suite regularly Prioritize critical paths Run smoke tests frequently Update suite after each release DON'T: Skip regression before releases Let suite become outdated Test everything every time Ignore failed regression tests </details Examples <details <summary <strong Example: Login Flow Test Case</strong </summary </details <details <summary <strong Example: Responsive Design Test Case</strong </summary </details "Testing shows the presence, not the absence of bugs." Edsger Dijkstra "Quality is not an act, it is a habit." Aristotle

qa-test-planner