Is there a shortcut for running regression tests?

Yes, you can simply use the shortcut 'reg' to trigger the regression test execution and analysis process.

Does this skill help with flaky tests?

Yes, the skill analyzes test history and execution results to identify and highlight tests that show inconsistent or flaky behavior.

When should I use the Regression Test Tracker?

It is best used before deploying new code, after significant refactoring, or when you need to verify that new changes haven't broken existing functionality.

How do I add a specific test to the regression suite?

You can mark a test by asking Claude to 'track regression --mark' followed by the name of the specific test case.

Regression Test Tracker

Name: Regression Test Tracker
Author: jeremylongshore

byjeremylongshore

•

883

セキュリティとテスト

Automates the identification, execution, and analysis of regression tests to ensure code stability and prevent software regressions.

概要

The Regression Test Tracker skill empowers Claude to manage software quality by automating the regression testing lifecycle. It allows developers to mark specific tests for tracking, execute comprehensive regression suites, and analyze results to identify flaky tests or critical failures. By integrating directly into the development workflow, it provides actionable insights into the impact of new code changes, helping teams maintain high standards of stability and reliability before deployment.

主な機能

Detailed impact reporting for code changes
Automated regression suite execution
Test marking and tracking via shortcuts
Flaky test identification and analysis
Historical test result tracking
883 GitHub stars

ユースケース

Running a full regression suite before deploying code to production
Marking critical new test cases to be permanently tracked in the regression suite
Investigating the root cause of failures and identifying unstable test behavior

概要

主な機能

Detailed impact reporting for code changes
Automated regression suite execution
Test marking and tracking via shortcuts
Flaky test identification and analysis
Historical test result tracking
883 GitHub stars

ユースケース

Running a full regression suite before deploying code to production
Marking critical new test cases to be permanently tracked in the regression suite
Investigating the root cause of failures and identifying unstable test behavior