Automated Enterprise Testing System for Concurrent Production Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional shadow testing of enterprise systems requires copying the entire production system, leading to significant memory consumption, downtime, and difficulty in identifying issues due to inconsistent data, making targeted testing challenging.
Innovation Solution
A method and system for concurrent production use and testing of a modified enterprise system, where inputs from users are filtered and used to perform transactions on both the production and modified systems, allowing for real-time comparison and analysis to ensure correct configuration without halting production.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire production system is copied for shadow testing, then testing can be performed with production data, but significant memory consumption occurs
Solution Approach 1:
The patent segments the production system copy into only the necessary components for testing - specifically, it copies only the relevant data subsets and system components needed for the modified system testing, rather than copying the entire production system. This selective segmentation reduces memory consumption while maintaining testing reliability.
2Reliability
If the entire production system is copied for shadow testing, then testing can be performed, but significant time is required for the copy procedure
Solution Approach 1:
The patent segments the copying process to only include necessary system components and data subsets required for testing the modified system, rather than copying the entire production system. This selective approach significantly reduces copy procedure time while maintaining testing accuracy.
Solution Approach 2:
The patent applies partial action by performing only the necessary copying of relevant data and system components needed for testing, rather than copying the complete production system. This partial copying approach reduces time loss while sufficient for achieving testing objectives.
3Productivity
If production use continues during copying, then downtime is avoided, but inconsistent data is created in the copy
Solution Approach 1:
The patent takes preliminary action by capturing production data at a specific point in time before copying, establishing a consistent snapshot baseline. This preliminary data capture ensures that the copy starts with consistent data, even as production continues during the testing process.
Solution Approach 2:
The patent uses targeted copying of production data to create a test environment that mirrors the production system at a specific moment. This copying approach allows production to continue while maintaining data consistency in the test copy by capturing and freezing the relevant data state.
4Reliability
If all transactions from the origin system are run in the test system, then comprehensive testing is achieved, but targeted testing becomes difficult
Solution Approach 1:
The patent segments the transaction set by implementing filtering mechanisms that allow selection of specific transactions for testing. This segmentation enables testers to choose only the relevant transactions needed for testing the modified system, providing both comprehensive coverage of necessary areas and the flexibility for targeted testing.
Solution Approach 2:
The patent applies partial action by running only the necessary subset of transactions required for testing the modified system, rather than forcing all origin system transactions through the test system. This approach maintains testing completeness for relevant areas while improving ease of operation through selective transaction execution.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for concurrent production use of an enterprise system and testing of a modified enterprise system is provided. The method includes obtaining inputs from one or more users of a production enterprise system; providing the inputs from the one or more users to the production enterprise system; determining, by at least a hardware processor, a subset of the inputs from among the one or more users to use to test the modified enterprise system; performing, by at least the hardware processor, one or more transactions on the subset of the inputs on the modified enterprise system and a copy of the production enterprise system; and analyzing, by at least the hardware processor, the one or more transactions to determine that the modified enterprise system is correctly configured.