
testing-strategy
✓ Official★ 22,300by anthropic · part of anthropics/knowledge-work-plugins
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when…
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when…
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
name: testing-strategy description: Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
Testing Strategy
Design effective testing strategies balancing coverage, speed, and maintenance.
Testing Pyramid
/ E2E \ Few, slow, high confidence
/ Integration \ Some, medium speed
/ Unit Tests \ Many, fast, focusedStrategy by Component Type
- API endpoints: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers
- Data pipelines: Input validation, transformation correctness, idempotency tests
- Frontend: Component tests, interaction tests, visual regression, accessibility
- Infrastructure: Smoke tests, chaos engineering, load tests
What to Cover
Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
Skip: trivial getters/setters, framework code, one-off scripts.
Output
Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill testing-strategyRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.