Testing Strategy
This skill designs effective testing strategies, balancing coverage, speed, and maintenance. It helps users create test plans, choose appropriate test types.
Install
npx promptshop add testing-strategyDetails
What This Skill Does
This skill designs effective testing strategies, balancing coverage, speed, and maintenance. It helps users create test plans, choose appropriate test types for different components, and set coverage targets. It is useful for QA engineers, developers, and test leads.
When to Use
- Design a testing strategy for a project.
- Select appropriate test types.
- Set coverage targets.
- Identify gaps in existing coverage.
- Create example test cases.
- Balance coverage, speed, and maintenance.
Key Features
- Applies the testing pyramid concept.
- Suggests strategies by component type.
- Focuses on business-critical paths.
- Identifies what to test and what to skip.
- Creates test plans with coverage targets.
- Balances coverage, speed, and maintenance.
Manual Installation
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. 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.