Mock Server Framework for Pre-Production Microservice Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise software testing techniques are inadequate in efficiently responding to evolving user needs, policy requirements, and security environments.
Innovation Solution
A mock server is deployed in a pre-production environment to mimic the operation of microservices, allowing for simulated testing of new microservices before full implementation, with predetermined responses to requests and monitoring for receipt of responses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional enterprise software testing techniques are used, then testing can be performed, but the testing process cannot efficiently respond to evolving user needs, policy requirements, and security environments
Solution Approach 1:
The patent applies preliminary action by deploying mock servers before the actual microservices are ready. The mock servers are configured with predetermined responses in advance, allowing the first microservice to be tested immediately without waiting for other microservices to be completed. This enables parallel development and testing, significantly reducing the overall testing time while maintaining adaptability to evolving requirements.
Solution Approach 2:
The patent uses mock servers as intermediary components that mediate between the first microservice under test and the other microservices that are not yet ready. The mock server acts as a placeholder that simulates the behavior of dependent microservices, allowing testing to proceed independently. This intermediary approach decouples the testing process from the availability of all microservices, improving both adaptability and response time.
2Reliability
If all microservices are deployed together in production environment, then the system can function completely, but testing cannot be performed until all microservices are fully implemented
Solution Approach 1:
The patent applies copying by creating mock servers that replicate the behavior and interfaces of the actual microservices. These mock servers are simplified copies that provide predetermined responses, allowing the first microservice to be tested with realistic interactions without requiring the full production system. This copying approach maintains testing reliability while dramatically improving productivity by enabling early testing.
Solution Approach 2:
The patent segments the testing process into independent units by allowing the first microservice to be tested separately from the other microservices. The mock server enables this segmentation by providing isolated, controllable responses that simulate the dependent microservices. This segmentation allows parallel testing and development, improving productivity without compromising the eventual system reliability when all microservices are integrated.
3Productivity
If mock server with predetermined responses is used, then testing can proceed without all microservices implemented, but the mock server must be configured to mimic specific microservice operations
Solution Approach 1:
The patent applies universality by designing the mock server to handle multiple types of microservice operations through a unified interface. The mock server can be configured with predetermined responses for various microservice calls (database operations, authentication, file storage, etc.) using a consistent configuration approach. This multi-functional capability reduces the complexity burden by providing a standardized way to handle diverse microservice simulations, maintaining high testing speed while managing configuration complexity.
Data Source
AI summary
A mock server is configured to mimic the operation of one or more microservices used in enterprise software. When a new microservice is completed for use in the enterprise software, the new microservice and the mock server can be deployed in a pre-production environment for testing. One or more test cases are created and then executed in the pre-production environment, causing the new microservice to access various other microservices represented by the mock server with one or more predetermined requests. In this manner, the new microservice may be tested in a simulated production environment before other microservices in the enterprise software design have been fully implemented.