Installation

Open Claude Code and run this command:

/plugin install regression-test-tracker@claude-code-plugins-plus

Use --global to install for all projects, or --project for current project only.

What It Does

Track and run regression tests to ensure new changes don't break existing functionality.

Features

Test tracking - Mark critical tests for regression suite
Automated execution - Run before deployments
Change impact analysis - Identify affected tests
Test history - Pass/fail trends over time
Flaky test detection - Identify unreliable tests
Fast execution - Optimized test selection

Skills (1) plugin-local skills

tracking-regression-tests View full skill →

Track and manage regression test suites across releases.

ReadWriteEditGrepGlobBash(test:regression-*)

Regression Test Tracker

Overview

Track, manage, and maintain regression test suites across releases to ensure previously fixed bugs stay fixed and existing features remain stable. Maps regression tests to bug tickets, monitors test health over time, and identifies gaps where fixed bugs lack corresponding regression tests.

Prerequisites

Test framework with tagging or marking support (@tag, pytest.mark, JUnit @Tag)
Bug tracking system with issue IDs (GitHub Issues, Jira, Linear)
Git history accessible for correlating bug fixes with test additions
Existing test suite with named test cases
CI pipeline producing test result artifacts (JUnit XML or JSON)

Instructions

Scan the codebase with Grep for bug-fix commits by searching commit messages for patterns like fix:, bugfix, closes #, or Jira ticket IDs.
For each bug-fix commit, check whether a corresponding regression test exists:

Search test files for the bug ticket ID in test names, comments, or tags.
Verify the test exercises the specific code path that was fixed.
Flag fixes without regression tests as coverage gaps.

Create a regression test inventory file (regression-tests.json or regression-tests.md) mapping:

Bug ticket ID to test file and test name.
Severity of the original bug (critical, high, medium, low).
Date the regression test was added.
Current test status (passing, failing, skipped).

Tag existing regression tests with metadata for traceability:

Jest: Add // @regression BUG-123 comments or use describe.each with ticket data.
pytest: Apply @pytest.mark.regression and @pytest.mark.bug("BUG-123") markers.
JUnit: Use @Tag("regression") and @DisplayName("BUG-123: description").

Generate a regression coverage report showing:

Total bugs fixed vs. bugs with regression tests (coverage percentage).
Untested regressions ranked by severity.
Tests that have become flaky or were disabled.

Set up a CI check that fails the build if a bug-fix PR does not include at least one regression test.
Schedule periodic audits (weekly or per-release) to verify all regression tests still pass and remain relevant.

Output

Regression test inventory file mapping bugs to tests
Tagged test files with regression markers and ticket references
Coverage gap report listing bug fixes without regression tests
CI configuration for regression test enforcement
Release readiness checklist based on regre

How It Works


/track-regression           # Run regression suite
/track-regression --mark    # Mark test as regression
/reg                       # Shortcut

regression-test-tracker

Installation

What It Does

Features

Skills (1) plugin-local skills

Regression Test Tracker

Overview

Prerequisites

Instructions

Output

How It Works

Ready to use regression-test-tracker?

Related Plugins

regression-test-tracker

Installation

What It Does

Features

Skills (1) plugin-local skills

Regression Test Tracker

Overview

Prerequisites

Instructions

Output

How It Works

Ready to use regression-test-tracker?

Related Plugins

accessibility-test-scanner

api-fuzzer

api-test-automation

browser-compatibility-tester

chaos-engineering-toolkit

contract-test-validator