Dynamic Software Testing via Runtime Test Result Entity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software testing methods become overly complex and unmanageable when dealing with various configuration settings, requiring constant supervision and rerunning of tests, and are inefficient in retrieving test result information due to the need for stopping the testing system and changing numerous rules and relationships.
Innovation Solution
The implementation of a test result entity that allows for runtime access and retrieval of test result information, enabling dynamic testing by supporting script execution platforms to run tests based on retrieved information from a database, thereby eliminating the need for separate testing infrastructures and simplifying the management of configuration settings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple rules and configuration setting variants are built separately for each test, then testing can accommodate different hardware and software configurations, but the testing process becomes overly complex and unmanageable
Solution Approach 1:
The patent creates a universal testing infrastructure that can handle multiple configuration settings through a single integrated system. The testing framework uses parameterized test cases and configuration files that allow the same test infrastructure to adapt to different hardware and software environments without requiring separate rule sets for each configuration, thereby reducing overall system complexity while maintaining versatility.
Solution Approach 2:
The testing system implements dynamic configuration management where test parameters and settings can be modified at runtime through configuration files and command-line arguments. This allows the testing infrastructure to dynamically adapt to different configurations without requiring static, pre-built rule sets for each possible scenario, reducing complexity while maintaining adaptability.
2Loss of information
If the testing system is stopped to retrieve test result information, then test results can be accessed, but the retrieval process becomes overly complex and time-consuming
Solution Approach 1:
The patent implements continuous test execution without system shutdowns. The testing framework maintains running tests in memory and allows real-time access to test result information through programmable interfaces. This eliminates the need to stop the testing system to retrieve results, maintaining continuous operation while providing immediate access to test data through the automated engine's internal state.
Solution Approach 2:
The patent introduces an intermediary layer (the automated testing engine with programmable interfaces) that provides direct access to test result information during execution. This intermediary allows testers to query and retrieve test results through standardized APIs without interrupting the testing process, eliminating the need to stop the system and simplifying the retrieval process.
3Reliability
If constant supervision and rerunning of failed tests is performed, then testing completeness is maintained, but productivity decreases
Solution Approach 1:
The patent implements automated feedback mechanisms where the testing framework automatically tracks test results, identifies failed tests, and triggers reruns based on predefined criteria. The system provides feedback loops that automatically supervise and rerun failed tests without requiring constant manual intervention, maintaining testing completeness while improving productivity through automation.
Solution Approach 2:
The testing system performs self-supervision and automatic rerunning of failed tests through built-in automation features. The automated engine monitors test execution, detects failures, and automatically reruns failed tests according to configured policies, eliminating the need for constant manual supervision and significantly improving productivity while maintaining reliability.
Data Source
AI summary
A mechanism for performing dynamic software testing on a computer system based on test result information retrieved in runtime using test result entity. A method of embodiments of the invention includes causing a test execution script to run a first test to test a first component, and the test execution script is supported by a script execution platform on a computer system, and the first component depends on a second component. The method further includes retrieving, in runtime, testing information relating to the second component from a database, if the first test produces unsatisfactory results relating to performance of the first component, and causing, in runtime, the test execution script to run a second test to test the second component.