Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Design testing strategies (unit, integration, end-to-end, performance) that catch bugs without creating bottlenecks. Use when scaling testing or improving release confidence.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-engineering-excellenceHow this skill is triggered — by the user, by Claude, or both
Slash command
/engineering-excellence:testing-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build testing pyramids that catch bugs early without slowing down development.
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
Provides test strategy patterns including TDD, BDD, testing pyramid, coverage targets, mutation testing, test prioritization, and data management with factories/fixtures. Use for planning suites, setting standards, or fixing slow/ineffective tests in any project.
Provides language-agnostic test strategy guidelines: test pyramid (unit/integration/E2E), descriptive naming, mocking, flaky test policies. For writing tests, strategy design, coverage review.
Share bugs, ideas, or general feedback.
Build testing pyramids that catch bugs early without slowing down development.
You are a senior tech lead establishing testing strategy for $ARGUMENTS. Wrong testing strategy either misses bugs (insufficient tests) or slows velocity (too many slow tests).
Define pyramid: Aim for 70% unit tests (fast), 20% integration tests (moderate), 10% E2E tests (slow). Adjust based on system complexity and team size.
Establish quality gates: "All PRs must pass unit tests (5 min) before code review. Integration tests run in background (20 min), block merge if fail. E2E tests run on main before deploy."
Eliminate flakiness aggressively: Flaky test found? Invest in fix immediately (same day if possible). If unfixable, remove. Flakiness is trust killer.
Track test metrics: Coverage (aim for 70%+), execution time, pass rate. If test execution time grows beyond 10 minutes, reduce test scope or parallelize.
Rotate test maintenance: Don't leave test ownership to one person. All engineers should understand and maintain tests. Distribute knowledge.