Test Script Execution Engine for Server Stack Resource Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Large enterprise systems face challenges in routine maintenance due to the diverse configuration and resource requirements of services within big data stores, leading to inefficient testing and potential overburdening of server processing resources, which can impact service quality and require extensive manual effort.

Innovation Solution

A functional test execution engine that manages the execution of test scripts based on the processing resources available in the server stack, determining which scripts to run and when, to optimize resource utilization and minimize downtime, ensuring efficient maintenance and high service quality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If test scripts are executed to verify service status in big data stores, then service reliability is improved, but server processing resources are overburdened

Engineering Contradiction:

Improveservice status verificationVSAvoidprocessing resources

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system monitors server processing resources in real-time and uses this feedback to dynamically adjust test script execution. When resources are sufficient, comprehensive tests run; when resources are constrained, test execution is paused or reduced, preventing overburdening while maintaining service reliability

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The test execution system transitions from static scheduling to dynamic adaptation based on current server conditions. Test scripts are selectively executed based on real-time resource availability, service criticality, and priority levels, allowing the system to optimize between reliability and resource consumption

Inventive Principle:

Principle #15Dynamics

2Reliability

If comprehensive test scripts are executed to maintain big data stores, then service quality is improved, but maintenance time increases

Engineering Contradiction:

Improveservice qualityVSAvoidmaintenance time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Instead of always executing complete test suites, the system performs partial testing based on current needs. Critical services receive comprehensive testing while less critical services receive minimal or deferred testing, reducing overall maintenance time while maintaining adequate service quality

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system changes test execution parameters dynamically based on service priority, resource availability, and risk levels. Test depth, duration, and scope are adjusted as variables rather than fixed parameters, enabling flexible optimization of maintenance time versus service quality

Inventive Principle:

Principle #35Parameter changes

3Measurement precision

If manual testing of big data stores is performed, then testing thoroughness is improved, but labor requirements increase

Engineering Contradiction:

Improvetesting thoroughnessVSAvoidhuman resources

Core Design Contradiction:

Measurement precisionVSQuantity of substance

Solution Approach 1:

The system implements automated self-testing capabilities where test scripts automatically execute, monitor, and report on service status without human intervention. The system self-manages test scheduling, resource monitoring, and result analysis, maintaining thorough testing while eliminating the need for extensive manual labor

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

Manual testing operations are replaced with automated computational systems. Test scripts, monitoring agents, and scheduling algorithms substitute human technicians, providing consistent, repeatable, and scalable testing thoroughness without proportional increases in human resources

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If test scripts are executed frequently to ensure service status, then service reliability is improved, but server performance degradation occurs

Engineering Contradiction:

Improveservice status monitoringVSAvoidserver performance

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

Instead of continuous or fixed-frequency testing, the system implements periodic test execution triggered by resource availability conditions. Tests run at optimal intervals when server performance is adequate, avoiding excessive frequency that would degrade performance while maintaining reliable service status monitoring

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS11243857B2Executing test scripts with respect to a server stack

Publication Date: 2022.02.08 BANK OF AMERICA CORP

AI summary

A functional test execution engine (“FTEE”) may be configured to execute test scripts with respect to a server stack. The FTEE may be communicatively coupled to a test script storage device, which may store the test scripts. The FTEE may select one or more test scripts for execution with respect to the server stack. The one or more test scripts may carry out maintenance or diagnostic functions for the server stack. The FTEE may determine the processing resources of the server stack and, based on those processing resources, select a first set of test scripts from the one or more test scripts to execute. The FTEE may cause the first set of test scripts selected to execute with respect to the server stack in order to generate test script results. The FTEE may store the test script results for subsequent analysis and use during execution of subsequent test scripts.