Automation Test Accelerator via Shared CTITS Module
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Previous information handling systems face inefficiencies in executing multiple automation test cases due to limited hardware resources, leading to long test durations and high costs, as they require separate hardware for each test case and fail to efficiently handle common time-intensive test steps.
Innovation Solution
The system creates a Common and Time-Intensive Test Steps (CTITS) module, which is shared across multiple test cases, allowing for the execution of CTITS only once, and inserts identifiers within normal test cases to manage test step execution efficiently, enabling separate processing of pre- and post-CTITS steps.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate hardware is used for each test case, then test case execution can proceed independently, but hardware resource requirements increase and test duration extends
Solution Approach 1:
The patent merges multiple test case executions by identifying and extracting common time-intensive test steps (CTITS) that are shared across multiple test cases. These common steps are executed once and their results are reused by multiple test cases, thereby reducing hardware resource requirements while maintaining test execution independence through proper result sharing mechanisms.
Solution Approach 2:
The patent creates a universal CTITS module that serves multiple test cases simultaneously. This module is designed to be reusable across different test cases, allowing the same hardware resources to be utilized efficiently for multiple testing purposes. The universal module handles common operations like device provisioning, network configuration, and baseline measurements that are needed across various test scenarios.
2Productivity
If separate hardware is allocated for each test case, then test execution can be parallelized, but test duration increases due to resource setup overhead
Solution Approach 1:
The patent combines the execution of common test steps across multiple test cases by implementing a shared CTITS execution mechanism. Instead of re-executing identical time-intensive operations for each test case, the system executes them once and shares results, significantly reducing overall test duration while enabling efficient parallelization of independent test case logic.
Solution Approach 2:
The patent performs preliminary identification and extraction of common time-intensive test steps before actual test case execution. By pre-processing the test suite to identify CTITS and prepare the shared execution mechanism, the system eliminates redundant setup overhead during parallel test execution, thereby reducing total test duration.
3Ease of operation
If common test steps are executed separately in each test case, then test case independence is maintained, but time consumption increases significantly
Solution Approach 1:
The patent extracts common time-intensive test steps from individual test cases and places them in a separate shared CTITS module. This extraction maintains test case independence by allowing each test case to reference and utilize the shared module's results without direct coupling, while simultaneously eliminating redundant execution of identical steps across multiple test cases, thereby reducing total execution time.
4Productivity
If multiple hardware resources are allocated for automation testing, then more test cases can be executed simultaneously, but system cost increases
Solution Approach 1:
The patent merges the resource requirements for concurrent test case execution by implementing a shared CTITS infrastructure. Multiple test cases can leverage the same hardware resources for common operations, allowing the system to execute more test cases simultaneously without proportionally increasing hardware investment. The shared module efficiently manages resources like device under test, network interfaces, and measurement equipment.
Data Source
AI summary
An information handling system includes a memory and a processor. The memory stores an automation test set for the information handling system, and the automation test set includes multiple test cases. The processor determines that each test case of a subset of the test cases includes a same common and time-intensive test step (CTITS). The processor creates a CTITS module based on the same CTITS in the subset test cases. The processor also creates multiple normal test cases based on the test cases of the automation test set. The processor creates a virtual test case to implement the CTITS, executes first test step code within a first normal test case, and executes second test step code within a second normal test case. In response to execution of both the first and second test step code being completed, the processor executes the CTITS via the CTITS module.