Stats
Actions
Tags
From billy-milligan
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/billy-milligan:test-strategyThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Starting a new project or module and need to define testing approach
references/testing-pyramid.md — unit/integration/e2e ratios, layer definitions, anti-patternsreferences/test-selection.md — when to write which test type, cost per level, skip decisions, ROI by scenarioreferences/tdd-bdd-patterns.md — red-green-refactor cycle, naming conventions, describe groupingreferences/bdd-gherkin.md — Given-When-Then, Gherkin feature files, Cucumber integration, Scenario Outlinereferences/coverage-strategy.md — coverage metrics, thresholds by code type, CI enforcement, exclusionsreferences/coverage-analysis.md — coverage gap analysis, mutation testing with Stryker, survived mutant patternsreferences/test-data-management.md — Fishery factories, deterministic Faker, static fixtures, when to use eachreferences/test-data-isolation.md — DB cleanup strategies, transaction rollback, per-worker schema isolationscripts/analyze-coverage.sh — parses lcov/json coverage reports and outputs improvement suggestionsassets/test-plan-template.md — fillable test strategy document for project kickoffsnpx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganProvides testing strategies including test pyramid, TDD/BDD, unit/integration/E2E patterns, mocking strategies, test data factories, snapshot testing, and mutation testing. Use for designing test strategies, writing tests, or improving coverage.
Design testing strategies (unit, integration, end-to-end, performance) that catch bugs without creating bottlenecks. Use when scaling testing or improving release confidence.
Guides test pyramid structure, coverage targets, and patterns for unit, integration, and E2E tests. Includes AAA pattern, naming conventions, and API test checklist.