Qa Test Planner

by softaworks3027f20f3181No license2.5K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

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

Includes scriptsSoftware Development
AI-generated overview

Generates QA test plans, manual test cases, regression suites, Figma design validations and bug reports.

What it does
Produces structured QA deliverables: test plans with scope, strategy, entry/exit criteria and risks; step-by-step manual test cases with expected results; regression suites ordered by priority; Figma design-implementation comparisons; and bug reports with reproduction steps and environment details. It ships two interactive shell scripts, one for generating test cases and one for creating bug reports, plus reference templates for test cases, bug reports, regression testing and Figma validation. Output is written documentation rather than executed test code.
When to use it
Use when a QA engineer needs to plan testing for a feature or release, write manual test cases, assemble a regression suite, document a bug, or compare an implementation against a Figma design. It is triggered only when explicitly called by name.
Requirements
Shell environment to run the bundled scripts (scripts/generate_test_cases.sh, scripts/create_bug_report.sh). Figma validation requires a configured Figma MCP server and access to Figma design files and URLs.

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

TaskWhat You GetTime
Test PlanStrategy, scope, schedule, risks10-15 min
Test CasesStep-by-step instructions, expected results5-10 min each
Regression SuiteSmoke tests, critical paths, execution order15-20 min
Figma ValidationDesign-implementation comparison, discrepancy list10-15 min
Bug ReportReproducible steps, environment, evidence5 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

ScriptPurposeUsage
./scripts/generate_test_cases.shCreate test cases interactivelyStep-by-step prompts
./scripts/create_bug_report.shGenerate bug reportsGuided input collection

Natural Language

RequestOutput
"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

AvoidWhyInstead
Vague test stepsCan't reproduceSpecific actions + expected results
Missing preconditionsTests fail unexpectedlyDocument all setup requirements
No test dataTester blockedProvide sample data or generation
Generic bug titlesHard to trackSpecific: "[Feature] issue when [action]"
Skip edge casesMiss critical bugsInclude 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 [blocked] - Standard formats for all test types
  • Bug Report Templates [blocked] - Documentation templates
  • Regression Testing Guide [blocked] - Suite building and execution
  • Figma Validation Guide [blocked] - Design-implementation validation
<details> <summary><strong>Deep Dive: Test Case Structure</strong></summary>

Standard Test Case Format

markdown
## 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 Steps1. [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 settings]
### Post-conditions- [System state after test]- [Cleanup required]
### Notes- [Edge cases to consider]- [Related test cases]- [Known issues]

Test Types

TypeFocusExample
FunctionalBusiness logicLogin with valid credentials
UI/VisualAppearance, layoutButton matches Figma design
IntegrationComponent interactionAPI returns data to frontend
RegressionExisting functionalityPrevious features still work
PerformanceSpeed, load handlingPage loads under 3 seconds
SecurityVulnerabilitiesSQL injection prevented
</details> <details> <summary><strong>Deep Dive: Test Plan Template</strong></summary>

Test Plan Structure

markdown
# Test Plan: [Feature/Release Name]
## Executive Summary- Feature/product being tested- Testing objectives- Key risks- Timeline overview
## Test Scope
**In Scope:**- Features to be tested- Test types (functional, UI, performance)- Platforms and environments- User flows and scenarios
**Out of Scope:**- Features not being tested- Known limitations- Third-party integrations (if applicable)
## Test Strategy
**Test Types:**- Manual testing- Exploratory testing- Regression testing- Integration testing- User acceptance testing
**Test Approach:**- Black box testing- Positive and negative testing- Boundary value analysis- Equivalence partitioning
## Test Environment- Operating systems- Browsers and versions- Devices (mobile, tablet, desktop)- Test data requirements- Backend/API environments
## Entry Criteria- [ ] Requirements documented- [ ] Designs finalized- [ ] Test environment ready- [ ] Test data prepared- [ ] Build deployed
## Exit Criteria- [ ] All high-priority test cases executed- [ ] 90%+ test case pass rate- [ ] All critical bugs fixed- [ ] No open high-severity bugs- [ ] Regression suite passed
## Risk Assessment
| Risk | Probability | Impact | Mitigation ||------|-------------|--------|------------|| [Risk 1] | H/M/L | H/M/L | [Mitigation] |
## Test Deliverables- Test plan document- Test cases- Test execution reports- Bug reports- Test summary report
</details> <details> <summary><strong>Deep Dive: Bug Reporting</strong></summary>

Bug Report Template

markdown
# BUG-[ID]: [Clear, specific title]
**Severity:** Critical | High | Medium | Low**Priority:** P0 | P1 | P2 | P3**Type:** Functional | UI | Performance | Security**Status:** Open | In Progress | Fixed | Closed
## Environment- **OS:** [Windows 11, macOS 14, etc.]- **Browser:** [Chrome 120, Firefox 121, etc.]- **Device:** [Desktop, iPhone 15, etc.]- **Build:** [Version/commit]- **URL:** [Page where bug occurs]
## Description[Clear, concise description of the issue]
## Steps to Reproduce1. [Specific step]2. [Specific step]3. [Specific step]
## Expected Behavior[What should happen]
## Actual Behavior[What actually happens]
## Visual Evidence- Screenshot: [attached]- Video: [link if applicable]- Console errors: [paste errors]
## Impact- **User Impact:** [How many users affected]- **Frequency:** [Always, Sometimes, Rarely]- **Workaround:** [If one exists]
## Additional Context- Related to: [Feature/ticket]- Regression: [Yes/No]- Figma design: [Link if UI bug]

Severity Definitions

LevelCriteriaExamples
Critical (P0)System crash, data loss, securityPayment fails, login broken
High (P1)Major feature broken, no workaroundSearch not working
Medium (P2)Feature partial, workaround existsFilter missing one option
Low (P3)Cosmetic, rare edge casesTypo, 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
"Get the button specifications from Figma file [URL]"
Response includes:- Dimensions (width, height)- Colors (background, text, border)- Typography (font, size, weight)- Spacing (padding, margin)- Border radius- States (default, hover, active, disabled)
  1. Compare Implementation
TC: Primary Button Visual Validation1. Inspect primary button in browser dev tools2. Compare against Figma specs:   - Dimensions: 120x40px   - Border-radius: 8px   - Background color: #0066FF   - Font: 16px Medium #FFFFFF3. Document discrepancies
  1. Create Bug if Mismatch
BUG: Primary button color doesn't match designSeverity: MediumExpected (Figma): #0066FFActual (Implementation): #0052CCScreenshot: [attached]Figma link: [specific component]

What to Validate

ElementWhat to CheckTool
ColorsHex values exactBrowser color picker
SpacingPadding/margin pxDevTools computed styles
TypographyFont, size, weightDevTools font panel
LayoutWidth, height, positionDevTools box model
StatesHover, active, focusManual interaction
ResponsiveBreakpoint behaviorDevTools device mode

Example Queries

"Get button specifications from Figma design [URL]""Compare navigation menu implementation against Figma design""Extract spacing values for dashboard layout from Figma""List all color tokens used in Figma design system"
</details> <details> <summary><strong>Deep Dive: Regression Testing</strong></summary>

Suite Structure

Suite TypeDurationFrequencyCoverage
Smoke15-30 minDailyCritical paths only
Targeted30-60 minPer changeAffected areas
Full2-4 hoursWeekly/ReleaseComprehensive
Sanity10-15 minAfter hotfixQuick 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

PriorityDescriptionMust Run
P0Business-critical, securityAlways
P1Major features, common flowsWeekly+
P2Minor features, edge casesReleases

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

markdown
# Test Run: [Release Version]
**Date:** 2024-01-15**Build:** v2.5.0-rc1**Tester:** [Name]**Environment:** Staging
## Summary- Total Test Cases: 150- Executed: 145- Passed: 130- Failed: 10- Blocked: 5- Not Run: 5- Pass Rate: 90%
## Test Cases by Priority
| Priority | Total | Pass | Fail | Blocked ||----------|-------|------|------|---------|| P0 (Critical) | 25 | 23 | 2 | 0 || P1 (High) | 50 | 45 | 3 | 2 || P2 (Medium) | 50 | 45 | 3 | 2 || P3 (Low) | 25 | 17 | 2 | 1 |
## Critical Failures- TC-045: Payment processing fails  - Bug: BUG-234  - Status: Open
## Blocked Tests- TC-112: Dashboard widget (API endpoint down)
## Risks- 2 critical bugs blocking release- Payment integration needs attention
## Next Steps- Retest after BUG-234 fix- Complete remaining 5 test cases- Run full regression before sign-off

Coverage Tracking

markdown
## Coverage Matrix
| Feature | Requirements | Test Cases | Status | Gaps ||---------|--------------|------------|--------|------|| Login | 8 | 12 | Complete | None || Checkout | 15 | 10 | Partial | Payment errors || Dashboard | 12 | 15 | Complete | None |
</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>
markdown
## TC-LOGIN-001: Valid User Login
**Priority:** P0 (Critical)**Type:** Functional**Estimated Time:** 2 minutes
### ObjectiveVerify users can successfully login with valid credentials
### Preconditions- User account exists ([email protected] / Test123!)- User is not already logged in- Browser cookies cleared
### Test Steps1. Navigate to https://app.example.com/login   **Expected:** Login page displays with email and password fields
2. Enter email: [email protected]   **Expected:** Email field accepts input
3. Enter password: Test123!   **Expected:** Password field shows masked characters
4. Click "Login" button   **Expected:**   - Loading indicator appears   - User redirected to /dashboard   - Welcome message shown: "Welcome back, Test User"   - Avatar/profile image displayed in header
### Post-conditions- User session created- Auth token stored- Analytics event logged
### Edge Cases to Consider- TC-LOGIN-002: Invalid password- TC-LOGIN-003: Non-existent email- TC-LOGIN-004: SQL injection attempt- TC-LOGIN-005: Very long password
</details> <details> <summary><strong>Example: Responsive Design Test Case</strong></summary>
markdown
## TC-UI-045: Mobile Navigation Menu
**Priority:** P1 (High)**Type:** UI/Responsive**Devices:** Mobile (iPhone, Android)
### ObjectiveVerify navigation menu works correctly on mobile devices
### Preconditions- Access from mobile device or responsive mode- Viewport width: 375px (iPhone SE) to 428px (iPhone Pro Max)
### Test Steps1. Open homepage on mobile device   **Expected:** Hamburger menu icon visible (top-right)
2. Tap hamburger icon   **Expected:**   - Menu slides in from right   - Overlay appears over content   - Close (X) button visible
3. Tap menu item   **Expected:** Navigate to section, menu closes
4. Compare against Figma mobile design [link]   **Expected:**   - Menu width: 280px   - Slide animation: 300ms ease-out   - Overlay opacity: 0.5, color #000000   - Font size: 16px, line-height 24px
### Breakpoints to Test- 375px (iPhone SE)- 390px (iPhone 14)- 428px (iPhone 14 Pro Max)- 360px (Galaxy S21)
</details>

"Testing shows the presence, not the absence of bugs." - Edsger Dijkstra

"Quality is not an act, it is a habit." - Aristotle

Source and attribution

Source:softaworks/agent-toolkitinskills/qa-test-plannerat commit3027f20

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from softaworks/agent-toolkit

Writing Clearly And Concisely

softaworks

Applies Strunk's Elements of Style rules and an AI-writing-pattern checklist to make human-facing prose clearer and more concise.

Writing & Content2.5Kupdated 7 months ago

Web To Markdown

softaworks

Converts webpage URLs into clean Markdown using a locally installed web2md CLI with Puppeteer and Readability.

Productivity & Workflow2.5Kupdated 7 months ago

Skill Judge

softaworks

Scores Agent Skill packages against official specifications and best practices, with multi-dimensional ratings and improvement advice.

AI & Agents2.5Kupdated 7 months ago

Ship Learn Next

softaworks

Turns learning content such as transcripts or articles into a Ship-Learn-Next action plan with concrete weekly iterations.

Learning & Education2.5Kupdated 7 months ago

Reducing Entropy

softaworks

Guides an agent to minimize total codebase size by biasing toward deletion and measuring the final code amount.

Software Development2.5Kupdated 7 months ago

Professional Communication

softaworks

Frameworks and templates for professional emails, team chat messages, meeting agendas and audience-adapted technical writing.

Communication2.5Kupdated 7 months ago

More in Software Development

Playground

anthropics

Featured

Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.

Software Development37Kupdated today

M5 Onboard

anthropics

Featured

Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.

Software Development37Kupdated today

Cardputer Buddy

anthropics

Featured

Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.

Software Development37Kupdated today

Web Design Guidelines

vercel-labs

Featured

Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.

Software Development32Kupdated 5 weeks ago

Vercel React Native Skills

vercel-labs

Featured

React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.

Software Development32Kupdated 5 weeks ago

Vercel React Best Practices

vercel-labs

Featured

Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.

Software Development32Kupdated 5 weeks ago