Joint debugging test method and system

Abstract

The invention relates to a joint debugging test method and a system, and the method comprises the steps: verifying the account information of a request end when a test request is received; querying information in test data corresponding to the account information, wherein the test data are logically isolated and stored through the account information; returning query results. According to the method, the test data are distinguished through the account information, logic isolation between the data of different test items is achieved, simultaneous testing of multiple users can be achieved, and the safety of the data is guaranteed; all the test processes are carried out in independent test data, and isolation from the production environment is achieved.

Description

technical field [0001] The present application relates to the technical field of interface debugging, in particular to a joint debugging test method and system. Background technique [0002] Joint debugging test is a logical extension of unit test. Its simplest form is: two tested units are combined into one component, and the interface between them is tested. In a real test scenario, many units are combined into components, which in turn are aggregated into larger parts of the program. [0003] At present, many open platforms can provide users with various interface services, and users need to perform a joint debugging test on the interface before using the interface service. At present, in the process of interface joint debugging and testing, the general connection method between the open platform and customers is that the open platform provides different servers for different customers, deploys the environment required by customers, and the test data needs to be provided...

AI Technical Summary

Problems solved by technology

[0006] Second, the test product data is incomplete

To simulate more comprehensive product data, it takes a long time and the process is complicated, and cannot meet user needs in a timely manner, seriously affecting the efficiency of API user access

[0007] The third is the lack of process

After the test environment is verified, it cannot be translated to the production environment, resulting in the known problems of various test environments still appearing in the production environment

Images