qa-test-impact-analysis
Test impact analysis + regression-suite hygiene: 2 skills (regression-suite-selector, coverage-debt-tracker) and 2 agents (test-suite-pruner, regression-suite-curator).
Install this plugin
/plugin install qa-test-impact-analysis@testland-qaPart of role bundles: qa-role-sdet, qa-role-leadership
qa-test-impact-analysis
Test impact analysis (TIA) and regression-suite hygiene. The selector cuts per-PR CI time by running only impacted tests (with always-on safety fallbacks). The curator manages long-term suite signal/noise at two grains - a quarterly signal-history pass and sprint-grain evidence scans - deciding which tests have stopped catching bugs and which can be folded, gated by test-removal-criteria.
Components
| Type | Name | Description |
|---|---|---|
| Skill | regression-suite-selector | Build-an-X TIA workflow: per-test → source map (coverage- or build-graph-derived) + git diff → impacted ∪ previously-failing ∪ newly-added; safe fallback to full suite. |
| Skill | test-removal-criteria | Decides which tests should stop existing: five removal classes and a four-condition delete gate where every condition must hold. A missing input is a failed condition, and keep is the default verdict. |
| Agent | regression-suite-curator | Two-grain suite curation: quarterly signal-history keep/fold/delete pass plus sprint-grain scans for duplicates / tautologies / trivial / dead-signal / orphan tests; never auto-merges. |
Install
/plugin marketplace add testland/qa
/plugin install qa-test-impact-analysis@testland-qaSkills
regression-suite-selector
Builds a CI workflow that runs only the subset of tests impacted by a PR's changes - combines a per-test → source-file dependency map (built from coverage profiles or, in build-graph projects, queried from the build system itself like Bazel `rdeps`) with the PR's `git diff --name-only`, then selects the union of (impacted by changed files + previously failing + newly added). Always pairs with a periodic full-suite run so a misconfigured map can't silently shrink coverage. Use when the regression suite is large enough that PR-time CI is the bottleneck and a full run is reserved for nightly / pre-release.
test-removal-criteria
Decides which existing tests should stop existing, using five removal classes (duplicate, tautology, trivial, dead-signal, orphan) and a four-condition delete gate where every condition must hold or the verdict reverts to keep. Puts the burden of proof on removal: each deletion carries a written reason, redundant-coverage evidence from a per-test source map, and a named reviewer; a test that has merely never failed is treated as possibly load-bearing, not worthless. Use when a suite has outgrown its signal value and someone is opening a pruning change set that deletes test files; for choosing which tests to RUN per change (not delete) use regression-suite-selector, and to track accumulating low-value coverage over time use the coverage debt ledger in qa-test-reporting's test-coverage-targeter.