From product-design
Applies QA test design patterns like equivalence partitioning, boundary value analysis, happy paths, edge cases, permissions, accessibility checklists, and prioritization for test cases and coverage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-design:qa-testing-methodologyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply proven test design patterns for comprehensive test coverage.
Apply proven test design patterns for comprehensive test coverage.
Always design tests in this order:
Divide input data into partitions where all values should behave identically.
| Partition | Values | Expected Behavior |
|---|---|---|
| Below minimum | 0-17 | Reject with "Must be 18+" |
| Valid range | 18-65 | Accept |
| Above maximum | 66+ | Reject with "Maximum age is 65" |
| Invalid | -1, "abc", empty | Reject with validation error |
Test Strategy: Test ONE value from each partition, not every value.
Focus testing on boundaries where behavior changes.
| Boundary | Test Values | Expected |
|---|---|---|
| Just below minimum | 7 chars | Reject |
| At minimum | 8 chars | Accept |
| Just above minimum | 9 chars | Accept |
| Just below maximum | 19 chars | Accept |
| At maximum | 20 chars | Accept |
| Just above maximum | 21 chars | Reject |
Prioritize tests based on risk and frequency:
| Priority | Risk | User Impact | Test Frequency |
|---|---|---|---|
| Critical | Data loss, security breach | All users blocked | Every build |
| High | Feature broken | Major workflow impacted | Every release |
| Medium | Inconvenient | Workaround available | Weekly |
| Low | Minor annoyance | Cosmetic issues | Monthly |
Include in every test procedure:
Note performance during manual testing:
| Metric | Acceptable | Needs Investigation |
|---|---|---|
| Page load | < 3 seconds | > 3 seconds |
| Button response | < 100ms | > 300ms |
| Form submission | < 2 seconds | > 5 seconds |
| Search results | < 1 second | > 2 seconds |
Email: [email protected]
Password: Test@1234! (in password manager)
Phone: +1-555-0100 (test range)
Credit Card: 4111-1111-1111-1111 (test card)
Address: 123 Test Street, Test City, TS 12345
When to run regression tests:
| Trigger | Regression Scope |
|---|---|
| Bug fix | Related feature + integration points |
| New feature | All features that share data/UI |
| Dependency update | Full regression |
| Release candidate | Critical + High priority tests |
Test all valid state transitions:
Example: Order Status
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌───────────┐
│ Created │ ──▶ │ Pending │ ──▶ │ Shipped │ ──▶ │ Delivered │
└─────────┘ └─────────┘ └─────────┘ └───────────┘
│ │
▼ ▼
┌───────────┐ ┌────────────┐
│ Cancelled │ │ Returned │
└───────────┘ └────────────┘
Test:
Check error messages for:
| Bad | Good |
|---|---|
| "Error 500" | "Something went wrong. Please try again." |
| "Invalid input" | "Email must be in format: [email protected]" |
| "User not found in database" | "No account found with this email" |
| "Password must match regex..." | "Password needs 8+ characters with a number" |
Minimum browser coverage:
| Browser | Desktop | Mobile |
|---|---|---|
| Chrome | Latest, Latest-1 | Android |
| Safari | Latest | iOS |
| Firefox | Latest | - |
| Edge | Latest | - |
Bad: Click the button Good: Click the blue "Submit" button in the bottom-right of the form
Bad: Enter your details Good: Enter "[email protected]" in the Email field
Bad: Verify it works Good: Verify success message "Order placed successfully" appears
npx claudepluginhub jpoutrin/product-forge --plugin product-designGenerates test plans, manual test cases, regression suites, bug reports, and Figma design validations for QA engineers.
Design systematic test cases covering valid inputs, invalid inputs, and edge cases. Use when creating manual test suites.
Generates ISTQB CTFL-aligned QA artifacts like test plans, cases, bug reports, traceability matrices, and regression suites. Supports test design techniques, risk-based testing, and Playwright automation.