Testing Strategy
- 5k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
testing-strategy is an agent skill that designs balanced test plans with pyramid guidance, component-specific strategies, and coverage targets.
About
The testing-strategy skill helps agents design effective testing approaches that balance coverage, speed, and maintenance cost. It applies the testing pyramid with many fast unit tests, some integration tests, and few slow E2E tests. Strategy guidance varies by component type: API endpoints need business-logic unit tests plus HTTP integration and consumer contract tests; data pipelines need validation, transformation correctness, and idempotency checks; frontend work covers component, interaction, visual regression, and accessibility tests; infrastructure targets smoke, chaos, and load tests. Focus areas include business-critical paths, error handling, edge cases, security boundaries, and data integrity while skipping trivial getters, framework code, and one-off scripts. Output is a structured test plan listing what to test, test types per area, coverage targets, and example cases plus gaps in existing coverage. Trigger when users ask how to test, request a test plan, or need test architecture guidance.
- Testing pyramid guidance: many unit, some integration, few E2E for confidence versus speed.
- Component-specific strategies for APIs, data pipelines, frontend, and infrastructure.
- Focus on business-critical paths, errors, edge cases, security boundaries, and data integrity.
- Explicit skip list for trivial getters, framework code, and one-off scripts.
- Produces test plans with types, coverage targets, example cases, and gap identification.
Testing Strategy by the numbers
- 4,952 all-time installs (skills.sh)
- +235 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #273 of 2,184 Testing & QA skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
testing-strategy capabilities & compatibility
- Capabilities
- testing pyramid strategy by component type · coverage focus and skip guidance · structured test plan output with examples · gap identification in existing coverage · api pipeline frontend and infra test patterns
- Use cases
- testing · planning
What testing-strategy says it does
Design effective testing strategies balancing coverage, speed, and maintenance.
Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill testing-strategyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
How should we test this feature and what test types and coverage targets do we need?
Design balanced test strategies and test plans covering unit, integration, E2E, and component-specific coverage targets.
Who is it for?
Teams planning test coverage before implementation or release with pyramid-balanced strategies.
Skip if: Skip when you need hands-on test code generation only without strategy or architecture planning.
When should I use this skill?
User asks how should we test, test strategy for, write tests for, test plan, or what tests do we need.
What you get
A structured test plan with areas, test types, coverage targets, example cases, and identified gaps.
- Test plan document
- Coverage target recommendations
- Example test case list
By the numbers
- Testing pyramid: unit integration E2E
- Component strategies for API pipeline frontend infra
- Outputs coverage targets and gap list
Files
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.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.510k185k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.176k260kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.164k185kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.151k185kWebapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.121k164k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.96.3k12.2kHow it compares
testing-strategy designs balanced test plans with pyramid guidance, not hands-on test code generation alone.
FAQ
Who is testing-strategy for?
Developers and QA engineers planning balanced test coverage across unit, integration, and E2E layers.
When should I use testing-strategy?
When designing test plans, choosing test types, or identifying coverage gaps before or during implementation.
Is testing-strategy safe to install?
Review the Security Audits panel on this page before installing in production.