Error Simulator Proxy for SUT Failure Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Testing systems under test (SUTs) is challenging due to the difficulty in simulating errors in downstream systems, especially in complex scenarios, as traditional mock-ups become unwieldy and require significant effort to replicate dynamic components and error scenarios.
Innovation Solution
An error simulator acts as a transparent proxy that intercepts traffic between the SUT and downstream systems, forwarding 'success' commands and responses while automatically returning preprogrammed error messages when instructed by the test process, allowing for controlled simulation of failures without modifying the SUT or creating complex mock-ups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional mock-ups are used to simulate errors in downstream systems, then error scenarios can be tested, but the complexity of the testing setup increases significantly and maintenance becomes difficult
Solution Approach 1:
The patent introduces an error simulator as an intermediary component positioned between the system under test and downstream systems. This mediator intercepts traffic, identifies failure commands, and injects appropriate error messages without requiring complex mock-up systems. The error simulator translates testing requirements into controlled error injections, simplifying the overall testing architecture while maintaining comprehensive error scenario coverage.
Solution Approach 2:
Instead of creating complex mock-ups that replicate entire downstream systems, the patent uses a lightweight error simulator that copies only the essential error-injection functionality. The simulator maintains a database of failure commands and corresponding error messages, allowing testers to simulate various error scenarios without rebuilding complete system replicas, thereby reducing complexity while preserving testing effectiveness.
2Reliability
If traditional mock-ups are used to replicate dynamic components and error scenarios, then comprehensive testing can be achieved, but significant effort and time are required for setup and maintenance
Solution Approach 1:
The error simulator performs preliminary actions by pre-configuring a database of failure commands and their corresponding error messages before actual testing begins. This advance preparation allows the simulator to quickly match intercepted commands with appropriate error responses during testing, eliminating the need for time-consuming mock-up configuration during test execution and significantly reducing setup and maintenance time while maintaining comprehensive testing coverage.
3Reliability
If the SUT is modified to facilitate error simulation, then testing capability improves, but the original system integrity is compromised
Solution Approach 1:
The error simulator serves as an external intermediary that enables comprehensive error simulation without modifying the system under test. By positioning the simulator between the SUT and downstream systems, it can intercept traffic, identify failure commands, and inject error messages while leaving the SUT's original architecture and integrity completely intact. This external mediation approach provides full testing capability without compromising system stability or requiring any SUT modifications.
Data Source
AI summary
Embodiments of the present invention relate to an error simulator for a test platform. The test platform includes a test process, a system under test (SUT), the error simulator and at least one downstream system. The error simulator is a transparent proxy that intercepts traffic from/to the SUT. The error simulator forwards only “success” commands from the SUT to the downstream system(s) and forwards actual responses from the downstream system(s) to the SUT. However, when the error simulator receives a “failure” command from the SUT, the error simulator automatically returns a corresponding error message that is obtained from preprogrammed failure information to the SUT. The preprogrammed failure information details one or more “failure” commands and corresponding error messages, and is received from the test process by the error simulator either prior to the start of testing or immediately preceding a failure during a test.