Release-Weighted Regression Test Selection for Code Changes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional technologies fail to effectively evaluate the value and weight of regression test cases, leading to challenges in selecting the appropriate test cases for regression testing, especially when resources are limited, and do not provide a way to identify an optimal subset of test cases based on code changes and defects in new product releases.

Innovation Solution

A test selection system determines a product release weight incorporating new features and defects, calculates a regression test case value, and selects an optimal subset of test cases using algorithms like the Knapsack Problem and Traceback algorithm to ensure comprehensive regression testing coverage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all regression test cases are executed to ensure comprehensive testing coverage, then testing reliability is improved, but testing time and resource consumption increase significantly

Engineering Contradiction:

Improvetesting coverageVSAvoidtesting time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and identifies a critical subset of regression test cases from the complete test suite by analyzing code changes and defect information. This extraction process selects only the most relevant test cases that provide maximum testing coverage for the specific product release, thereby reducing the total number of test cases that need to be executed while maintaining comprehensive coverage of critical areas.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the selection parameters for regression test cases by incorporating dynamic factors such as code change impact analysis and defect-related weighting. Instead of using static or uniform selection criteria, the system adjusts test case priorities based on their relevance to recent code changes and historical defect patterns, enabling more efficient selection of high-value test cases.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If the complete regression test suite is executed to ensure thorough quality verification, then testing reliability is improved, but resource consumption increases

Engineering Contradiction:

Improvequality verificationVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts a minimal sufficient subset of regression test cases that provides adequate quality verification for the product release. By analyzing code changes and applying defect-related weighting, the system identifies and extracts only the essential test cases needed to verify quality, eliminating redundant or low-value test cases from execution.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by executing only the necessary portion of the regression test suite rather than the complete set. The system determines the optimal subset of test cases that provides sufficient quality verification coverage, performing just enough testing to ensure reliability without the excessive resource consumption of running all available test cases.

Inventive Principle:

Principle #16Partial or excessive action

3Productivity

If regression test cases are selected without systematic evaluation to reduce testing time, then productivity is improved, but testing precision deteriorates

Engineering Contradiction:

Improvetest case selection efficiencyVSAvoidtest case selection accuracy

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The patent performs preliminary analysis of code changes and defect information before selecting regression test cases. By pre-processing and evaluating the impact of code changes and analyzing historical defect patterns, the system prepares weighting information that guides the subsequent selection process, ensuring that the most relevant test cases are identified efficiently and accurately.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent replaces manual or heuristic-based test case selection with an automated systematic evaluation system. The system uses algorithmic analysis of code changes, defect data, and test case relationships to objectively determine the optimal subset of test cases, substituting mechanical automation for human judgment and achieving both high productivity and precise selection accuracy.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12430229B2Intelligent way to select regression test cases in system test

Publication Date: 2025.09.30 DELL PROD LP

AI summary

Methods, system, and non-transitory processor-readable storage medium for a test selection system are provided herein. An example method includes selecting, by a test selection system, a regression test case from a plurality of regression test cases in a software testing lifecycle system. The test selection system determines a product release weight associated with the regression test case, where the product release weight incorporates new features associated with a product release. The test selection system obtains a regression test case value for the regression test case by applying the product release weight. The test selection system selects the regression test case for use in regression testing for the product release, based on the regression test case value and executes the regression test case on a system.