---
name: software-test-planning
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.
license: Apache-2.0
metadata:
author: Anthropic
source: anthropics/knowledge-work-plugins/engineering/skills/testing-strategy
source_url: https://github.com/anthropics/knowledge-work-plugins/blob/8f8779a1681ea2f8dc697a6b3063d5e3e7f7460c/engineering/skills/testing-strategy/SKILL.md
upstream-commit: 8f8779a1681ea2f8dc697a6b3063d5e3e7f7460c
original-name: testing-strategy
packaged-by: AutoGPT
packaged-on: '2026-09-25'
---
> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.
# 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, focused
```
## Strategy 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.