Test Pyramid Design
Design test pyramid architecture balancing unit, integration, and E2E tests. Use when establishing test level distribution and automation strategy.
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-pyramid-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/qa-engineer/test-strategy/skills/test-pyramid-design ~/.claude/skills/test-pyramid-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Pyramid Design Structure test automation across levels to maximize speed, reliability, and cost-efficiency. ## Context You are a senior QA engineer designing test pyramid architecture for $ARGUMENTS. The pyramid guides investment decisions across unit, integration, and end-to-end testing. ## Domain Context - **Test pyramid** (Mike Cohn) emphasizes many fast unit tests (base), fewer integration tests (middle), and few slow E2E tests (top) - Typical pyramid ratio: 70% unit, 20% integration, 10% E2E (varies by architecture and risk profile) - Inverted pyramid (many E2E, few unit tests) leads to slow feedback, high maintenance, and brittle suites - Test types differ: unit tests validate units in isolation; integration tests validate component interactions; E2E tests validate end-user workflows ## Instructions 1. **Understand Application Architecture**: Analyze system design (monolith, microservices, frontend/backend separation, API-driven). Architecture determines pyramid shape: monoliths favor unit tests; distributed systems require more integration/contract tests. 2. **Define Test Level Boundaries**: Determine what constitutes unit (single class/function, mocked dependencies), integration (multiple components, real databases), and E2E (complete user workflow, production-like environment). Clear boundaries prevent overlap and confusion.
Details
- Skill name
test-pyramid-design- Repository
- sethdford/claude-skills
- Path
qa-engineer/test-strategy/skills/test-pyramid-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Test Pyramid Design skill do?
Design test pyramid architecture balancing unit, integration, and E2E tests. Use when establishing test level distribution and automation strategy.
How do I install the Test Pyramid Design 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 Pyramid Design 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 Scenario
48sethdford/claude-skills
Write usability test scenarios with tasks, success criteria, and observation guides.
Test Plan Review
48sethdford/claude-skills
Expert approach to test-plan-review in QA operations. Use when working with .
Test Strategy
48sethdford/claude-skills
Create testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.