skills.rest
machenjie
machenjieCOMMUNITY
Explore all skills by this author →
GitHub

regression-testing

Create regression tests that fail on pre-fix code and pass on post-fix code.

4|Updated May 16, 2026
Search Tags:#unit testing#test strategy#regression testing#test design#CI quality gate#defect traceability
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill regression-testing-machenjie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-testing
Source: https://github.com/machenjie/rd-skills/tree/main/src/foundation/capabilities/regression-testing
Command: npx skills add https://github.com/machenjie/rd-skills --skill regression-testing-machenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Regression-testing ensures a specific past failure is automatically caught again in future changes, preventing the same defect or incident from recurring without detection.

Core Features & Use Cases

  • Regression-proof coverage: Adds tests that reproduce the original failure mode and fail before the fix, then pass after the fix.
  • Defect traceability: Requires every regression test to be linked to a defect ID, incident, or review finding so the test’s purpose is never ambiguous.
  • Right-sized test strategy: Selects the narrowest effective level (unit, integration, or E2E) so teams get fast, reliable protection without unnecessary flakiness.
  • Untestable defect handling: When automation is infeasible, documents residual risk and compensating controls such as monitoring or manual regression evidence.

Quick Start

Use the regression-testing skill to create a failing-first test plan for a confirmed defect, tied to the exact triggering input and conditions from the original bug report.

Frequently Asked Questions about regression-testing

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

FAQPage Schema
How do I write a regression test that prevents a specific past defect from coming back?▼

A regression test prevents recurrence by reproducing the exact triggering conditions, data state, and dependency behavior of a past defect. The test must fail on pre-fix code and pass on post-fix code to automatically catch the specific failure in future changes.

What is the right test level to select for regression testing?▼

The right test level for regression testing is the narrowest effective option—unit, integration, or E2E. This right-sized strategy ensures fast, reliable protection against defect recurrence without introducing unnecessary test flakiness.

How do I handle regression testing when automating the test is technically impossible?▼

When regression test automation is technically impossible, document the residual risk and establish compensating controls such as monitoring or manual regression evidence. This ensures the defect is managed even without automated CI quality gates.

How do I link my regression test to the original incident for defect traceability?▼

Defect traceability is maintained by linking every regression test to a specific defect ID, incident, or review finding. This ensures the test's purpose is never ambiguous and connects the non-recurrence validation to the original resolved incident.

Why does my regression test need to capture original roles and data state?▼

Regression tests must capture original roles, data state, and dependency behavior to accurately reproduce the specific past failure. Without these exact triggering conditions, the test cannot reliably fail on pre-fix code and prevent recurrence.

Related Skills

Explore More Software Engineering Skills→
ToanPV90ToanPV90

regression-verify

Run a revert-and-confirm protocol to verify regression tests catch defects.

Community
Intermediate
proffesor-for-testingproffesor-for-testing
436

shift-left-testing

Generate and execute unit, integration, and end-to-end tests within CI/CD workflows.

Community
Advanced
BarryrnBarryrn

testing

Codify a scalable testing strategy across unit, integration, and E2E layers.

Community
Basic
davidmatousekdavidmatousek
86

tachi-control-analysis

Explain compensating-controls analysis concepts for threat-modeling workflows.

Community
Advanced