WO2018014580A1

WO2018014580A1 - Data interface test method and apparatus, and server and storage medium

Info

Publication number: WO2018014580A1
Application number: PCT/CN2017/078351
Authority: WO
Inventors: 曹静; 岑海菊; 张博文; 毛皓; 邹文涛
Original assignee: 平安科技（深圳）有限公司
Priority date: 2016-07-20
Filing date: 2017-03-28
Publication date: 2018-01-25
Also published as: CN106991040A; CN106991040B

Abstract

A data interface test method, comprising: acquiring a test case selection instruction input, by a terminal, into an interface test web page; according to the test case selection instruction, selecting an interface test case from a test case set; sending the selected interface test case to a test execution machine; receiving a test result generated after the test execution machine runs the selected interface test case, and storing same; and returning the test result to the terminal.

Description

Data interface test method, device, server and storage medium

The present application claims priority to Chinese Patent Application No. 201610581627.X filed on Jul. 20, 2016, the entire disclosure of which is incorporated herein by reference. in.

[Technical Field]

The present invention relates to the field of testing technologies, and in particular, to a data interface testing method, apparatus, server, and storage medium.

【Background technique】

At present, in the field of data interface testing technology, there are many schemes for writing interface test cases. When testing the same interface, interface test cases written by different testers may be different. When a data interface needs to be tested multiple times, there is no good management of the written interface test cases, which leads to the need to rewrite the interface test cases for each test, and fails to make full use of the previously written interface test cases.

However, when testing the same data interface multiple times, it may be necessary to rewrite the interface test case of the data interface for each test, resulting in the unused interface test cases being underutilized, resulting in waste of resources and rewriting. When the interface test case of the data interface takes a lot of time, the test efficiency of the data interface is seriously reduced.

[Summary of the Invention]

In accordance with various embodiments disclosed herein, a data interface testing method, apparatus, server, and storage medium are provided.

A data interface test method, including:

Obtaining a test case selection instruction input by the terminal in the interface test webpage;

Selecting an interface test case from the test case set according to the test case selection instruction;

Send the selected interface test case to the test execution machine;

Receiving the test result generated by the test execution machine running the selected interface test case and storing the test result; and

Returning the test result to the terminal.

A data interface testing device, the device comprising:

The instruction acquisition module is configured to obtain a test case selection instruction input by the terminal in the interface test webpage;

a test case selection module, configured to select an interface test case in the test case set according to the test case selection instruction;

a test case sending module, configured to send the selected interface test case to the test execution machine;

a test result storage module, configured to receive the test result generated by the test execution machine after running the selected interface test case and store the test result; and

a test result sending module, configured to return the test result to the terminal.

A server comprising a memory and a processor, the memory storing computer executable instructions, the computer executable instructions being executed by the processor, such that the processor performs the following steps:

Send the selected interface test case to the test execution machine;

Returning the test result to the terminal.

One or more non-volatile storage media storing computer-executable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

Send the selected interface test case to the test execution machine;

Returning the test result to the terminal.

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features, objects, and advantages of the invention will be apparent from the description and appended claims.

[Description of the Drawings]

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present application, and other drawings can be obtained according to the drawings without any creative work for those skilled in the art.

1 is an application environment diagram of a data interface test system in an embodiment;

2 is a functional block diagram of a server in a data interface test system in an embodiment;

3 is a schematic flow chart of a data interface test method in an embodiment;

4 is a schematic flow chart of steps of collecting an interface test case in an embodiment;

5 is a schematic flow chart of a data interface testing method in another embodiment;

6 is a schematic flow chart of steps of searching for a test execution machine in an embodiment;

7 is a flow chart showing the steps of generating a test result in one embodiment;

8 is a functional block diagram of a data interface test apparatus in an embodiment;

9 is a functional block diagram of a data interface testing device in another embodiment;

10 is a functional block diagram of a data interface testing device in still another embodiment;

11 is a functional block diagram of a test case sending module in an embodiment;

Figure 12 is a functional block diagram of a test result storage module in one embodiment.

【detailed description】

Exemplary embodiments embodying the features and advantages of the present application will be described in detail in the following description. It should be understood that the present invention is capable of various modifications in the various embodiments, and This application.

FIG. 1 is an application environment diagram of a data interface test system in an embodiment. The data interface test system includes a terminal 110, a server 120, and a test executive 130. The terminal 110 and the test execution machine 130 are connected to the server 120 through a network. The terminal 110, the server 120, and the test executive 130 may each be one or more.

2 is a functional block diagram of the server 120 in the data interface test system of FIG. 1 in one embodiment. As shown in FIG. 2, the server 120 includes a processor, a non-volatile storage medium, an internal memory, and a network interface connected by a system bus. The processor is used to provide computing and control capabilities to support the operation of the entire server 120. The non-volatile storage medium of the server 120 stores an operating system and computer executable instructions. The computer executable instructions are executable by a processor to implement a data interface testing method as provided by the following embodiments. The internal memory in server 120 provides a cached operating environment for operating systems and computer executable instructions in a non-volatile storage medium. The network interface is used for network communication with the terminal 110 or the test executive machine 130. It can be understood that the server 120 can be implemented by a separate server or a server cluster composed of multiple servers.

It will be understood by those skilled in the art that the structure shown in FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. The specific server may include a ratio. More or fewer components are shown in Figure 2, or some components are combined, or have different component arrangements.

As shown in FIG. 3, in one embodiment, a data interface test method is provided. This embodiment is applied to the server 120 in the data interface test system of FIG. 1 as an example. The server 120 runs a data interface. The test program implements the data interface test method through the data interface test program. The method specifically includes the following steps:

Step 302: Acquire a test case selection instruction input by the terminal in the interface test webpage.

Specifically, the terminal 110 sends an acquisition request of the interface test webpage to the server 120. After the server 120 receives the acquisition request of the interface test webpage, the server 120 returns the data of the interface test webpage to the terminal 110. The terminal 110 tests the webpage according to the data display interface of the interface test webpage returned by the server 120, and controls the data interface test system by using the interface test webpage displayed in the terminal. The tester inputs a test case selection instruction in the interface test webpage displayed by the terminal, and the terminal 110 sends the selection instruction of the test case to the server 120. The test case selection instruction may include a test case identifier, and the test case identifier is used to uniquely identify the test case, and may specifically be at least one of a test case name, a code, a keyword, and a data interface identifier. Test case (Test Case), also known as a test case, is a set of test inputs, execution conditions, and expected results for a test target to test the data interface of the test target or verify that the data interface meets a particular requirement.

Step 304: Select an interface test case in the test case set according to the test case selection instruction.

Specifically, after obtaining the test case selection instruction input by the terminal in the interface test webpage, the server 120 extracts the test case identifier in the test case selection instruction, and selects a test that matches the test case identifier in the test case set according to the test case identifier. Example. The test case identifier in the test case selection instruction may be one or more.

Step 306, the selected interface test case is sent to the test execution machine.

Specifically, after selecting the interface test case from the test case set, the server 120 searches the test execution machine 130 and sends the interface test case to the found test execution machine 130.

In one embodiment, the server 120 extracts the tags of the test execution machine from the selected interface test cases, and searches for the corresponding test execution machine 130 based on the extracted tags.

Step 308: Receive test results generated by the test execution machine running the selected interface test case and store the test results.

Specifically, after the server 120 sends the test case to the test execution machine 130, the test execution machine 130 extracts the interface information from the test case, generates a test data request according to the interface information, and the test execution machine 130 sends the test data request to the server 120. After receiving the test data request, the server 120 extracts the interface information in the test request data, searches for the test data corresponding to the extracted interface information, and returns the found test data to the test execution machine 130. The test execution machine 130 tests the test data returned by the server 120 according to the interface test case to generate test results. The test execution machine 130 sends the test result back to the server 120, and the server 120 stores the test result corresponding to the interface test case. Specifically, the test result is stored corresponding to the identifier of the interface test case.

In step 310, the test result is returned to the terminal.

Specifically, after the server 130 stores the test result returned by the test execution machine, the server sends the test result to the terminal 110, and the terminal 110 displays the test result in the interface test page.

In this embodiment, in the interface test webpage, the terminal may input a test case selection instruction, obtain a test case selection instruction input by the terminal, select an interface test case in the test case set according to the test case selection instruction, and do not need to rewrite the interface test. Example. The selected interface test case is sent to the configured test execution machine, and the test execution machine is not required to be reconfigured, and the test result of the interface test case selected by the test execution machine is obtained and stored, and the test result is returned to the terminal. In the process of testing the data interface, it is not necessary to rewrite the interface test case, and the terminal can directly input the test case selection instruction in the interface test webpage, so that the interface test case that has been edited can be selected in the test case set, and the interface test case is not needed. Reconfigure the test execution machine, directly send the selected interface test case to the configured test execution machine, so that the test execution machine uses the selected interface test case to test the data interface, saving the rewriting interface test case and configuring the test execution machine. Time, improve the efficiency of the test of the data interface.

As shown in FIG. 4, in an embodiment, step 302 further includes the step of collecting an interface test case, the step specifically including the following:

Step 402: Collect interface test cases written by each terminal in the interface test webpage.

Specifically, the tester can write an interface test case in the interface test webpage displayed by the terminal 110. After the interface test case is written, the save command is triggered, and the terminal sends the interface test case written in the interface test webpage to the server 120. The different terminals 110 are different from each other, and the server 120 collects different interface test cases sent by different terminals 110.

In one embodiment, the tester can upload a locally saved interface test case through the interface test web page displayed by the terminal 110.

In step 404, the collected interface test cases are stored in the test case set.

Specifically, the server 120 stores the collected interface test cases sent by the terminals 110 in the test case set, extracts the identifier of the interface test case, sends the identifier of the interface test case to each terminal 110, and tests the interface according to the terminal 110. The identity of the use case is displayed on the interface test web page.

In this embodiment, the interface test cases written by the terminals in the interface test webpage are collected, and the collected interface test cases are stored in the test case set, and the interface test cases in the test case set can be uniformly managed and can be The interface test cases stored in the test case set are used multiple times to improve the utilization of the interface test cases.

As shown in FIG. 5, in an embodiment, a data interface test method is provided, and the method specifically includes the following steps:

Step 502: Acquire a test case selection instruction input by the terminal in the interface test webpage.

Step 504: Select an interface test case in the test case set according to the test case selection instruction.

In step 506, it is detected whether there is a test result corresponding to the selected interface test case; if it is detected, step 508 is performed; if not, step 510 is performed.

Specifically, after selecting the interface test case, the server 120 obtains the identifier of the interface test case, and detects whether there is a test result corresponding to the identifier of the interface test case in the database.

Step 508: Delete the test result corresponding to the selected interface test case.

Specifically, when the server 120 detects that there is a test result corresponding to the interface test case, the server 120 deletes the test result and proceeds to step 510.

In step 510, the selected interface test case is sent to the test execution machine.

Step 512: Receive test results generated by the test execution machine running the selected interface test case and store the test results.

In step 514, the test result is returned to the terminal.

In this embodiment, after the interface test case is selected, the selected interface test case is detected to have a corresponding test result. When the test result of the selected interface test case is detected, the detected test result is deleted, and the detected test result is deleted. When the interface test case is used again for testing, the test result that is already existing is prevented from being affected by the test result generated by the retest, and the accuracy of the test is improved.

As shown in FIG. 6, in an embodiment, step 306 further includes the step of searching for a test execution machine, the step specifically including the following:

Step 602: Obtain a resource occupancy rate of each test execution machine according to the selected interface test case.

Specifically, the server 120 obtains the resource occupancy rate of each test execution machine in the selected interface test case, and the resource occupancy rate may be at least one of the memory usage rate of the test execution machine 130, the occupancy rate of the central processing unit, and the thread occupancy rate. Kind.

In one embodiment, the server 120 extracts the label of the test execution machine in the selected interface test case. The label of the test execution machine corresponds to multiple test execution machines, and the server 120 acquires the resource occupancy rate of each test execution machine 130.

Step 604: Find a test execution machine with the smallest resource occupancy rate.

Specifically, when the resource occupancy rate of each test execution machine is obtained, the server 120 compares the resource occupancy rate of each test execution machine 130, and selects the test execution machine 130 with the smallest resource occupancy rate.

Step 606: Transfer the selected interface test case to the found test execution machine.

Specifically, the server 130 transmits the selected interface test case to the test execution machine 130 with the smallest resource occupancy, and the test execution machine 130 performs the test according to the received interface test case.

In this embodiment, the test execution machine with the smallest resource occupancy rate is searched, and the selected interface test case is transmitted to the found test execution machine, so that the test execution machine with the smallest resource occupancy rate tests the data interface according to the interface test case. In this way, the execution interface test case waits due to the busy test execution machine is avoided, the time spent waiting for the execution of the interface test case is saved, and the test speed of the data interface is accelerated.

As shown in FIG. 7, in an embodiment, step 308 specifically includes the step of generating a test result, the step specifically including the following:

Step 702: Receive a test data acquisition request generated by the test execution machine according to the interface identifier, where the interface identifier is extracted by the test execution machine from the selected interface test case.

Specifically, the test execution machine 130 receives the interface test case sent by the server 120, and the test execution machine 130 parses the received interface test case, and extracts the interface identifier of the interface to be tested from the interface test case, and the interface identifier is an interface. The unique identifier, the interface identifier may specifically be the path of the access interface. After the test execution device 130 extracts the interface identifier, the test data acquisition request is generated according to the interface identifier, and the test data acquisition request is used to obtain the test data from the interface corresponding to the interface identifier. The test execution machine 130 transmits a test data acquisition request to the server 120.

Step 704, returning test data to the test execution machine according to the test data acquisition request.

Specifically, after receiving the test data acquisition request, the server 120 parses the test data acquisition request, extracts the interface identifier from the test data acquisition request, searches for an interface corresponding to the interface identifier, and obtains corresponding test data from the found interface. The server 120 returns the acquired test data to the test execution machine 130.

Step 706: Receive test results generated by the test execution machine based on the test data and the expected data in the interface test case.

Specifically, after receiving the test data returned by the server 120, the test execution machine 130 extracts the expected data from the interface test case, compares the test data with the expected data, and generates a test result according to the comparison result, and the test execution machine 130 generates the generated test result. The test result is returned to the server 120.

In one embodiment, the test execution machine 130 may obtain expected data and test data from the server 120, compare the test data with the expected data to generate a test result; or, the test execution machine 130 performs an operation on the test data to obtain an operation result, and the operation is performed. The results are compared to the expected data to generate test results. The test result may specifically be a test report, and the test report includes at least one of a test time, an interface identifier of the test interface, and a test error existing in the test data.

In this embodiment, after receiving the test data acquisition request generated by the test execution machine according to the interface identifier, the test data is returned to the test execution according to the test data acquisition request, and the test execution machine generates the test according to the test data and the expected data in the interface test case. As a result, by comparing the expected data with the test data, it is possible to accurately determine the error of the interface during the test and improve the accuracy of the test result.

As shown in FIG. 8 , in one embodiment, a data interface testing apparatus 800 is provided. The apparatus specifically includes: a selection instruction acquisition module 802, a test case selection module 804, a test case sending module 806, a test result storage module 808, and The test result is sent to the module 810.

The instruction acquisition module 802 is configured to obtain a test case selection instruction input by the terminal in the interface test webpage.

The test case selection module 804 is configured to select an interface test case in the test case set according to the test case selection instruction.

The test case sending module 806 is configured to send the selected interface test case to the test execution machine.

The test result storage module 808 is configured to receive and store the test result generated after the interface test case selected by the test execution machine is run.

The test result sending module 810 is configured to return the test result to the terminal.

As shown in FIG. 9 , in one embodiment, the data interface testing apparatus 800 specifically includes: a test case collection module 812 and a test case storage module 814.

The test case collection module 812 is configured to collect interface test cases written by each terminal in the interface test webpage.

The test case storage module 814 is configured to store the collected interface test cases into the test case set.

As shown in FIG. 10, in one embodiment, the data interface testing apparatus 800 specifically includes a test result detecting module 816 and a test result deleting module 818.

The test result detecting module 816 is configured to detect whether there is a test result corresponding to the selected interface test case.

The test result deletion module 818 is configured to delete the test result corresponding to the selected interface test case when detecting the test result corresponding to the selected interface test case.

The test case sending module 806 is further configured to send the selected interface test case to the test execution machine when detecting that the test result corresponding to the selected interface test case does not exist.

As shown in FIG. 11, in one embodiment, the test case sending module 806 specifically includes:

The occupancy acquisition module 806a is configured to obtain the resource occupancy rate of each test execution machine according to the selected interface test case.

The execution machine search module 806b is configured to find a test execution machine with the smallest resource occupancy rate.

The test case transmission module 806c is configured to transmit the selected interface test case to the found test execution machine.

As shown in FIG. 12, in one embodiment, the test result storage module 808 specifically includes:

The acquisition request receiving module 808a is configured to receive a test data acquisition request generated by the test execution machine according to the interface identifier, where the interface identifier is extracted by the test execution machine from the selected interface test case.

The test data return module 808b is configured to return test data to the test execution machine according to the test data acquisition request.

The test result receiving module 808c is configured to receive test results generated by the test execution machine according to the test data and the expected data in the interface test case.

The various modules in the above data interface test apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The network interface may be an Ethernet or a wireless network card. The above modules may be embedded in the hardware in the processor or in the memory in the server, or may be stored in the memory in the server, so that the processor calls the corresponding operations of the above modules. The processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.

One of ordinary skill in the art can understand that all or part of the process of implementing the foregoing embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-described embodiments are merely illustrative of several embodiments of the present invention, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A data interface test method, including:

Obtaining a test case selection instruction input by the terminal in the interface test webpage;

Selecting an interface test case from the test case set according to the test case selection instruction;

Send the selected interface test case to the test execution machine;

Receiving the test result generated by the test execution machine running the selected interface test case and storing the test result; and

Returning the test result to the terminal.
The method according to claim 1, wherein the method further comprises: before the obtaining the test case selection instruction input by the terminal in the interface test webpage, the method further comprises:

Collecting interface test cases written by each terminal in the interface test webpage; and

Store the collected interface test cases into the test case collection.
The method according to claim 1, wherein after the selecting the interface test case in the test case set according to the test case selection instruction, the method further comprises:

Detect whether there is a test result corresponding to the selected interface test case;

If detected, deleting the test result corresponding to the selected interface test case; and

If not detected, the step of transmitting the selected interface test case to the test execution machine is performed.
The method according to claim 1, wherein the sending the selected interface test case to the test execution machine comprises:

Obtaining the resource occupancy rate of each test execution machine according to the selected interface test case;

Finding the test execution machine with the smallest resource occupancy rate; and

The selected interface test case is transmitted to the found test execution machine.
The method according to claim 1, wherein the receiving the test result generated by the test execution machine after running the selected interface test case and storing comprises:

Receiving a test data acquisition request generated by the test execution machine according to the interface identifier, where the interface identifier is extracted by the test execution machine from the selected interface test case;

Returning test data to the test execution machine according to the test data acquisition request; and

Receiving test results generated by the test execution machine based on the test data and expected data in the interface test case.
A data interface testing device includes:

The instruction acquisition module is configured to obtain a test case selection instruction input by the terminal in the interface test webpage;

a test case selection module, configured to select an interface test case in the test case set according to the test case selection instruction;

a test case sending module, configured to send the selected interface test case to the test execution machine;

a test result storage module, configured to receive the test result generated by the test execution machine after running the selected interface test case and store the test result; and

a test result sending module, configured to return the test result to the terminal.
The device according to claim 6, further comprising:

a test case collection module, configured to collect an interface test case written by each terminal in the interface test webpage; and

A test case storage module for storing the collected interface test cases into a test case set.
The device according to claim 6, further comprising:

a test result detecting module, configured to detect whether there is a test result corresponding to the selected interface test case;

The test result deleting module is configured to delete the test result corresponding to the selected interface test case when detecting the test result corresponding to the selected interface test case; and

The test case sending module is further configured to send the selected interface test case to the test execution machine when detecting that the test result corresponding to the selected interface test case does not exist.
The device according to claim 6, wherein the test case sending module comprises:

An occupancy acquisition module, configured to obtain a resource occupancy rate of each test execution machine according to the selected interface test case;

Executing a machine search module for finding a test execution machine with the smallest resource occupancy rate; and

A test case transmission module is configured to transmit the selected interface test case to the found test execution machine.
The device according to claim 6, wherein the test result storage module comprises:

a request receiving module, configured to receive a test data acquisition request generated by the test execution device according to the interface identifier, where the interface identifier is extracted by the test execution machine from the selected interface test case;

a test data returning module, configured to return test data to the test execution machine according to the test data acquisition request; and

And a test result receiving module, configured to receive a test result generated by the test execution machine according to the test data and expected data in the interface test case.
A server comprising a memory and a processor, the memory storing computer executable instructions, the computer executable instructions being executed by the processor, such that the processor performs the following steps:

Obtaining a test case selection instruction input by the terminal in the interface test webpage;

Selecting an interface test case from the test case set according to the test case selection instruction;

Send the selected interface test case to the test execution machine;

Receiving the test result generated by the test execution machine running the selected interface test case and storing the test result; and

Returning the test result to the terminal.
The server according to claim 11, wherein said acquiring terminal causes said processor to be executed by said processor before said test case selection instruction input in said interface test webpage Perform the following steps:

Collecting interface test cases written by each terminal in the interface test webpage; and

Store the collected interface test cases into the test case collection.
The server according to claim 11, wherein said computer executable instructions are executed by said processor after said test case selection instruction selects an interface test case in said test case set The processor performs the following steps:

Detect whether there is a test result corresponding to the selected interface test case;

If detected, deleting the test result corresponding to the selected interface test case; and

If not detected, the step of transmitting the selected interface test case to the test execution machine is performed.
The server according to claim 11, wherein the sending the selected interface test case to the test execution machine comprises:

Obtaining the resource occupancy rate of each test execution machine according to the selected interface test case;

Finding the test execution machine with the smallest resource occupancy rate; and

The selected interface test case is transmitted to the found test execution machine.
The server according to claim 11, wherein the receiving the test result generated by the test execution machine after running the selected interface test case and storing comprises:

Receiving a test data acquisition request generated by the test execution machine according to the interface identifier, where the interface identifier is extracted by the test execution machine from the selected interface test case;

Returning test data to the test execution machine according to the test data acquisition request; and

Receiving test results generated by the test execution machine based on the test data and expected data in the interface test case.
One or more non-volatile storage media storing computer-executable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

Obtaining a test case selection instruction input by the terminal in the interface test webpage;

Selecting an interface test case from the test case set according to the test case selection instruction;

Send the selected interface test case to the test execution machine;

Receiving the test result generated by the test execution machine running the selected interface test case and storing the test result; and

Returning the test result to the terminal.
The non-volatile storage medium according to claim 16, wherein said computer-executable instruction is executed by one or more processors before said acquisition terminal selects an instruction input in said interface test web page And causing the one or more processors to perform the following steps:

Collecting interface test cases written by each terminal in the interface test webpage; and

Store the collected interface test cases into the test case collection.
The non-volatile storage medium according to claim 16, wherein said computer executable instructions are processed by one or more after said interface test case is selected in said test case set according to said test case selection instruction When executed, the one or more processors are caused to perform the following steps:

Detect whether there is a test result corresponding to the selected interface test case;

If detected, deleting the test result corresponding to the selected interface test case; and

If not detected, the step of transmitting the selected interface test case to the test execution machine is performed.
The non-volatile storage medium according to claim 16, wherein the sending the selected interface test case to the test execution machine comprises:

Obtaining the resource occupancy rate of each test execution machine according to the selected interface test case;

Finding the test execution machine with the smallest resource occupancy rate; and

The selected interface test case is transmitted to the found test execution machine.
The non-volatile storage medium according to claim 16, wherein the receiving the test result generated by the test execution machine after running the selected interface test case and storing comprises:

Receiving a test data acquisition request generated by the test execution machine according to the interface identifier, where the interface identifier is extracted by the test execution machine from the selected interface test case;

Returning test data to the test execution machine according to the test data acquisition request; and

Receiving test results generated by the test execution machine based on the test data and expected data in the interface test case.