Marked Test Script Automation for Software Verification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The creation of test scripts for application testing is time-consuming and prone to user errors, as it requires manual identification of test scenarios and expected results, which can lead to syntactical mistakes and inefficiencies as the number of test scripts and scenarios grow.

Innovation Solution

Automating the creation of test scripts by using marked test scripts that include parameter types replaceable with actual parameters, allowing a computing device to generate instances of test scenarios, thereby reducing user errors and enabling testing across different programs or versions without manual input of expected results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual creation of test scripts is used, then user flexibility in identifying test scenarios is maintained, but user errors and time consumption increase as the number of test scripts grows

Engineering Contradiction:

ImproveUser flexibility in identifying test scenariosVSAvoidUser error rate in test script creation

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system enables self-service by allowing the computing device to automatically generate test scripts and expected results by analyzing the application code and executing test scenarios against a benchmark application, eliminating the need for manual user input in script generation and expected result determination

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of creating test scripts with an automated computing system that uses program analysis, code execution, and comparison mechanisms to generate test scenarios and expected results automatically

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If manual identification of test scenarios is performed, then test scenario relevance can be ensured, but time consumption increases significantly

Engineering Contradiction:

ImproveTest scenario relevanceVSAvoidTime to create test scripts

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically analyzing the application code structure, identifying potential test scenarios through program analysis, and pre-generating test scripts before actual testing begins, thereby reducing the time needed during the testing phase

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent replaces manual scenario identification with automated program analysis mechanisms that systematically examine application code to generate relevant test scenarios, significantly reducing time consumption while maintaining relevance through systematic code analysis

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Measurement precision

If manual determination of expected results is performed, then accuracy of expected results can be verified, but time consumption and user error increase

Engineering Contradiction:

ImproveAccuracy of expected resultsVSAvoidTime to determine expected results

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The system enables self-service by automatically determining expected results through execution of test scenarios against a benchmark application, where the computing device autonomously compares results and generates expected outcome data without manual verification

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent implements feedback mechanisms where the system executes test scenarios against both the application under test and a benchmark application, compares the results, and uses this feedback to automatically determine expected results, ensuring accuracy through systematic comparison

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8918763B2Marked test script creation

Publication Date: 2014.12.23 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

Systems, methods, and machine-readable and executable instructions are provided for marked test script creation. Marked test script creation can include identifying a number of test scenarios that are associated with a program under test. Marked test script creation can include identifying a number of parameter types that are associated with the number of test scenarios. Marked test script creation can include including the number of test scenarios and the number of parameter types in a marked test script. Marked test script creation can include marking the number of test scenarios in the marked test script with a mark that identifies the number of test scenarios as requiring further processing. Marked test script creation can include creating, with a computing device, a number of un-marked test scripts from the marked test script wherein the number of un-marked test scripts are used to test the program under test.