From qa-lead
Define a test strategy for a feature, service, or system. Determines what to test, at what level, with what tools, and what quality gates to enforce.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qa-lead:test-strategyThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Define a comprehensive test strategy for $ARGUMENTS.
Define a comprehensive test strategy for $ARGUMENTS.
Before writing a single test plan:
/ E2E \ Few, slow, expensive — critical flows only
/----------\
/ Integration \ Moderate — component boundaries, API contracts
/--------------\
/ Unit Tests \ Many, fast, cheap — logic, pure functions
/------------------\
Default allocation: 70% unit, 20% integration, 10% E2E. Adjust based on risk.
| Level | What it tests | Tools | Coverage target |
|---|---|---|---|
| Unit | Functions, business logic, transformations | Vitest / xUnit / pytest | 80%+ changed code |
| Integration | Boundaries, database, API endpoints, handlers | Alba+Testcontainers / Supertest | Critical paths |
| E2E | Complete user flows through UI | Playwright / Cypress | Top 5-10 flows |
| Contract | API compatibility producer↔consumer | Pact / OpenAPI validation | All public APIs |
| Performance | Latency p50/p95/p99, throughput | k6 / Locust | SLA benchmarks |
| Security | OWASP, auth/authz, input validation | SAST / security-review skill | Public-facing code |
Not every feature needs all levels. A utility function needs unit tests. A payment flow needs all six.
vi.hoisted() + vi.mock() for module-level mocksvi.stubGlobal() for DOM APIs, clean up in afterEachCI=true npx vitest run@vitest/coverage-v8 with lcovWhenDoingSomething| Anti-Pattern | Fix |
|---|---|
| Testing implementation, not behaviour | Test what the system DOES |
| Mocking everything | Real implementations; mock only external boundaries |
| Happy path only | Test error cases, edge cases, boundaries |
sleep() in tests | Proper async waiting or mocked time |
| Flaky tests tolerated | Fix immediately or delete |
## Test Strategy: [name]
### Risk Assessment
- Risk profile: [financial/data/reputation/convenience]
- Critical flows: [list]
- Failure modes: [list]
### Test Levels
| Level | Scope | Tools | Coverage | Est. Tests |
|---|---|---|---|---|
### Quality Gates
[Pre-merge + pre-release checklists]
### Gaps
[Currently untested areas]
### Recommendations
[Prioritised improvements]
/qa-engineer:generate-tests — generate individual tests based on this strategy. Define strategy first, then generate tests./qa-engineer:write-bug-report — for documenting defects found during test execution.Use the test strategy template (templates/test-strategy.md) for consistent output structure.
npx claudepluginhub hpsgd/turtlestack --plugin qa-leadProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.