Test Strategy
Create testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill test-strategygit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/testing/skills/test-strategy ~/.claude/skills/test-strategyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Strategy Systematic approach to test planning: pyramid structure (70% unit, 20% integration, 10% E2E), coverage targets (70-80%), and risk-based testing. ## Context You are planning test coverage for a feature. Your role is to: - Design test pyramid: unit (fast, isolated) > integration (slower, real) > E2E (slowest, brittle) - Identify high-risk code needing extra testing - Set realistic coverage targets - Balance speed (fast feedback) vs confidence (comprehensive testing) - Avoid the "test everything" trap Good testing builds confidence, not false security. 100% coverage often means testing trivia instead of business logic. ## Domain Context Based on Martin Fowler, Google Testing, and J.B. Rainsberger: - **Test Pyramid**: Most tests at bottom (unit), fewer at middle (integration), few at top (E2E) - **Coverage Target**: 70-80% code coverage sufficient; 100% is waste - **Business Value**: Test what users care about; not every code path - **High-Risk Code**: Auth, payment, data integrity → extra testing - **Speed**: Unit tests <100ms; integration <1s; E2E <10s each ## When to Use This Skill - Planning tests for a new feature - Adding tests to existing codebase - Auditing test coverage (too little or too much) - Improving test speed (too slow) - Preparing for high-risk deployments ## Prerequisites - Understand feature requirements and acceptance criteria - Know the domain (what's valuable to test vs trivial) - Have testing tools/frameworks available
Details
- Skill name
test-strategy- Repository
- sethdford/claude-skills
- Path
engineer/testing/skills/test-strategy/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Test Strategy skill do?
Create testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.
How do I install the Test Strategy skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Strategy popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Test Strategy Design
48sethdford/claude-skills
Design comprehensive test strategies aligned with project goals, risks, and constraints. Use when planning testing efforts for new projects or major releases.
Test Scenario
48sethdford/claude-skills
Write usability test scenarios with tasks, success criteria, and observation guides.
Unit Test Design
48sethdford/claude-skills
Single-unit tests, isolation via mocks/stubs, Arrange-Act-Assert pattern, one assertion per test.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.