Real-time Regression Test Scope Definition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Defining the scope of regression testing to ensure existing functionality remains intact after code changes is labor-intensive and often infeasible due to complex code structures, with no existing device capable of real-time scope definition.

Innovation Solution

A regression test generator device with a deployment monitoring engine that identifies user interactions and dependent software classes, a development monitoring engine that tracks changes, and a regression scope engine that compares these to define the scope of regression tests in real-time using artificial intelligence and machine learning to determine new functional paths and exclude irrelevant classes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual methods are used to define regression test scope, then comprehensive testing coverage can be achieved, but the process becomes labor-intensive and time-consuming

Engineering Contradiction:
Improvetesting coverageVSAvoidtime to define regression scope
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically monitoring user interactions with the application, identifying dependent software classes, and defining regression test scope without human intervention. The deployment monitoring engine captures functional paths, the development monitoring engine tracks code changes, and the regression scope engine automatically determines which tests to execute, eliminating manual effort while maintaining comprehensive coverage.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the manual mechanical process of defining regression scope with an automated computational system. Instead of manually analyzing code dependencies and determining test scope, the system uses software engines to automatically monitor interactions, identify dependencies, and calculate the regression scope, substituting human cognitive effort with automated processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If comprehensive regression testing is performed on entire application, then all functionality is verified, but the complexity of code structures makes this process infeasible

Engineering Contradiction:
Improvefunctionality verificationVSAvoidcode structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the complex code structure into manageable units by identifying dependent software classes and functional paths. Instead of treating the entire application as a monolithic testing target, the regression scope engine breaks down the codebase into specific classes and methods that are actually affected by changes, making the testing process feasible by working with segmented, relevant portions rather than the whole.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts only the relevant portions of the codebase that need to be tested by identifying software classes dependent on changed code. The regression scope engine extracts specific classes and functional paths from the larger code structure, separating the necessary test targets from the unnecessary portions, thereby reducing testing complexity while maintaining verification of affected functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If real-time regression scope definition is implemented, then testing efficiency is improved, but the system requires complex monitoring and analysis capabilities

Engineering Contradiction:
Improveregression testing efficiencyVSAvoidmonitoring system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple monitoring and analysis functions into an integrated system. The deployment monitoring engine, development monitoring engine, and regression scope engine work together as a unified system, combining interaction monitoring, dependency analysis, and scope definition capabilities. This integration reduces the complexity that would arise from separate systems while enabling real-time regression scope definition and improving testing efficiency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The monitoring system is designed with multi-functionality, where the same infrastructure serves multiple purposes: capturing user interactions, tracking code changes, identifying dependencies, and determining regression scope. This universal approach reduces overall system complexity compared to having separate specialized systems for each function, while still achieving real-time regression testing efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11074164B1Real-time regression test generator
Publication Date: 2021.07.27 BANK OF AMERICA CORP
  • US11074164B1 patent drawing
  • US11074164B1 patent drawing
  • US11074164B1 patent drawing

AI summary

A regression test generator device configured for real-time monitoring of a user's interaction with an application running within a production environment and definition of a scope of regression testing to be carried out on one or more components of the application in response to changes made within a development environment. The regression test generator device identifies new user flows through an application, and stores the underlying software classes used to facilitate a given task associated with the new user flows. In addition, the regression test generator device monitors software classes changed in a development environment, and matches the changed software classes to one or more flows that are to be regression tested.