Stats
Actions
Tags
From engineering
Designs test strategies and plans with testing pyramid. Covers APIs, frontend, data pipelines, infrastructure; outputs plans including coverage targets, examples, and gaps.
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 engineeringCreate testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.
Design testing strategies (unit, integration, end-to-end, performance) that catch bugs without creating bottlenecks. Use when scaling testing or improving release confidence.
Guides test pyramid structure, coverage targets, and patterns for unit, integration, and E2E tests. Includes AAA pattern, naming conventions, and API test checklist.