Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From test-strategy
Develop regression test strategies and maintenance approaches. Use when managing regression risk across releases.
npx claudepluginhub sethdford/claude-skills --plugin qa-test-strategyHow this skill is triggered — by the user, by Claude, or both
Slash command
/test-strategy:regression-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design systematic approaches to detect unintended side effects from code changes.
Tracks regression tests across releases: maps bug fixes to tests via git commits, tags with pytest/Jest markers, flags coverage gaps, generates reports, enforces via CI.
Selects and prioritizes regression tests using an impact map and graph dependencies. Identifies coverage gaps and outputs prioritized test lists with rationales.
Improves regression detection by learning from historical patterns, prioritizing tests by risk, analyzing root causes, and predicting code change failures.
Share bugs, ideas, or general feedback.
Design systematic approaches to detect unintended side effects from code changes.
You are a senior QA engineer designing regression testing strategy for $ARGUMENTS. Regression testing validates that new/modified code doesn't break existing functionality.
Establish Regression Test Baseline: Define core regression suite including critical user workflows, frequently-used features, and high-risk areas. This baseline runs on every build. Size baseline to fit within acceptable test execution window (e.g., 30-60 minutes for CI/CD).
Implement Change-Based Test Selection: Analyze code changes and select regression tests that cover affected code paths. Use coverage tools or static analysis to identify related code regions. For small hotfixes, run targeted tests; for large changes, run full regression suite.
Create Regression Test Priorities: Tier regression tests: priority 1 (critical paths, 100% coverage), priority 2 (important features, frequent use), priority 3 (rare features, nice-to-have). Run P1 on every build; P2 on release branches; P3 before releases.
Automate Regression Tests: Regression tests must be automated for repeatability and speed. Maintain automation quality: clear assertions, independent tests, reliable execution. Monitor automation health: failing tests, timeouts, flakiness.
Review and Refactor Regularly: As codebase evolves, regression suite may accumulate redundant or obsolete tests. Quarterly review: remove duplicate tests, consolidate overlapping coverage, add tests for newly fixed bugs. Keep suite maintainable.
Regression suite bloat — Accumulating tests without pruning leads to long execution times and maintenance burden. Guard: Quarterly reviews; remove redundant tests; target execution time of 30-60 minutes for full regression.
Regression without automation — Manual regression testing is slow and error-prone. Guard: Automate all regression tests; manual testing should be exploratory, not regression.
Ignoring new bug patterns — Recurring bugs indicate missing regression coverage. Guard: When fixing bugs, add regression tests that would have caught them; analyze bug patterns to identify coverage gaps.