Intelligent Automated Script for Parallel Software Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual sanity testing of software applications is time-consuming and costly, especially for large applications, and existing automated techniques require modification or re-writing for different versions or applications, lacking adaptability across multiple platforms.

Innovation Solution

An intelligent automated script that builds a temporary map of the software application's user interface, allowing for parallel testing of multiple versions or applications by instantiating test scripts and performing sanity tests on elements, with error message reporting, without the need for re-writing or modifying the script.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual sanity testing is performed on large applications, then testing thoroughness is improved, but time consumption and labor expenses increase significantly

Engineering Contradiction:
Improvetesting thoroughnessVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically generating test scripts from the application's own user interface elements. The test script generation module captures UI elements and their relationships directly from the application under test, eliminating the need for manual test case creation and reducing dependency on external testers while maintaining comprehensive testing coverage

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical testing processes with automated script execution. The test execution module automatically runs generated scripts against multiple application versions, substituting human operators with automated systems that can perform repetitive testing tasks faster and without fatigue, thereby reducing time consumption while maintaining thoroughness

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

2Productivity

If automated testing scripts are created for specific applications, then testing efficiency is improved, but adaptability to different versions or applications deteriorates

Engineering Contradiction:
Improvetesting efficiencyVSAvoidscript adaptability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system achieves universality by designing a test script generation module that can create scripts applicable to multiple versions and applications within the same domain. The generated scripts use parameterized UI element references and relationship-based navigation that can adapt to version changes without requiring complete script rewrites, allowing one script template to serve multiple testing scenarios

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

Solution Approach 2:

The patent implements dynamics by making test scripts flexible and adaptable rather than static. The scripts incorporate dynamic element identification based on UI relationships and hierarchical structures, allowing them to automatically adjust when UI elements change position or properties across different versions, maintaining script validity without manual intervention

Inventive Principle:
Principle #15Dynamics

3Productivity

If the scope of sanity testing is limited to reduce time and expense, then testing cost is reduced, but product quality deteriorates

Engineering Contradiction:
Improvetesting cost efficiencyVSAvoidproduct quality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary action by automatically generating comprehensive test scripts that cover all major UI elements and their relationships before testing begins. This automated script generation ensures that no critical testing scenarios are omitted, maintaining thoroughness while reducing the manual effort required, thereby achieving both cost efficiency and product quality

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating virtual representations of UI elements and their relationships in the form of structured data models. These copied representations are then used to generate test scripts that systematically cover all UI components, ensuring comprehensive testing coverage without requiring manual inspection of each element, thus maintaining quality while improving efficiency

Inventive Principle:
Principle #26Copying

4Reliability

If test environments are patched to resolve issues after creation, then problem resolution is achieved, but significant rework is required

Engineering Contradiction:
Improveissue resolutionVSAvoidrework effort
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback by automatically detecting UI element changes in patched versions and regenerating test scripts to accommodate these changes. The script generation module continuously monitors and adapts to environment modifications, providing real-time feedback adjustments that eliminate the need for manual rework and reduce the complexity associated with environment patching

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9176851B2Utilizing intelligent automated scripts to test software applications
Publication Date: 2015.11.03 ORACLE INT CORP
  • US9176851B2 patent drawing
  • US9176851B2 patent drawing
  • US9176851B2 patent drawing

AI summary

Embodiments of the invention provide for utilizing an intelligent automated script to test software applications. According to one embodiment, testing a software application can comprise executing a test script for testing a plurality of versions of the software application. For example, executing the test script can comprise instantiating a first instance of the test script for testing the first version of the software application. The first version of the software application can be initiated and a temporary map of the first version of the software application can be built by the test script. The first version of the software application can be tested based on the temporary map. In some cases, a second instance of the test script can be instantiated for testing a second version of the software application. In such cases, the first and second versions of the application may be tested in parallel.