WO2019153472A1

WO2019153472A1 - Automated interface testing method, device, equipment, and storage medium

Info

Publication number: WO2019153472A1
Application number: PCT/CN2018/081545
Authority: WO
Inventors: 贾江丽
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-02-07
Filing date: 2018-04-02
Publication date: 2019-08-15
Also published as: CN108415832A; CN108415832B

Abstract

The present application relates to the field of software testing. Provided are an automated interface testing method, a device, equipment, and a storage medium. The method comprises the following steps: acquiring interface files of different interfaces, automatically generating JSON test samples of the different interfaces on the basis of the interface files; automatically generating a test case template on the basis of the JSON test samples, automatically generating a JSON test case on the basis of the test case template, and then automatically generating a JMeter test script on the basis of the JSON test case; generating an integrated test case on the basis of the JMeter test script, calling the integrated test case via a test tool, triggering the JMeter test script via the integrated test case for testing, and automatically outputting the test result. The automated interface testing method, the device, the equipment, and the storage medium provided in the present application increase the degree of automation of interface testing and facilitate the maintenance of a test case when modifying an interface.

Description

Interface automation test method, device, device and storage medium

This application is based on the Chinese Patent Application No. 201101121971.X filed on February 7, 2018, entitled "Interface Automation Test Method, Apparatus, Equipment, and Storage Medium", and requires priority.

Technical field

This application belongs to the field of software testing, and more specifically to an interface automatic test method, apparatus, device and storage medium.

Background technique

Interface testing is a test of the interface between test system components. It is mainly used to detect the interaction between external systems and systems and internal subsystems, focusing on data exchange, transfer and control management processes, and inter-system Mutual logical dependencies, etc.

In the prior art, when an interface or an interface in an interface test needs to be added, deleted, or modified, one code is required for maintenance, and the interface is run in a postman (a tool for automated test of an interface), or one by one. Executing the results in the existing interface test tool takes a long time, is not automated, and is inefficient.

Summary of the invention

In view of the deficiencies of the prior art, the present application provides an interface automatic test method, apparatus, device, and storage medium, which can improve the degree of automation and the efficiency of testing.

This application is implemented as follows:

A first aspect of the present application provides an interface automation testing method, the method comprising the following steps:

Obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document;

Generating a test case template automatically according to the Json test sample, and automatically generating a Json test case according to the test case template, and automatically generating a Jmeter test script according to the Json test case;

Generating an integrated test case according to the Jmeter test script, calling the integrated test case through a test tool, and triggering the Jmeter test script to test by the integrated test case, and automatically outputting the test result.

The second party of the present application provides an interface automatic testing device, the device comprising:

a sample generation module: an interface document for acquiring different interfaces, and automatically generating a Json test sample of different interfaces according to the interface document;

a script generation module: configured to automatically generate a test case template according to the Json test sample, automatically generate a Json test case according to the test case template, and automatically generate a Jmeter test script according to the Json test case;

The interface test module is configured to generate an integrated test case according to the Jmeter test script, invoke the integrated test case by using a test tool, and trigger the Jmeter test script to test by the integrated test case, and automatically output the test result.

A third aspect of the present application provides a terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, wherein the processor executes the computer The following steps are implemented when the instructions are readable:

A fourth aspect of the present application provides one or more non-transitory readable storage mediums storing computer readable instructions, the computer readable instructions being executed by one or more processors such that the one or more processes Perform the following steps:

The interface automatic test method, device, device and storage medium provided by the application automatically generate test samples, test sample sets, test case templates, Json test cases, Jmeter test scripts and integrated test cases through interface documents, and then pass the test. The tool calls the Jmeter test script to test, automatically outputs the test result, and the degree of automation is high, which improves the efficiency of the test. When the interface is modified, a new test script can be quickly generated for testing, and the interface test process is easy to maintain.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only the present application. For some embodiments, other drawings may be obtained from those of ordinary skill in the art in light of the inventive workability.

FIG. 1 is a flowchart of an interface automatic testing method according to an embodiment of the present application;

2 is a diagram showing an example of a request message and a response message in the embodiment shown in FIG. 1;

3 is a diagram showing an example of a test sample set of the embodiment shown in FIG. 1;

4 is a diagram showing an example of a test case template of the embodiment shown in FIG. 1;

Figure 5 is a flow chart showing the sub-steps of the step S103 of the embodiment shown in Figure 1;

6 is a schematic structural diagram of an interface automatic testing apparatus according to another embodiment of the present application;

FIG. 7 is a schematic structural diagram of a terminal device according to another embodiment of the present disclosure.

Detailed ways

In order to make the technical problems, technical solutions and beneficial effects to be solved by the present application more clear, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

Please refer to FIG. 1 , which is a flowchart of an interface automatic testing method provided by an embodiment of the present application.

Interface testing refers to testing the application program interface (API), including two types: one is the external interface, that is, the call between the system and the system, such as the interface call between the Taobao order system and the payment system; the other is the internal interface. It refers to the call of the upper layer service to the lower layer service or the call between the service and the service. For example, the business layer calls the data layer, the business layer is the upper layer service, the data layer is the lower layer service, and for example, the goods are selected and the order is created.

The role of interface testing is to check whether the data exchange, delivery, and management processes between interfaces are normal.

As shown in FIG. 1 , the interface automatic testing method provided by the embodiment of the present application includes the following steps:

Step S101: Obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document.

The interface document refers to the interface parameters provided by the developer of the application for different interface tests. The interface document mainly includes four parts of the request method, the URI, the request parameter and the return parameter. The request method usually includes: GET/PUT/POST/DELETE; the URI is a Uniform Resource Identifier (URI), which is a string for identifying the name of an Internet resource, starting with /a, if you need to log in. The interface to be called (such as adding, modifying; user information of the foreground, fund information, etc.) needs to add /u, ie: /a/u; generally put the table name or the word that can express this interface; request parameters and return Parameters usually include: field, description, type, comment, required or not.

Specifically, by clicking the Json test sample automatic generation tool, the data of the interface document can be called according to the outer field name in the interface description table of an interface document, and a test sample in the Json format is automatically generated. The interface description table refers to a table that generalizes the interface, including the name, field name, type, format, and the like of the interface document information; the outer field name refers to the field of the outermost interface in the interface document. For example, in the case of the inspection service, the information of the inspector is used as an outer field name, and the name, gender, ID number, etc. of the inspected person can be called from the interface document according to the information of the inspected person. Information data.

For example, taking the security service system as an example, the names of the outer field names of the interface description document mainly include: system code, salesperson code, effective date, hierarchical information, information of the inspected person, the total number of inspected persons, and the like. The Json test sample generation tool can be used to call various information data in the interface document through these outer field names.

In the embodiment of the present application, the JSON format is generated by the test sample, mainly because the data between the interfaces is transmitted in the Json format; optionally, the Json test sample automatic generation tool is generated by the VBA script.

Specifically, the test sample of the Json format mainly includes a request message and a response message. Please refer to FIG. 2, which shows an example diagram of the request message and the response message, as shown in FIG. 2(a), the request message The request method in the text is a method for sending a request to the interface, requesting the field name as the outer field name, and calling the data of the interface document according to the outer field name to make a specific request for the interface, “non-empty”, “length”, “ The type is to limit the format of the request message; as shown in Figure 2(b), the returned result in the response message is the result returned by the interface, and the return field name is the outer field name, according to the outer field name. The data of the calling interface document returns the specific result. "Non-empty", "length", and "type" are used to define the format of the response message. When the actual interface performs data communication, the interface receives the request packet, searches for the resource to be requested in the system or the platform according to the request packet, and converts the resource into a response packet after the resource is found.

Step S102: automatically generate a test case template according to the Json test sample, and automatically generate a Json test case according to the test case template, and then automatically generate a Jmeter test script according to the Json test case.

Interface testing includes testing many different interfaces. For example, in the interface test for purchasing insurance, you need to test the interfaces such as "customer authentication", "insurance information verification", "mobile phone number change", "insured" and so on. Therefore, the Json test samples of all interfaces can be gathered together to generate a Json test sample set, which facilitates centralized management of interface tests and subsequent integration tests, making the interface test process more intuitive. Please refer to FIG. 3, which shows an example diagram of a test sample set. As shown in FIG. 3, the interface test includes testing of N interfaces, the interface name refers to a process of the system under test, and the interface description means that the interface name is The corresponding process direction in the system, the data following the interface description is the request message and the response message corresponding to the Json sample generated by each interface document.

Specifically, a Json test sample is automatically generated according to each interface document, and then all Json test samples are grouped in a table to form a Json test sample set.

Then, by clicking the test case template generation tool, the test case template of all interfaces can be automatically generated according to the test sample set. The test case template mainly includes the request message and the result verification corresponding to the request message, please refer to FIG. It shows an example diagram of a test case template. Figure 4 is an example of a Json test sample with the request field name "Customer Authentication", where the call field name is a request with the request field name "Customer Authentication". The field name called by the method parameter, including "customer name", "gender", "date of birth", "document type", "document number", and then set the result verification according to the data of each call field name. The result is a security test on the interface, so that the interface can run normally in various scenarios. The result verification can be set according to the pre-defined interface test strategy and actual situation.

After inputting the value verified by the result, click the Json test case generation tool, you can generate a JSON format test case based on the test case module of an interface, and then click the Jmeter test case generation tool to generate the Jmeter format according to the Json format test case. The test script, jmx. is the suffix file; the Jmeter test script named after the interface name is generated in the preset storage path while generating the test script, for example, according to the "customer authentication" interface in the predetermined storage path (eg D hard drive) Generate a Jmeter test script for "Customer Authentication.jmx". Among them, Jmeter is a Java-based stress testing tool developed by the Apache organization, which can be applied to interface testing.

Optionally, the Json test case generation tool and the Jmeter test case generation tool are also generated by VBA scripts.

Step S103, generating an integrated test case according to the Jmeter test script, calling the integration test case through the test tool, and triggering the Jmeter test script to test through the integrated test case, and automatically outputting the test result.

Among them, the integration test case refers to the integration of all modules according to the design requirements (such as according to the structure diagram) into subsystems or systems for integration testing; the role of integration testing is that each unit and module can work normally. Under the premise, verify that the connection works for global operation.

Specifically, test cases are written into the integration test case of the integration test tool so that integration tests can be performed.

Optionally, the integration test tool uses the Ant integration test tool. Ant is a tool that automates the steps of compiling, testing, and deploying software. Most of them are used for software development in the Java environment.

Specifically, referring to FIG. 5, in step S103, the following sub-steps are further included:

Step S1031: Generate an integrated test case in an xml format according to the storage path and the result output path of the Jmeter test script.

Step S1032, running the Ant integration test tool to call the integration test case, so that the integration test case triggers the Jmeter test script to test through the storage path of the Jmeter test script.

In step S1033, the test response message is automatically compared with the response message, and the test result is output according to the result output path.

Specifically, create an integration test case named BUILD.xml, generate a test case according to the format of the Ant integration tool, and input the storage path of the Jmeter test script and the test result path to be output into the BUILD.xml integration test case.

By running Ant's integrated test tool, you can call the integrated test case of BUILD.xml. The integration test case then triggers the Jmeter test case to perform the integration test through the storage path of the Jmeter test script. After the test is completed, the test result is output according to the input test result path.

The test result is that the response message obtained after running the test is automatically compared with the response message in the Json sample. If the test result is consistent with the expected result, the interface meets the usage requirements and can be used normally, if the test result and expectation If the results are inconsistent, the interface is faulty and needs to be further improved.

Further, since the test case is a Jmeter format script, as an implementation manner, the Jmeter test tool can be used to directly call the Jmeter test case to perform interface test. It should be understood that Jmeter can only perform interface test on one interface. That is, integration testing cannot be performed, but testing with Jmeter can simulate stress testing by means of concurrent threads, and has better effect on performance testing of interface testing. Therefore, Jmeter can be used to perform interface testing of a single interface before integration. Testing to make interface testing more complete. Among them, the performance test mainly includes: response speed, interface fault tolerance, interface load and other performance tests.

Further, when the interface is added, deleted, or modified, the test code needs to be maintained. In the embodiment of the present application, the specific maintenance process is: obtaining a modified interface document from a developer, and then sequentially generating a Json test sample, a Json test case, and a Jmeter test case according to the modified interface file, and then writing the Jmeter test case. In the integration test case, the test tool is called to test the test case and output the test result. In the process of performing maintenance, the interface automatic test method provided by the embodiment of the present application can make the whole maintenance process relatively simple and high in efficiency.

For example, when adding an interface, obtain a new interface document, click the Json sample generation tool to automatically generate a Json sample based on the newly added interface document, and then click the test case template generation tool to automatically generate a test case based on the Json sample. Module, optionally, you can put the Json sample into the Json sample set for centralized management. When you click the test case template generation tool, you can generate test case templates only for the Json sample generated by the new interface. Other interfaces The same is true, so you only need to input the result verification data of the new interface into the test case template. The result verification data of other interfaces does not need to be re-entered; then, click the Json test case generation tool according to the test case of the new interface. The template automatically generates Json test cases, and then clicks the Jmeter test case generation tool to automatically generate Jmeter test cases. Next, add the newly generated Jmeter test case storage path to the integrated test case of BUILD.xml, and run the Ant integration test tool. Call the Jmeter test case to test by integrating test cases and output new Test Results.

The interface automatic test method provided by the embodiment of the present application automatically generates a test case from the interface document through an automated generation tool, and then uses the integrated test tool to call the test case for interface test, automatically outputs the test result, and verifies the performance and security of the test result. To guide the correction and improvement of the interface; when there is a modified interface, the test case can be automatically generated only by modifying the interface part, and the test cases of other interfaces need not be regenerated, the maintenance process is relatively simple and the efficiency is high; During the whole test process, the corresponding automatic data generation tool automatically generates the corresponding transition data, which reduces the requirements of the interface tester, improves the degree of automation, and improves the interface test efficiency.

The following are device embodiments of the present application. For details that are not described in detail in the device embodiments, reference may be made to the corresponding method embodiments.

Please refer to FIG. 6 , which is a schematic structural diagram of an interface automatic testing apparatus provided by an embodiment of the present application.

As shown in FIG. 6, the interface automation test apparatus 20 includes a sample generation module 201, a script generation module 202, and an interface test module 203.

The sample generation module 201 is configured to obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document.

Specifically, the sample generation module 201 can automatically generate a test sample of the Json format according to the outer field name in the interface description table of an interface document by running the Json test sample automatic generation tool, Json. The test samples of the format mainly include request messages and response messages.

Optionally, the Json test sample auto-generation tool is generated by a VBA script.

The script generation module 202 is configured to automatically generate a test case template according to the Json test sample, automatically generate a Json test case according to the test case module, and automatically generate a Jmeter test script according to the Json test case.

Specifically, the sample generation module 201 automatically generates a Json test sample according to each interface document, and then the script generation module 202 sets all the Json test samples in a table to form a Json test sample set.

Then, the script generation module 202 can automatically generate a test case template of all interfaces according to the test sample set by running the test case template generation tool. The test case template mainly includes the request message and the result verification corresponding to the request message.

Next, the script generation module 202 obtains the specific value of the result verification. By running the Json test case generation tool, the JSON format test case can be generated according to the test case module of an interface, and then the Jmeter test case generation tool can be executed according to the Jmeter test case generation tool. Test cases in Json format generate test scripts in Jmeter format.

The interface test module 203 is configured to generate an integrated test case according to the Jmeter test script, invoke the integration test case through the test tool, and trigger the Jmeter test script to test through the integrated test case, and automatically output the test result.

Specifically, the interface test module 203 writes the Jmeter test script into an integrated test case of the integrated test tool.

Optionally, the integration test tool adopts an Ant integration test tool, and the interface test module 203 creates an integration test case named BUILD.xml, generates a test case according to the format of the Ant integration tool, and simultaneously stores the storage path of the Jmeter test script and outputs The test result path is entered into the BUILD.xml integration test case.

The interface test module 203 calls the integration test case of BUILD.xml by running Ant's integrated test tool, so that the integration test case triggers the Jmeter test case to perform the integration test through the storage path of the Jmeter test script, and outputs the path according to the input test result after the test is completed. Test Results.

Further, since the test case is a script in the Jmeter format, as an embodiment, the interface test module 203 can directly call the Jmeter test case to test the interface by using the Jmeter test tool. It should be understood that the Jmeter can only be used for one interface. Interface testing, that is, integration testing is not possible, but testing with Jmeter can simulate stress testing by means of concurrent threads, and has better effect on performance testing of interface testing. Therefore, interface testing module 203 can use Jmeter for single testing. After the interface test of the interface, the integration test is performed to make the interface test more complete.

Further, when the interface is added, deleted, or modified, the test code needs to be maintained. In the embodiment of the present application, the specific maintenance process is: the interface automation testing device 20 obtains the modified interface document through the sample generation module 201, generates a modified Json test sample, and then the script generation module 202 sequentially according to the Json test sample. The test case template, the Json test case, and the Jmeter test case are generated. Finally, the modified Jmeter test case is written into the integrated test case by the interface test module 203, and the test tool is called to test the test case and output the test result.

The interface automatic testing device provided by the embodiment of the present application automatically generates test cases step by step from the interface document through the automatic generation tool, and then uses the integrated test tool to call the test case for interface test, automatically outputs the test result, and verifies the performance and security of the test result. To guide the correction and improvement of the interface; when there is a modified interface, the test case can be automatically generated only by modifying the interface part, and the test cases of other interfaces need not be regenerated, the maintenance process is relatively simple and the efficiency is high; During the whole test process, the corresponding automatic data generation tool automatically generates the corresponding transition data, which reduces the requirements of the interface tester, improves the degree of automation, and improves the interface test efficiency.

Another embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions that, when executed by one or more processors, cause one or more processors The interface automatic test method in the foregoing embodiment is executed. To avoid repetition, details are not described herein again. Alternatively, when the computer readable instructions are executed by one or more processors, the one or more processors are configured to perform the functions of the modules/units in the interface automation test apparatus in the above embodiments. To avoid repetition, details are not described herein again.

Please refer to FIG. 7, which shows a schematic diagram of a terminal device of the present embodiment. The terminal device 60 includes a processor 61, a memory 62, and computer readable instructions 63 stored in the memory 62 and executable on the processor 61. The processor 61 executes the computer readable instructions 63 to implement the various steps of the interface automation test method of the above-described embodiments, such as steps S101, S102, and S103 shown in FIG. Alternatively, when the processor 61 executes the computer readable instructions 63, the functions of the modules/units of the interface automation test apparatus in the above embodiments are implemented, for example, the functions of the sample generation module 201, the script generation module 202, and the interface test module 203 shown in FIG. .

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

An interface automatic testing method, characterized in that the method comprises the following steps:

Obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document;

Generating a test case template automatically according to the Json test sample, and automatically generating a Json test case according to the test case template, and automatically generating a Jmeter test script according to the Json test case;

Generating an integrated test case according to the Jmeter test script, calling the integrated test case through a test tool, and triggering the Jmeter test script to test by the integrated test case, and automatically outputting the test result.
The interface automation test method according to claim 1, wherein the obtaining an interface document of a different interface, and automatically generating a Json test sample of different interfaces according to the interface document, comprising:

The interface document of the interface is obtained, and the data of the interface document is automatically generated according to the outer field name of the interface document to automatically generate a test sample of the Json format of the interface. The test sample includes a request message and a response message.
The interface automation test method according to claim 2, wherein said automatically generating a test case template according to said Json test sample, and automatically generating a Json test case according to said test case template, and then according to said Json test Use cases automatically generate Jmeter test scripts, including:

Automatically generating a test case template according to the Json test sample, inputting the value of the result verification into the test case template, automatically generating a Json test case according to the test case template, and finally automatically generating a Jmeter according to the Json test case. Test script

Alternatively, the Json test sample set of the different interfaces is generated to generate a Json test sample set, and the test case template of each interface included in the Json test sample set is automatically generated according to the Json test sample set, and the result is verified. The values are respectively input into the test case template, and then the Json test cases are automatically generated according to the test case templates, and finally the Jmeter test scripts are automatically generated according to the Json test cases.
The interface automation test method according to claim 3, wherein the generating an integration test case according to the Jmeter test script, calling the integration test case by a test tool, and triggering the Jmeter by the integration test case Test scripts are tested and automatically output test results, including:

Generating an integrated test case in an xml format according to the storage path and the result output path of the Jmeter test script;

Running the Ant integration test tool to invoke the integrated test case in the xml format, so that the integration test case triggers the Jmeter test script to test through the storage path of the Jmeter test script;

The test response message is automatically compared with the response message, and the test result is output according to the result output path.
The interface automation test method according to claim 4, wherein the generating an integration test case according to the Jmeter test script, calling the integration test case by a test tool, and triggering the Jmeter by the integration test case The test script is tested and the test results are automatically output. After that, it also includes:

When the interface is modified, obtaining the modified interface document, and sequentially generating a Json test sample, a test case template, a Json test case, a Jmeter test case, and an integrated test case according to the modified interface file, and then running the test. The tool calls the integrated test case to test and re-output the test result automatically.
An interface automatic test device, characterized in that the device comprises:

a sample generation module: an interface document for acquiring different interfaces, and automatically generating a Json test sample of different interfaces according to the interface document;

a script generation module: configured to automatically generate a test case template according to the Json test sample, automatically generate a Json test case according to the test case template, and automatically generate a Jmeter test script according to the Json test case;

The interface test module is configured to generate an integrated test case according to the Jmeter test script, invoke the integrated test case by using a test tool, and trigger the Jmeter test script to test by the integrated test case, and automatically output the test result.
The interface automation test apparatus according to claim 6, wherein the sample generation module is further configured to:

The interface document of the interface is obtained, and the data of the interface document is automatically generated according to the outer field name of the interface document to automatically generate a test sample of the Json format of the interface, where the test case includes a request message and a response message.
The interface automation test apparatus according to claim 7, wherein the script generation module is further configured to:

Automatically generating a test case template according to the Json test sample, inputting the value of the result verification into the test case template, automatically generating a Json test case according to the test case template, and finally automatically generating a Jmeter according to the Json test case. Test script

Alternatively, the Json test sample set of the different interfaces is generated to generate a Json test sample set, and the test case template of each interface included in the Json test sample set is automatically generated according to the Json test sample set, and the result is verified. The values are respectively input into the test case template, and then the Json test cases are automatically generated according to the test case templates, and finally the Jmeter test scripts are automatically generated according to the Json test cases.
The interface automation test apparatus according to claim 8, wherein the interface test module is further configured to:

Generating an integrated test case in an xml format according to the storage path and the result output path of the Jmeter test script;

Running the Ant integration test tool to invoke the integrated test case in the xml format, so that the integration test case triggers the Jmeter test script to test through the storage path of the Jmeter test script;

The test response message is automatically compared with the response message, and the test result is output according to the result output path.
The interface automation test apparatus according to claim 9, wherein said interface automatic test apparatus is further configured to:

When the interface is modified, obtaining the modified interface document, and sequentially generating a Json test sample, a test case template, a Json test case, a Jmeter test case, and an integrated test case according to the modified interface file, and then running the test. The tool calls the integrated test case to test and re-output the test result automatically.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:

Obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document;

Generating a test case template automatically according to the Json test sample, and automatically generating a Json test case according to the test case template, and automatically generating a Jmeter test script according to the Json test case;

Generating an integrated test case according to the Jmeter test script, calling the integrated test case through a test tool, and triggering the Jmeter test script to test by the integrated test case, and automatically outputting the test result.
The terminal device according to claim 11, wherein the obtaining an interface document of a different interface, and automatically generating a Json test sample of different interfaces according to the interface document, comprising:

The interface document of the interface is obtained, and the data of the interface document is automatically generated according to the outer field name of the interface document to automatically generate a test sample of the Json format of the interface. The test sample includes a request message and a response message.
The terminal device according to claim 12, wherein said automatically generating a test case template according to said Json test sample, and automatically generating a Json test case according to said test case template, and then automatically according to said Json test case Generate Jmeter test scripts, including:

Automatically generating a test case template according to the Json test sample, inputting the value of the result verification into the test case template, automatically generating a Json test case according to the test case template, and finally automatically generating a Jmeter according to the Json test case. Test script

Alternatively, the Json test sample set of the different interfaces is generated to generate a Json test sample set, and the test case template of each interface included in the Json test sample set is automatically generated according to the Json test sample set, and the result is verified. The values are respectively input into the test case template, and then the Json test cases are automatically generated according to the test case templates, and finally the Jmeter test scripts are automatically generated according to the Json test cases.
The terminal device according to claim 13, wherein said generating an integrated test case according to said Jmeter test script, calling said integrated test case through a test tool, and triggering said Jmeter test script by said integrated test case Test and automatically output test results, including:

Generating an integrated test case in an xml format according to the storage path and the result output path of the Jmeter test script;

Running the Ant integration test tool to invoke the integrated test case in the xml format, so that the integration test case triggers the Jmeter test script to test through the storage path of the Jmeter test script;

The test response message is automatically compared with the response message, and the test result is output according to the result output path.
The terminal device according to claim 14, wherein the integration test case is generated according to the Jmeter test script, the integration test case is invoked by a test tool, and the Jmeter test is triggered by the integration test case After the script performs the test and automatically outputs the test result, the processor further implements the following steps when executing the computer readable instruction:

When the interface is modified, obtaining the modified interface document, and sequentially generating a Json test sample, a test case template, a Json test case, a Jmeter test case, and an integrated test case according to the modified interface file, and then running the test. The tool calls the integrated test case to test and re-output the test result automatically.
One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps:

Obtain an interface document of different interfaces, and automatically generate a Json test sample of different interfaces according to the interface document;

Generating a test case template automatically according to the Json test sample, and automatically generating a Json test case according to the test case template, and automatically generating a Jmeter test script according to the Json test case;

Generating an integrated test case according to the Jmeter test script, calling the integrated test case through a test tool, and triggering the Jmeter test script to test by the integrated test case, and automatically outputting the test result.
The non-volatile readable storage medium according to claim 16, wherein the obtaining an interface document of a different interface, and automatically generating a Json test sample of different interfaces according to the interface document, comprising:

The interface document of the interface is obtained, and the data of the interface document is automatically generated according to the outer field name of the interface document to automatically generate a test sample of the Json format of the interface. The test sample includes a request message and a response message.
The non-volatile readable storage medium according to claim 17, wherein said automatically generating a test case template according to said Json test sample, and automatically generating a Json test case according to said test case template, and then The Json test case automatically generates a Jmeter test script, including:

Automatically generating a test case template according to the Json test sample, inputting the value of the result verification into the test case template, automatically generating a Json test case according to the test case template, and finally automatically generating a Jmeter according to the Json test case. Test script

Alternatively, the Json test sample set of the different interfaces is generated to generate a Json test sample set, and the test case template of each interface included in the Json test sample set is automatically generated according to the Json test sample set, and the result is verified. The values are respectively input into the test case template, and then the Json test cases are automatically generated according to the test case templates, and finally the Jmeter test scripts are automatically generated according to the Json test cases.
The non-volatile readable storage medium according to claim 18, wherein said generating an integrated test case according to said Jmeter test script, calling said integrated test case through a test tool, and passing said integrated test case Trigger the Jmeter test script to test and automatically output the test results, including:

Generating an integrated test case in an xml format according to the storage path and the result output path of the Jmeter test script;

Running the Ant integration test tool to invoke the integrated test case in the xml format, so that the integration test case triggers the Jmeter test script to test through the storage path of the Jmeter test script;

The test response message is automatically compared with the response message, and the test result is output according to the result output path.
The non-volatile readable storage medium according to claim 19, wherein said integrated test case is generated according to said Jmeter test script, said integrated test case is invoked by said test tool, and said integration test is passed The use case triggers the Jmeter test script to test, and after the step of automatically outputting the test result, the computer readable instructions are executed by one or more processors, such that the one or more processors further perform the following steps:

When the interface is modified, obtaining the modified interface document, and sequentially generating a Json test sample, a test case template, a Json test case, a Jmeter test case, and an integrated test case according to the modified interface file, and then running the test. The tool calls the integrated test case to test and re-output the test result automatically.