Dynamic Test Script Adaptation via CMDB Queries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Automated testing tools struggle to adapt to changes in the computer environment, leading to incomplete simulations and the inability to continue testing after exceptions occur, as they rely on static test scripts that do not account for changes in resources such as moved, renamed, or reconfigured computer resources.

Innovation Solution

The Functional Tester Plug-in (FTP) accesses a Configuration Management Database (CMDB) to dynamically update test scripts and expected results, allowing simulations to continue and complete even after exceptions by identifying and using alternative resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a static test script is used for automated testing, then the testing process is simple to implement, but the simulation cannot adapt to changes in the computer environment

Engineering Contradiction:
Improveease of implementing automated testingVSAvoidadaptability to environment changes
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent transforms the static test script into a dynamic system by integrating real-time database queries. The test script now dynamically retrieves current resource configurations and relationships during execution, allowing it to adapt to environment changes without manual updates while maintaining automated operation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces a database as an intermediary between the test script and the computer environment. This intermediary stores resource configuration information and relationships, enabling the test script to adapt to changes by querying the database rather than containing hard-coded resource references.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If the simulation stops at the first exception, then the testing precision is high for that specific failure, but the overall testing completeness is reduced

Engineering Contradiction:
Improveprecision in identifying specific failuresVSAvoidcompleteness of testing execution
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent implements a feedback mechanism where exceptions during simulation are captured and analyzed in real-time. When an exception occurs, the system queries the database to identify related resources and dynamically adjusts the test execution to continue with alternative resources, providing feedback that enables comprehensive testing while maintaining precision in identifying original failures.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary actions by pre-establishing resource relationships and alternative resource mappings in the database before testing begins. This allows the system to quickly respond to exceptions by retrieving pre-defined alternative resources, enabling continuation of testing without losing precision on the original failure identification.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If manual updates to test scripts are performed to reflect environment changes, then the testing accuracy is maintained, but the time and effort required increases

Engineering Contradiction:
Improveaccuracy of test resultsVSAvoidtime for updating test scripts
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent enables the test script to self-update by automatically querying the database for current resource configurations and relationships during execution. This eliminates the need for manual updates while maintaining testing accuracy, as the script dynamically adapts to environment changes through automated database lookups.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary action by pre-populating the database with resource configuration information and relationships before testing begins. This allows the test script to automatically retrieve accurate, up-to-date information without manual intervention, maintaining precision while eliminating the time loss associated with manual script updates.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10055338B2Completing functional testing
Publication Date: 2018.08.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10055338B2 patent drawing
  • US10055338B2 patent drawing
  • US10055338B2 patent drawing

AI summary

The Functional Tester Plug-in (FTP) extracts information from a data base to enhance automated testing tools to accommodate changes to the computer environment and so that a simulation can be fully executed even if an exception occurs. The FTP accesses the test script and static data store created by a developer using the automated testing tool, wherein the test script and static data store indicate a first resource to be tested at a verification point and a first expected result. The FTP identifies the first resource used by the test script at a first verification point and accesses the data base. The FTP identifies the status and configuration of the first resource in the data base. The FTP calculates an optimal expected result based any changes in the status and configuration of the first resource. The FTP executes the test script using the optimal expected result based any changes in the status and configuration of the first resource.