Relay Testing System for Business Application Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of independently developed enterprise applications often goes untested due to resource constraints, leading to potential issues when these applications interact in a production environment, as traditional staging methods require two complete production environments and are not always feasible.
Innovation Solution
A relay testing system that records and executes calls between business systems, allowing for end-to-end testing by simulating external interactions through stubbing and data coverage reporting, thereby improving integration quality without the need for full staging environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional staging methods are used to test integration between independently developed applications, then integration quality can be improved, but resource requirements and complexity increase significantly
Solution Approach 1:
The patent introduces a relay testing system that acts as an intermediary between independently developed applications. The relay system records calls from one application and executes them as stubs in another application, enabling integration testing without requiring both applications to be fully deployed in parallel production environments. This mediator approach allows testing of integration between applications while reducing the complexity of maintaining multiple complete production environments.
2Reliability
If full staging environments are deployed to test application interactions, then comprehensive integration testing is enabled, but time and resource constraints are exceeded
Solution Approach 1:
The relay testing system performs preliminary recording of application calls during normal operation. By capturing the call patterns and data flows in advance, the system can later execute these recorded calls as stubs to test integration scenarios without needing to wait for full staging environments to be deployed and configured. This preliminary action enables integration testing to proceed parallel to development cycles, reducing overall testing time.
Solution Approach 2:
The system creates a copy of the call interaction patterns by recording actual calls between applications and then re-executing these calls as stubs in the relay testing system. This copying approach allows comprehensive integration testing to be performed using simplified test scenarios that replicate real-world interactions without requiring full production environments to be replicated, thereby reducing testing time and resource requirements.
3Productivity
If independently developed applications are deployed without extensive integration testing, then deployment speed increases, but integration errors may arise in production
Solution Approach 1:
The relay testing system enables applications to test their own integration interactions by recording their own calls and executing them as stubs. This self-service approach allows each application to verify its integration points without requiring extensive manual testing by other teams, thereby maintaining fast deployment speeds while improving integration stability through automated relay testing of the application's own call patterns.
Data Source
AI summary
Methods, systems, and computer readable medium are disclosed to test a first business system and a second business system. A test of the first business system is performed, wherein the first business system is integrated with the second business system. One or more calls are recorded from the first business system to the second business system during the test of the first business system. The one or more calls from the first business system are identified for a test of the second business system.