Backend Interface Verification Using UI-Configured Mock Assertions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional backend interface testing methods require programming skills, are costly to maintain, prone to errors, and lack intuitive result visualization, with complex rule modifications needing code redeployment.
Innovation Solution
A system that allows users to create and manage mock responses and assertion rules through a user interface, generating verification results without writing test scripts, using a user interface to configure mock and assertion rules for backend interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional programming-based testing methods are used, then testing functionality can be achieved, but the difficulty of operation increases and maintenance cost increases
Solution Approach 1:
The patent uses mock data as a copy or simulation of real backend interface responses. Instead of requiring actual backend systems and complex programming test scripts, the system creates mock responses that replicate the structure and content of real interface responses, allowing frontend testing to proceed independently without relying on the actual backend implementation.
Solution Approach 2:
The patent introduces a mock data management system as an intermediary between the frontend and backend. This intermediary layer provides mock responses that simulate backend behavior, eliminating the need for direct backend connection during frontend testing and reducing the complexity of test script programming.
2Reliability
If traditional programming-based testing methods are used, then testing can be performed, but the time required increases
Solution Approach 1:
The mock data management system automatically generates and manages mock responses based on predefined templates and rules. Instead of requiring testers to manually write complex test scripts, the system self-generates appropriate mock data and comparisons, significantly reducing the time required for test script creation and execution.
Solution Approach 2:
The system pre-defines mock data templates, response structures, and comparison rules before actual testing begins. By preparing these elements in advance through configuration rather than programming, the system eliminates time-consuming script writing during the testing phase itself.
3Measurement precision
If complex rule modifications are made in traditional testing, then testing accuracy can be improved, but device complexity increases
Solution Approach 1:
The patent implements a dynamic mock data management system where mock responses and comparison rules can be flexibly configured and modified through a graphical interface. The system adapts to different testing scenarios by dynamically selecting and applying appropriate mock data templates and comparison strategies without requiring structural changes to the underlying testing framework.
4Reliability
If traditional testing methods are used, then interface verification can be performed, but ease of operation deteriorates
Solution Approach 1:
The patent introduces a user-friendly mock data management interface as an intermediary layer between the user and the complex verification processes. This interface allows users to configure mock data, set comparison rules, and analyze results through graphical controls rather than programming code, making interface verification accessible to non-programmers while maintaining verification accuracy.
Data Source
AI summary
Embodiments of the present disclosure provide a method, device, and medium for verifying a backend interface. The method comprises receiving a request associated with the backend interface. The method further comprising generating a mock response based on the request and a mock rule corresponding to the backend interface, where the mock rule is received through a user interface. The method further comprises obtaining an assertion rule corresponding to the backend interface, where the assertion rule is received through the user interface. In addition, the method further comprises generating a verification result for display based on the mock response and the assertion rule.