Concurrent Application Test Recording and Replay

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application testing workflows require sequential execution of record, replay, development, and analysis phases, resulting in prolonged testing times, whereas concurrent execution of these phases can significantly reduce overall workflow time by overlapping record and replay phases, and development and replay phases.

Innovation Solution

Concurrently executing the record and replay phases, and the development and replay phases, allowing for simultaneous execution of multiple test portions on different platforms to reduce the time needed for each phase, thereby accelerating the testing process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequential execution of record, replay, development, and analysis phases is used, then workflow completeness is ensured, but total testing time increases

Engineering Contradiction:
Improveworkflow completenessVSAvoidtotal testing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The replay phase is executed preliminarily during the record phase by initiating replay operations on previously recorded scripts while the current recording is still in progress. This allows the replay phase to be partially completed before the record phase finishes, reducing the total sequential time required for both phases.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Multiple phases (record, replay, development) are executed concurrently rather than sequentially, ensuring that useful actions continue across all phases simultaneously. The system maintains continuous productive work by overlapping phase executions, thereby reducing idle time and total workflow duration while maintaining completeness through proper phase integration.

Inventive Principle:
Principle #20Continuity of useful action

2Loss of time

If concurrent execution of record and replay phases is implemented, then total workflow time is reduced, but system complexity increases

Engineering Contradiction:
Improvetotal workflow timeVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The testing system is segmented into independent, modular phases (record, replay, development, analysis) that can be executed independently or concurrently. Each phase is treated as a separate unit with defined inputs and outputs, allowing concurrent execution without requiring complex inter-phase dependencies, thus managing system complexity while enabling time reduction.

Inventive Principle:
Principle #1Segmentation

3Productivity

If multiple phases are executed simultaneously on different platforms, then testing speed increases, but resource management complexity increases

Engineering Contradiction:
Improvetesting speedVSAvoidresource management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The testing system is designed with universal phase execution capabilities that can run the same phase (record, replay, development, or analysis) simultaneously on multiple different platforms. Each phase is implemented as a multi-functional module that adapts to different platforms, allowing parallel execution without requiring platform-specific complex resource management for each phase.

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

Data Source

PatentUS10296449B2Recording an application test
Publication Date: 2019.05.21 MICRO FOCUS LLC
  • US10296449B2 patent drawing
  • US10296449B2 patent drawing
  • US10296449B2 patent drawing

AI summary

Recording an application test can include creating a number of recordings that define a number of interactions with an application under test (AUT), wherein the number of recordings are created serially. Recording an application test can include replaying each of the number of recordings while the number of recordings are being created to determine an outcome of a test. Recording an application test can include analyzing and reporting the outcome of the test.