From engineering
Designs test strategies and test plans covering unit, integration, and E2E tests across API, data, frontend, and infrastructure components.
How this skill is triggered — by the user, by Claude, or both
Slash command
/engineering:testing-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design effective testing strategies balancing coverage, speed, and maintenance.
Design effective testing strategies balancing coverage, speed, and maintenance.
/ E2E \ Few, slow, high confidence
/ Integration \ Some, medium speed
/ Unit Tests \ Many, fast, focused
Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
Skip: trivial getters/setters, framework code, one-off scripts.
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 claudepluginhub anthropics/knowledge-work-plugins --plugin engineering3plugins reuse this skill
First indexed Jun 13, 2026
Provides test design patterns, coverage strategies (80-100% targets), types (unit/integration/E2E), organization, and best practices for comprehensive test suites. Use for new suites, coverage improvement, or test design.
Guides test pyramid structure, coverage targets, and patterns for unit, integration, and E2E tests. Includes AAA pattern, naming conventions, and API test checklist.
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".