WO2020155778A1

WO2020155778A1 - Interface automation test method, test apparatus, test device and storage medium

Info

Publication number: WO2020155778A1
Application number: PCT/CN2019/118701
Authority: WO
Inventors: 师江帆
Original assignee: 苏州市龙测智能科技有限公司
Priority date: 2019-02-03
Filing date: 2019-11-15
Publication date: 2020-08-06
Also published as: CN109857667B; CN109857667A

Abstract

An interface automation test method, a test apparatus, a test device and a storage medium, the test method comprising: acquiring interface set information of an object to be tested (S1), comprising various interface nodes and interface descriptions thereof; sorting related interface nodes in sequence according to a function to be tested, and establishing an association between output parameters of the previous interface node and input parameters of the next interface node among two adjacent interface nodes to obtain an interface flowchart; performing depth traversal on the interface flowchart in view of input parameters of a preset interface node, and generating a corresponding test code according to each complete branch path from a traversal start node backwards (S3), the test code comprising a program that calls interface nodes; and running the test code in a test running environment to obtain a test result (S4). The described method uses an interface endpoint process and configured parameters to automatically generate a test code used for testing an interface, thus an automation test may be completed by running the code in a test environment.

Description

Interface automatic test method, test device, test equipment and storage medium

Technical field

The invention relates to the technical field of computer testing, in particular to an interface automatic testing method, testing device, testing equipment and storage medium.

Background technique

With the development of software technology, more and more software provides services to users through platformization. Third parties can customize their own services according to the interfaces provided by the platform. Therefore, software nowadays often involves interface testing. Interfaces are pre-defined functions. The purpose is to provide applications and developers with the ability to access a set of routines based on certain software or hardware without having to access the source code or understand the details of the internal working mechanism. Interface testing is a test that submits input data to the interface, obtains the returned results, and analyzes whether the results meet expectations.

The interface testing method in the prior art is as follows: the tester pre-writes the test case corresponding to the interface to be tested, sends the interface request message corresponding to the test case to the interface to be tested, and receives the response message fed back by the interface to be tested, according to the test case corresponding The interface request message and response message determine the test result. In practical applications, each interface corresponds to a parameter, each parameter may have multiple values, and each test case includes the values of all parameters. In order to ensure the comprehensiveness of interface testing, testers need to write multiple test cases so that the multiple test cases can cover all combinations of parameter values.

Since testers need to manually write test cases in the prior art, when there are many interface parameters, testers need to manually write dozens or even hundreds of test cases, which makes the efficiency of test case writing low and leads to interface testing The efficiency is low, and test cases are easily missed, and the interface test process cannot be effectively traced.

Summary of the invention

In order to solve the problems of the prior art, the present invention provides an interface automatic test method, test device, test equipment and storage medium, which use the interface process and configured parameters to automatically generate test code for testing the interface of the software to be tested. And generate a clear test report, the technical solution is as follows:

In one aspect, the present invention provides a method for automatic interface testing, which includes the following steps:

Acquiring interface set information of the object to be tested, the interface set information including each interface node and an interface description corresponding to each interface node, the interface description including input parameters and output parameters;

According to the function to be tested, arrange the relevant interface nodes in order, and associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flowchart;

Combining the preset parameter types and parameter values of the input parameters of the interface node, the interface flowchart is deeply traversed, and the corresponding test code is generated according to each complete branch path from the traversal start node to the back. The test The code includes programs to call each interface node;

Run the test code in the test run environment to obtain the test result.

Further, the method further includes obtaining an assertion setting result before or after obtaining the interface flowchart, where the assertion setting result is an expected value set for the output parameter output after calling the corresponding interface node;

Generating the test code includes: quoting the program of the assertion judgment operation after calling the interface node corresponding to the set expected value.

Further, the method further includes obtaining an initialization parameter configuration result after obtaining the interface flow chart, the initialization parameter configuration result includes a test start interface node, and the initialization parameter configuration result is used to realize parameter initialization when the test code is generated, It includes: initializing the traversal start node as the test start interface node, and the test start interface node may be any interface node in the interface flowchart.

Further, the initialization parameter configuration result further includes a test depth value, and the configuration value of the test depth value is greater than or equal to the longest depth value of the flow chart starting from the configured test start interface node.

Further, the method further includes obtaining an input parameter configuration result before or after obtaining the interface flowchart, where the input parameter configuration result includes the input parameters required to implement the calling interface node;

Generating the test code includes: assigning the above-mentioned input parameter configuration result to the program of the input parameter at the corresponding calling interface node.

Further, the steps of establishing the interface flowchart include the following operations:

Based on the situation that different interface nodes correspond to the same previous interface node, the different interface nodes are set in different branch paths, and/or

Based on the situation that the first interface node is the previous interface node of the second interface node and the second interface node is the previous interface node of the third interface node, the first interface node, the second interface node, and the third interface node Set in the same branch path.

Further, part or all of the interface flowchart can be moved, copied, cut and/or pasted.

Optionally, the step of running the test code in the test run environment includes a local run mode and/or a cloud run mode, and the local run mode includes: downloading the test code from the cloud to a local computer, and Run the test code in the test software in the computer to obtain the test result;

The cloud operation mode includes: sending an operation request to the cloud, the operation request including the object to be tested information; according to the operation request, obtaining the corresponding test code; receiving based on the operation request to run the test software in the cloud Describe the test results obtained by the test code.

Further, the test report of the test result includes a test failure case description, and the test failure case includes an interface call error and/or an assertion judgment error.

Further, the process information and data information in each test case obtained by running the test code in the test running environment are associated and stored separately.

On the other hand, the present invention provides an interface automatic test device, including the following modules:

The target module to be tested is used to obtain interface set information of the object to be tested, the interface set information includes each interface node and the interface description corresponding to each interface node, and the interface description includes input parameters and output parameters;

The flow chart module is used to arrange the related interface nodes in order according to the functions to be tested, and to associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flow chart;

The code generation module is used to combine preset parameter types and parameter values of the input parameters of the interface node to perform a deep traversal of the interface flowchart, and generate the corresponding branch path according to each complete branch path from the traversal start node backward Test code, the test code includes a program to call each interface node;

The running module is used to run the test code in the test running environment to obtain the test result.

In another aspect, the present invention provides an interface automation test equipment, including a processor and a memory, the memory stores a program, and when the processor executes the program, the following operations are performed:

Run the test code in the test run environment to obtain the test result.

In another aspect, the present invention provides a storage medium for storing a program, and the program performs the following operations when executed:

Run the test code in the test run environment to obtain the test result.

The beneficial effects brought by the technical solution provided by the present invention are as follows:

a. The interface flowchart strengthens the semantic support of the test software;

b. Use automatic code generation engine to automatically generate test code;

c. Separate and store the process and data in the test case, and effectively display it on the product to improve the convenience of testers;

d. Able to automate testing of interfaces in computer web pages, mobile terminal web pages, mobile terminal App, WeChat applet, WeChat official account, PC application, and industrial control software, with a wide range of applications;

e. The test report is comprehensive and accurate, the test process is traceable, and the test results are clear at a glance.

Description of the drawings

In order to explain the technical solutions in the embodiments of the present invention more clearly, the following will briefly introduce the accompanying drawings used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained from these drawings without creative work.

FIG. 1 is a flowchart of an interface automated testing method provided by an embodiment of the present invention;

Figure 2 is a schematic diagram of an interface flowchart provided by an embodiment of the present invention;

FIG. 3 is a flowchart of an interface automatic test method with parameter configuration and assertion added according to an embodiment of the present invention;

4 is a schematic diagram of modules of an interface automatic test device provided by an embodiment of the present invention;

Fig. 5 is a schematic diagram of modules of the interface automatic test device after the assertion setting and input parameter configuration of Fig. 4 are placed after the flow chart is established.

detailed description

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only It is a part of the embodiments of the present invention, not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

It should be noted that the terms "first" and "second" in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and not necessarily used to describe a specific sequence or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations of them are intended to cover non-exclusive inclusions. For example, a process, method, device, product, or device that includes a series of steps or units is not necessarily limited to the clearly listed Those steps or units may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

In an embodiment of the present invention, an automatic interface testing method is provided, as shown in Figure 1, including the following processes:

S1. Obtain the interface collection information of the object to be tested.

The present invention applies to protect the technology related to interface testing. The interface generally refers to the way of interaction between the front-end and the back-end. For example, in the case of Ctrip booking a hotel, the front-end needs to input parameters such as destination (such as Shanghai) and check-in time, and the back-end returns to this purpose List of hotels in the place. The test objects involved in the interface include mobile APP, webpage, WeChat applet, WeChat official account, PC application, industrial control software and other interfaces, which are hereinafter referred to as interfaces or interface nodes.

Specifically, the interface set information includes each interface node and the interface description corresponding to each interface node. The interface description includes input parameters and output parameters. For example, taking the Ctrip application as an example, when testing its hotel reservation function, The interfaces involved include hotel query interface, hotel list interface, hotel order interface, and order payment interface.

S2, the flow chart of establishing the interface.

Specifically, according to the function to be tested, the related interface nodes are arranged in order, and the output parameters of the previous interface node among the two adjacent interface nodes are associated with the input parameters of the next interface node. The specific establishment process is as follows:

After getting the set of the entire interface of the software (such as Ctrip website) and the interface description (input parameters, output parameters) for each interface, according to the software requirements, press the relevant interface for a certain function (such as the Ctrip hotel reservation function) The order is arranged and organized, and then for every two interfaces, a certain field in the output of the previous interface corresponds to a certain parameter in the input of the next interface on its line. When all the functions are drawn, the interface flowchart is complete.

Based on the situation that different interface nodes correspond to the same previous interface node, the different interface nodes are set in different branch paths. For example, the Ctrip homepage interface corresponds to multiple sub-interfaces: hotel query interface, air ticket query interface, train ticket query Interface, scenic spot ticket query interface, etc.;

Based on the situation that the first interface node is the previous interface node of the second interface node and the second interface node is the previous interface node of the third interface node, the first interface node, the second interface node, and the third interface node Set in the same branch path, take the interface of the above hotel reservation function as an example: for the hotel query interface, the input parameters are query conditions (destination, time, additional conditions, etc.), and the output parameters are obtained under the specific query conditions Hotel list; use the hotel list parameter output by the hotel query interface as the input parameter of the hotel list interface, and the user selects a piece of hotel information in the hotel list, and the hotel list interface outputs the hotel information as an output parameter; Use this piece of hotel information (including hotel name, check-in date, price, etc.) as input parameters of the hotel order interface, and the user selects the payment method on the hotel order interface, and the hotel order interface outputs the payment method and payment amount as output parameters ; Use the output parameters of the above payment method and payment amount as the input parameters of the order payment interface, and finally get the interface flow chart as shown in Figure 2. The interface name and input/output parameter naming in the figure is only for illustration, and the actual bottom interface is The name in the script shall prevail.

S3. Perform an in-depth traversal of the interface flowchart, and generate corresponding test codes according to each complete branch path from the traversal start node backward.

Specifically, the process of using the code engine to generate the test code is actually the process of the code engine traversing the interface flow chart. The test code includes a program that calls each interface node: during the traversal process, when an interface node is detected, Get the parameter type and parameter value of the input parameter of the preset interface node to call the interface node. The interface can be called directly by calling the interface, such as the interface getHotelList(String destination), and then according to the input data destination=Shanghai, when running like this Just pass the data to getHotelList() to trigger this interface, get the parameter value of the output parameter, and then match the field from the output parameter as the input parameter of the next interface node, so as to complete the traversal path and start the traversal The interface node on each complete branch path behind the node.

S4. Run the test code in the test operation environment to obtain the test result.

Put the test code in the test running environment in the form of a template that meets the running conditions, run the test code, and obtain the test result. The operation methods include but are not limited to the following two methods:

Cloud operation mode: send a running request to the cloud, the running request includes the information of the object to be tested; the cloud server obtains the test code corresponding to the information of the object to be tested according to the operation request, and puts the test code in Project template to make it meet the operating requirements of the cloud test environment. For example, copy the test code to a folder at a specified address, call the source configuration file of the object to be tested, and use the source configuration file to The parameters in the project template are automatically filled, and the filled project template including the test code can be put into the cloud test software to run, and the test code is received by running the test code in the cloud test software based on the run request Test Results;

Local running mode: Download the corresponding test code from the cloud to the local computer, and run the test code in the test software in the computer. Before running the test code, it is also necessary to configure the project. The method is the same as the operation of putting the test code into the project template in the cloud operation mode. The difference is that the cloud operation mode is automatically completed by the cloud server, while the local operation mode is completed by the operating user. While downloading the test code, it also downloads the project template, source configuration file and operating instructions. The project configuration can be completed according to the operating instructions, put into the local test environment for operation, and the test results are obtained. It should be noted that if the carrier of the object information to be tested is a mobile terminal, the mobile terminal needs to be connected to the local computer first.

Wherein, the test software includes but is not limited to JMeter and Postman, both of which can be applied to test Android, iOS system, Web or PC interface.

For most objects that need to be tested, the initialization parameters, input parameters and assertion conditions need to be configured before the code is automatically generated. The method flow is shown in Figure 3. The following is the parameters before the corresponding test code is generated in step S3 Initialization is explained:

After obtaining the interface flowchart, the initialization parameter configuration is performed. The initialization parameter configuration result includes the test start interface node. The initialization parameter configuration result is used to initialize the parameters when the test code is generated, including: traversing the start node Initialized as the test start interface node, the test start interface node can be any interface node in the interface flow chart, it can be seen that the traversal start node can be the root interface node of the interface flow chart, It can also be a certain (not the last) interface node in the middle of the interface flowchart, and each complete branch path from the traversal start node to the last interface node. In an embodiment of the present invention, The interface flowchart is a process tree structure (one-way), or in a preferred embodiment of the present invention, two interface nodes in the interface flowchart can be called in both directions. For example, in Figure 2, the user selects in the hotel list After a certain piece of hotel information, call the hotel order interface. After calling the hotel order interface, you can call the hotel order interface again by entering the parameter back. After reselecting a piece of hotel information, call the hotel order interface again. In this case, use the hotel The query interface is the interface node process under the complete traversal path of the traversal starting node: hotel query interface→hotel list interface→hotel order interface→hotel list interface→hotel order interface→order payment interface. The traversal start node can select any node in the middle of the process, so that when a new function needs to be tested, there is no need to retest from the beginning, but only the interface node with the new function added as the traversal start node , Effectively improve test efficiency. The automated test system in the prior art cannot achieve partial testing of only added new functions, resulting in low automated testing efficiency and lengthy testing process.

In addition to the test start interface node, the initialization parameter configuration result also includes a test depth value, and the configuration value of the test depth value is greater than or equal to the longest depth value of the flow chart starting from the configured test start interface node, where: The depth configuration value is equal to the longest depth value of the flow chart starting from the configured test start interface node, which can ensure that each branch path flow from the test start interface node can be completely traversed; if there are multiple branch paths There are interactions between them. For example, in the loan app, there is both a loan business process interface and a repayment business process interface. There is interaction between the loan business and the repayment business. For example, it should be the loan first and then the repayment, so if you want to test For the interactive function between the two branch paths, you need to set the page depth to the sum of the depth values of the two branch processes.

The following describes the input parameter configuration before generating the corresponding test code in step S3:

Obtain the input parameter configuration result before or after obtaining the interface flowchart (see Figure 4 and Figure 5). The input parameter configuration result includes the parameters required to call the interface node, such as the input parameters that need to be configured in the hotel query interface Including the hotel name, target city, check-in date and price, as well as filtering conditions, such as room type, area size, rental type, etc., for example, in the hotel order interface, you need to set the selection item information, such as selecting the second hotel After clicking the information, enter the hotel order interface. Through pre-set input parameters corresponding to each interface, in the process of generating test code, the code engine puts the user's input parameter settings in a suitable position, that is, assigns the above-mentioned input parameter configuration results to the input parameter elements at the corresponding called interface nodes In order to complete the matching of the input parameters to the next interface node.

The following describes the assertion configuration before generating the corresponding test code in step S3:

Perform assertion settings before or after obtaining the interface flowchart (see Figure 4 and Figure 5), the assertion setting result is the expected value set for a field in the output parameter output after calling the corresponding interface node; in the code generation process For a certain interface node with preset assertion configuration, after calling the interface node, refer to the assertion operation to make assertion judgment. For example, for the hotel query interface, if its input parameter is from February 14th to February 15th, For Beijing and Four Seasons Hotels, in the process of automatically generating test codes, the list table of the hotel list interface will be retrieved from the background. According to the list table configuration, the first column of the list is check-in time information, and the second column is check-out time information. The third column is the hotel address information, and the fourth column is the hotel name information. The assertion judgment inserted in the test code can be to judge whether the value in the first column of the list table is equal to "02-14" and whether the value in the second column is Equal to "02-15", or judge whether the value in the fourth column is equal to "Four Seasons Hotel", if not, the assertion fails, which is a case of failed test cases.

The test result includes a test report in text form, and the test report includes a test failure case description, such as interface call errors and/or assertion judgment errors, corresponding to the fail mark, click the fail mark, and the specific For details of failure, fields that do not meet expectations in the text report are preferably displayed in a highlighted form. In addition, the test report can also include performance index test results, such as the start time of the test for each interface, the return time of the interface, the time difference between the two is the total time spent by the interface, and this time can be used to detect it. Whether it is the bottleneck of the entire system.

In a preferred embodiment of the present invention, part or all of the interface flow chart can be moved, copied, cut and/or pasted, which provides greater convenience when establishing the interface flow chart and reduces repetitive work .

Further, the process information and data information in each test case obtained by running the test code in the test running environment are associated and stored separately, and effectively displayed on the product. Because the process and data are stored in different folders, the organization is clear, and the tester is clear at a glance. Whether it involves viewing or modifying the process or data, the work efficiency of the tester can be significantly improved.

The embodiment of the present invention provides an interface automatic testing method, which includes the following steps:

Obtain the interface set information of the object to be tested, the interface set information includes each interface node and the interface description corresponding to each interface node, the interface node is a way for front-end and back-end interaction, and the interface description includes input parameters and output parameters ；

According to the function to be tested, arrange the related interface nodes in order, and associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flow chart, including: Get the entire website After the collection of interfaces and the corresponding interface description for each interface, the related interfaces are arranged in order according to the functional requirements, and then for every two interfaces, a field in the output of the previous interface corresponds to the next one. A certain parameter in the input of the interface until the interface process of all functions is completed; based on the situation that different interface nodes correspond to the same previous interface node, the different interface nodes are set in different branch paths; based on the first interface When the node is the previous interface node of the second interface node and the second interface node is the previous interface node of the third interface node, the first interface node, the second interface node, and the third interface node are set in the same branch In the path, the name of the interface and input/output parameters shall be based on the name in the underlying interface script;

Perform initialization parameter configuration. The initialization parameter configuration result includes a test start interface node and a test depth value. The initialization parameter configuration result is used to realize parameter initialization when the test code is generated, including: initializing the traversal start node to For the test start interface node, the traversal start node can be any node in the middle of the process, and each complete branch path from the traversal start node to the last interface node, the interface flow chart The two interface nodes can be called in both directions; the configuration value of the test depth value is greater than or equal to the longest depth value of the flowchart starting from the configured test start interface node, where the depth configuration value is equal to the configured test start The longest depth value of the flow chart with the interface node as the starting point, if there is interaction between multiple branch paths, the page depth is set to the sum of the depth values of the two branch processes;

Combining the preset parameter types and parameter values of the input parameters of the interface node, the code engine is used to deeply traverse the interface flow chart, and the corresponding test code is generated according to each complete branch path from the traversal start node to the back, The test code includes a program to call each interface node. In the process of traversal, when an interface node is detected, the parameter type and parameter value of the input parameter of the preset interface node are obtained to call the interface node, This interface is triggered to obtain the parameter value of the output parameter, and the matching field from the output parameter is used as the input parameter of the next interface node, so as to traverse each complete branch path from the traversal starting node backward in the path Interface node on

Put the test code in the test run environment in the form of a template that meets the operating conditions, run the test code to obtain the test result, and run the test code in the following two ways:

Cloud operation mode: send a running request to the cloud, the running request includes the information of the object to be tested; the cloud server obtains the test code corresponding to the information of the object to be tested according to the operation request, and puts the test code in Project template to make it meet the operating requirements of the cloud test environment. For example, copy the test code to a folder at a specified address, call the source configuration file of the object to be tested, and use the source configuration file to The parameters in the project template are automatically filled, and the filled-in project template including the test code can be put into the cloud test software to run, and the test code is received based on the run request and the test code is run in the cloud test software. Test Results;

Local running mode: download the corresponding test code from the cloud to the local computer, and run the test code in the test software in the computer. Before running the test code, the operating user completes putting the test code into For the operation of the project template, while downloading the test code in the cloud, it also downloads the project template, source configuration file and operating instructions. The project configuration can be completed according to the operating instructions, put into the local test environment for operation, and the test results are obtained; The carrier of the interface is a mobile terminal, and the mobile terminal needs to be connected to the local computer first.

In an embodiment of the present invention, an automatic interface test device is provided. Referring to Fig. 4, the device includes the following modules:

In general, the testing process of the interface automation test module is as follows: the target module to be tested obtains the interface set information of the object to be tested, and the interface set information includes each interface node and the input parameters and output parameters corresponding to each interface node. The information that needs to be filled on the interface node is preset as input parameters, and the assertion setting is set on the interface node; an interface flow chart is established according to the interface information, and then a node is selected in the interface flow chart as Test the starting interface node and initialize its test depth value; then traverse the flowchart and automatically generate code. The essence of automatic code generation is to use the code engine to traverse to the interface node. If there is an assertion setting, then an assertion judgment will be performed, if there is no assertion setting , The input parameters of the current interface node are added to the code. After completing the input parameters, call this interface and receive the return value, and then match the value of a field in the preset return value to the input parameters required by the next interface node , And call the next interface node until the last interface node on the branch path is called (complete the corresponding assertion judgment, if the interface has an assertion setting).

It should be noted that when the interface automation test device provided in the above embodiment performs the interface automation test, only the division of the above functional modules is used as an example for illustration. In actual applications, the above functions can be allocated to different functional modules according to needs. Complete, that is, divide the internal structure of the interface automated test device into different functional modules to complete all or part of the functions described above. In addition, the embodiment of the interface automatic test device provided in this embodiment belongs to the same concept as the interface automatic test method provided in the above-mentioned embodiment. For the specific implementation process, please refer to the method embodiment, which will not be repeated here.

In an embodiment of the present invention, there is provided an interface automated test equipment, including a processor and a memory, the memory stores a program, and when the processor executes the program, the following operations are performed:

Run the test code in the test run environment to obtain the test result.

In an embodiment of the present invention, a storage medium is provided for storing a program, and the program performs the following operations when executed:

Run the test code in the test run environment to obtain the test result.

The above embodiments of the interface automatic test equipment and the corresponding storage medium belong to the same concept as the interface automatic test method provided in the above embodiments. For the specific implementation process, please refer to the method embodiment, which will not be repeated here.

The above descriptions are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection of the present invention. Within range.

Claims

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

Obtain the interface set information of the object to be tested, the interface set information includes each interface node and the interface description corresponding to each interface node, the interface node is a way for front-end and back-end interaction, and the interface description includes input parameters and output parameters ；

According to the function to be tested, arrange the related interface nodes in order, and associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flow chart, including: Get the entire website After the collection of interfaces and the corresponding interface description for each interface, the related interfaces are arranged in order according to the functional requirements, and then for every two interfaces, a field in the output of the previous interface corresponds to the next one. A certain parameter in the input of the interface until the interface process of all functions is completed; based on the situation that different interface nodes correspond to the same previous interface node, the different interface nodes are set in different branch paths; based on the first interface When the node is the previous interface node of the second interface node and the second interface node is the previous interface node of the third interface node, the first interface node, the second interface node, and the third interface node are set in the same branch In the path, the name of the interface and input/output parameters shall be based on the name in the underlying interface script;

Perform initialization parameter configuration. The initialization parameter configuration result includes a test start interface node and a test depth value. The initialization parameter configuration result is used to realize parameter initialization when the test code is generated, including: initializing the traversal start node to For the test start interface node, the traversal start node can be any node in the middle of the process, and each complete branch path from the traversal start node to the last interface node, the interface flow chart The two interface nodes can be called in both directions; the configuration value of the test depth value is greater than or equal to the longest depth value of the flowchart starting from the configured test start interface node, where the depth configuration value is equal to the configured test start The longest depth value of the flow chart with the interface node as the starting point, if there is interaction between multiple branch paths, the page depth is set to the sum of the depth values of the two branch processes;

Combining the preset parameter types and parameter values of the input parameters of the interface node, the code engine is used to deeply traverse the interface flowchart, and the corresponding test code is generated according to each complete branch path from the traversing start node to the back, The test code includes a program to call each interface node. In the process of traversal, when an interface node is detected, the parameter type and parameter value of the input parameter of the preset interface node are obtained to call the interface node, This interface is triggered to obtain the parameter value of the output parameter, and the matching field from the output parameter is used as the input parameter of the next interface node, so as to traverse each complete branch path from the traversal starting node backward in the path Interface node on

Put the test code in the test run environment in the form of a template that meets the operating conditions, run the test code to obtain the test result, and run the test code in the following two ways:

Cloud operation mode: send a running request to the cloud, the running request includes the information of the object to be tested; the cloud server obtains the test code corresponding to the information of the object to be tested according to the operation request, and puts the test code in Project template to make it meet the operating requirements of the cloud test environment. For example, copy the test code to a folder at a specified address, call the source configuration file of the object to be tested, and use the source configuration file to The parameters in the project template are automatically filled, and the filled project template including the test code can be put into the cloud test software to run, and the test code is received by running the test code in the cloud test software based on the run request Test Results;

Local running mode: download the corresponding test code from the cloud to the local computer, and run the test code in the test software in the computer. Before running the test code, the operating user completes putting the test code into For the operation of the project template, while downloading the test code in the cloud, it also downloads the project template, source configuration file and operating instructions. The project configuration can be completed according to the operating instructions, put into the local test environment for operation, and the test results are obtained; The carrier of the interface is a mobile terminal, and the mobile terminal needs to be connected to the local computer first.
An automatic interface testing method, characterized in that it comprises the following steps:

Acquiring interface set information of the object to be tested, the interface set information including each interface node and an interface description corresponding to each interface node, the interface description including input parameters and output parameters;

According to the function to be tested, arrange the relevant interface nodes in order, and associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flowchart;

Combining the preset parameter types and parameter values of the input parameters of the interface node, the interface flowchart is deeply traversed, and the corresponding test code is generated according to each complete branch path from the traversal start node to the back. The test The code includes programs to call each interface node;

Run the test code in the test run environment to obtain the test result.
The interface automation test method according to claim 2, wherein the method further comprises obtaining an assertion setting result before or after obtaining the interface flowchart, and the assertion setting result is an output parameter output after calling the corresponding interface node Set expected value;

Generating the test code includes: quoting the program of the assertion judgment operation after calling the interface node corresponding to the set expected value.
The interface automation test method according to claim 2, wherein the method further comprises obtaining an initialization parameter configuration result after obtaining the interface flowchart, the initialization parameter configuration result including a test start interface node, the initialization parameter The configuration result is used to implement parameter initialization when generating the test code, including: initializing the traversal start node as the test start interface node, and the test start interface node may be any interface in the interface flowchart node.
The interface automation test method according to claim 4, wherein the initialization parameter configuration result further includes a test depth value, and the configuration value of the test depth value is greater than or equal to the test starting interface node configured as a starting point. The longest depth value of the flowchart.
The interface automation test method according to claim 2, wherein the method further comprises obtaining an input parameter configuration result before or after obtaining the interface flowchart, and the input parameter configuration result includes the input required to implement the calling interface node The parameters;

Generating the test code includes: assigning the above-mentioned input parameter configuration result to the program of the input parameter at the corresponding calling interface node.
The interface automation test method according to claim 2, wherein the establishing step of the interface flowchart includes the following operations:

Based on the situation that different interface nodes correspond to the same previous interface node, the different interface nodes are set in different branch paths, and/or

Based on the situation that the first interface node is the previous interface node of the second interface node and the second interface node is the previous interface node of the third interface node, the first interface node, the second interface node, and the third interface node Set in the same branch path.
The interface automation test method according to claim 7, wherein part or all of the interface flow chart can be moved, copied, cut and/or pasted.
The interface automation test method according to claim 2, wherein the step of running the test code in a test operation environment includes a local operation mode and/or a cloud operation mode, and the local operation mode includes: from the cloud Download the test code to a local computer, and run the test code in the test software in the computer to obtain a test result;

The cloud operation mode includes: sending an operation request to the cloud, the operation request including the object to be tested information; according to the operation request, obtaining the corresponding test code; receiving based on the operation request to run the test software in the cloud Describe the test results obtained by the test code.
The interface automation test method according to claim 2, wherein the test report of the test result includes a test failure case description, and the test failure case includes an interface call error and/or an assertion judgment error.
The interface automation test method according to claim 2, wherein the process information and data information in each test case obtained by running the test code in the test operation environment are associated and stored separately.
An automatic interface test device, which is characterized by comprising the following modules:

The target module to be tested is used to obtain interface set information of the object to be tested, the interface set information includes each interface node and the interface description corresponding to each interface node, and the interface description includes input parameters and output parameters;

The flow chart module is used to arrange the related interface nodes in order according to the functions to be tested, and to associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flow chart;

The code generation module is used to combine preset parameter types and parameter values of the input parameters of the interface node to perform a deep traversal of the interface flowchart, and generate the corresponding branch path according to each complete branch path from the traversal start node backward Test code, the test code includes a program to call each interface node;

The running module is used to run the test code in the test running environment to obtain the test result.
An automatic interface test equipment includes a processor and a memory, the memory stores a program, and is characterized in that when the processor executes the program, the following operations are performed:

Acquiring interface set information of the object to be tested, the interface set information including each interface node and an interface description corresponding to each interface node, the interface description including input parameters and output parameters;

According to the function to be tested, arrange the relevant interface nodes in order, and associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flowchart;

Combining the preset parameter types and parameter values of the input parameters of the interface node, the interface flowchart is deeply traversed, and the corresponding test code is generated according to each complete branch path from the traversal start node to the back. The test The code includes programs to call each interface node;

Run the test code in the test run environment to obtain the test result.
A storage medium used to store a program, wherein the program performs the following operations when being executed:

Acquiring interface set information of the object to be tested, the interface set information including each interface node and an interface description corresponding to each interface node, the interface description including input parameters and output parameters;

According to the function to be tested, arrange the relevant interface nodes in order, and associate the output parameters of the previous interface node with the input parameters of the next interface node among the two adjacent interface nodes to obtain the interface flowchart;

Combining the preset parameter types and parameter values of the input parameters of the interface node, the interface flowchart is deeply traversed, and the corresponding test code is generated according to each complete branch path from the traversal start node to the back. The test The code includes programs to call each interface node;

Run the test code in the test run environment to obtain the test result.