regression-testing

Automate regression test selection and analysis across CI/CD pipelines.

436|78|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill regression-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-testing
Source: https://github.com/proffesor-for-testing/agentic-qe/tree/main/.claude/skills/regression-testing
Command: npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill regression-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that new code changes (bug fixes, features, refactoring) do not inadvertently break existing, previously working functionality, providing a crucial safety net for continuous development and deployment.

Core Features & Use Cases

  • Intelligent Test Selection: Guides in choosing the most relevant tests based on code changes, risk, historical failures, and time budgets, avoiding exhaustive runs.
  • Regression Suite Building: Provides a phased approach to building a robust regression suite, from smoke tests to full integration tests.
  • CI/CD Integration: Demonstrates how to embed regression tests into continuous integration and deployment pipelines for fast, automated feedback.
  • Use Case: After a bug fix in the payment module, use this Skill to automatically select and run only the affected payment and checkout tests in your CI pipeline, ensuring the fix didn't introduce new issues.

Quick Start

Use the regression-testing skill to design a selective regression strategy for a pull request, focusing on tests related to changed files and high-risk areas.

Frequently Asked Questions about regression-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent code changes from breaking existing features in production?

Regression testing automates the process of verifying that new code changes don't break previously working functionality. It uses intelligent test selection based on code changes and risk to run only relevant tests in your CI/CD pipeline, catching defects before deployment.

What's the best way to select which tests to run after a code change?

Test selection strategies analyze which parts of your codebase changed, then run only tests covering those areas plus high-risk components. This approach reduces feedback time while maintaining coverage, using change-based, risk-based, and historical failure data to guide decisions.

How do I integrate regression testing into my CI/CD pipeline?

Embed regression tests as automated gates in your CI/CD workflow to run on every commit, nightly, or before release. The regression-testing Skill guides setup of per-commit fast feedback, parallel execution, and sharded test runs to balance speed and coverage.

Can regression testing work with different test frameworks and deployment schedules?

Yes. Regression testing applies across CI/CD pipelines using change-based strategies for per-commit runs, risk-based selection for nightly builds, and historical analysis for pre-release gates, adapting to your framework and deployment cadence.

What happens when a regression test fails in production?

Production defect tracing links failed tests back to the code changes that introduced them, enabling root cause analysis and faster remediation. The agent-driven workflow helps identify which tests detected the issue and what changes caused it.

Do I need a full test suite to use regression testing effectively?

No. Regression testing guides you through building a phased regression suite starting with smoke tests, then integration tests. You build incrementally based on risk and coverage requirements rather than running every test exhaustively.