Automated Webpage Validation Tool for Source Code Change Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Automated software tests are time and resource intensive, often failing due to unintended surface-level changes in webpages that are not checked until the full test suite is executed, leading to unnecessary resource expenditure.

Innovation Solution

An automated validation tool that analyzes webpage elements according to predefined rules when source code changes occur, determining which elements are affected and communicating potential test failures to the test server, thereby avoiding the need for a full test suite execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the full automated test suite is executed against every source code change, then comprehensive bug detection is achieved, but time and computational resources are wasted when changes only affect surface-level aspects

Engineering Contradiction:

Improvebug detection completenessVSAvoidtest execution time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the test execution process into two distinct phases: a fast validation phase that checks surface-level webpage elements (presence, visibility, basic functionality) and a comprehensive automated test phase that performs deep functional testing. This segmentation allows the system to quickly filter out changes that only affect surface elements before committing resources to full test suite execution.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary validation checks that run immediately after source code changes are detected. These preliminary checks analyze surface-level webpage elements before the full automated test suite is executed, enabling early detection of obvious issues and preventing unnecessary full test runs when changes are purely cosmetic.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If the full automated test suite is executed against every source code change, then comprehensive bug detection is achieved, but computational resources are unnecessarily consumed

Engineering Contradiction:

Improvebug detection completenessVSAvoidcomputational resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by performing only the necessary validation checks based on the type of change detected. For surface-level changes, only surface validation is performed rather than the complete test suite, optimizing resource usage by doing exactly what is needed - no more, no less.

Inventive Principle:

Principle #16Partial or excessive action

3Reliability

If surface level changes are not checked until full automated tests run, then comprehensive validation is achieved, but time and resources are wasted on unintended changes

Engineering Contradiction:

Improvevalidation completenessVSAvoiddevelopment workflow efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary validation checks that run immediately after source code changes are detected. These preliminary checks analyze surface-level webpage elements (presence, visibility, basic functionality) before the full automated test suite is executed, enabling early detection of obvious issues and preventing unnecessary full test runs when changes are purely cosmetic.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the results of surface-level validation checks are communicated back to the development workflow. When surface-level changes are detected, the system provides immediate feedback about potential issues before full testing occurs, allowing developers to make corrections early in the process.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS10599426B2Automated validation tool

Publication Date: 2020.03.24 BANK OF AMERICA CORP

AI summary

An automated validation tool includes a hardware processor that receives a message that indicates a first element, a second element, and a third element of a first webpage. The message is generated in response to a detected change to source code for the first webpage. The processor determines that the first element and the second element exist on a second webpage and that the third element does not exist on the second webpage, that activating the first element on the second webpage performs a first function, and that activating the second element on the second webpage does not perform a second function. The second webpage represents the first webpage after the detected change is implemented. The processor communicates a response that indicates the determinations.