Schema-Based Automated Testing for Enterprise Service Payloads
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Testing of business applications involving multiple services that process large volumes of data is challenging due to differing structures in electronic documents, making it difficult to verify the correctness of these services automatically and generically.
Innovation Solution
A method and system that receive and compare payloads from different services using a schema to determine discrepancies, with a service execution module, communication module, and comparison management module to execute and verify the correctness of services, even when payload structures differ.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If services handle data in differently structured electronic documents, then services can process diverse business objects, but testing becomes difficult and manual verification is required
Solution Approach 1:
The patent applies universality by creating a generic testing framework that can test multiple services handling differently structured electronic documents using a single unified approach. The test procedure generator and execution system are designed to work with various payload structures (XML, JSON, etc.) through schema-based validation, making the testing system multi-functional and adaptable to diverse service types without requiring service-specific testing logic.
Solution Approach 2:
The patent uses parameter changes by dynamically adapting the testing parameters based on the schema of the electronic document. The system receives schema definitions that describe the structure of payloads, and these schema parameters guide the generation of test procedures. When schemas change to reflect different document structures, the testing parameters automatically adjust, enabling the system to handle diverse structures without increasing testing complexity.
2Quantity of substance
If electronic documents contain hundreds or thousands of fields, then services can process comprehensive business objects, but testing becomes a difficult and time-consuming task
Solution Approach 1:
The patent applies preliminary action by pre-defining schemas that describe the structure, data types, and validation rules for electronic document fields before actual testing occurs. These schemas serve as templates that automatically generate test procedures. When new fields are added to electronic documents, the schema is updated beforehand, and the testing system automatically adapts, eliminating the need for manual test case creation for each new field and significantly reducing testing time.
Solution Approach 2:
The system applies self-service by automatically generating test procedures and executing tests based on the provided schema without requiring manual intervention for each test case. The test procedure generator automatically creates appropriate test scenarios, and the execution system runs these tests and generates reports, enabling the testing process to serve itself and eliminating time-consuming manual testing efforts.
3Productivity
If automatic testing is implemented, then testing efficiency improves, but handling structurally different payloads requires complex comparison logic
Solution Approach 1:
The patent introduces an intermediary element - the schema - that mediates between structurally different payloads and the comparison logic. Instead of implementing complex comparison logic to handle different payload structures directly, the system uses schemas as intermediaries that normalize and standardize the representation of payloads. The comparison logic simply validates payloads against their corresponding schemas, which handles the structural differences automatically, thus maintaining high testing efficiency without increasing comparison logic complexity.
Data Source
AI summary
The testing of services techniques include a method, a system, and a non-transitory computer-readable storage medium. In some embodiments of these techniques, the method includes receiving a first payload generated by a first service. The first service transmits the first payload to a system. The method further includes receiving a second payload from a second service. The second payload is generated based on data received from the first service. The method further includes receiving a schema associated with the second payload. The schema is configured to define the structure of the second payload. The method further includes determining one or more discrepancies between the second payload and the first payload using the schema associated with the second payload. The method further includes determining a testing result based on the one or more discrepancies.This Abstract is provided for the sole purpose of complying with the Abstract requirement rules. This Abstract is submitted with the explicit understanding that it will not be used to interpret or to limit the scope or the meaning of the claims.