CN111639026A - Interface test method, device and system - Google Patents

Abstract

The invention relates to an interface testing method, device and system, which receive an interface testing instruction carrying an interface identification of an interface to be tested sent by a test user; obtain an online interface document corresponding to the interface identification according to the interface testing instruction, and use the online interface document for connection The joint debugging data of the debugging; analyze the online interface document, determine the formatted interface document, so as to ensure the unified format of the interface test document. According to the joint debugging data and formatted interface documents, use the preset interface test case generation rules to automatically generate interface test cases and assertions; use the interface test cases and assertions to test the interface to be tested to obtain the test results. Using the technical solution of the present application, an interface test case can be automatically generated to perform an interface test. Compared with the manual or semi-automatic scripting of the interface use case in the prior art, manpower and time can be saved, and the test efficiency of the interface test can be improved.

Description

Interface testing method, apparatus and system

technical field

The invention relates to the technical field of interface testing, in particular to an interface testing method, device and system.

Background technique

In today's Internet era, with the continuous development of communication technology and the widespread use of computer software in the whole industry, the quality of software is of paramount importance. As an important way to ensure software quality, software testing has received more and more attention and specialization. The interaction between the front-end service and the back-end service of the software is all communicated through API (Application Programming Interface, application programming interface), so interface testing is also particularly important in software testing.

Traditionally, there are many sources of interface test documents, and the formats are different, and when doing interface testing, the scripting of interface use cases in the test is written manually or semi-automatically, and each script writing takes a lot of manpower and time. The test efficiency of the interface test is low.

SUMMARY OF THE INVENTION

In view of this, the purpose of the present invention is to provide an interface testing method, device and system to solve the problem of low testing efficiency of interface testing in the prior art.

To achieve the above purpose, the present invention adopts the following technical solutions:

An interface testing method, including:

Receive an interface test instruction sent by the test user; the interface test instruction carries the interface identifier of the interface to be tested;

According to the interface test instruction, obtain the online interface document corresponding to the interface identifier and the joint debugging data for joint debugging using the online interface document;

Parsing the online interface document to determine the formatted interface document;

According to the joint debugging data and the formatted interface document, using preset interface test case generation rules, automatically generate interface test cases and assertions;

Using the interface test case and the assertion, the interface to be tested is tested to obtain a test result.

Further, in the above-mentioned interface testing method, the obtaining the online interface document corresponding to the interface identifier includes:

According to the interface identifier carried by the interface test instruction, obtain the uniform resource locator URL of the online interface document corresponding to the interface identifier;

According to the URL, the online interface document corresponding to the URL is accessed and obtained.

Further, in the above-mentioned interface testing method, the online interface document is an interface document generated by coding and annotation using the swagger framework component.

Further, in the above interface testing method, after the automatic generation of interface test cases and assertions, the method further includes:

According to the interface test case, record each modification of the interface test case;

According to each modification, an interface test case modification log is generated and output.

Further, in the above interface testing method, the interface test case generation rules include: equivalence class division rules and/or boundary value rules.

The present invention also provides an interface testing device, comprising:

a receiving module, configured to receive an interface test instruction sent by a test user; the interface test instruction carries the interface identifier of the interface to be tested;

an acquisition module, configured to acquire, according to the interface test instruction, an online interface document corresponding to the interface identifier and joint debugging data for joint debugging using the online interface document;

an interface document parsing module, configured to parse the online interface document and determine the formatted interface document;

A test case generation module, configured to automatically generate interface test cases and assertions by using preset interface test case generation rules according to the joint debugging data and the formatted interface document;

A test module, configured to test the interface to be tested by using the interface test case and the assertion to obtain a test result.

Further, in the above-mentioned interface testing device, the acquisition module includes: a URL acquisition unit and an access unit;

The URL obtaining unit is configured to obtain the Uniform Resource Locator URL of the online interface document corresponding to the interface identification according to the interface identification carried by the interface testing instruction;

The access unit is configured to access and obtain the online interface document corresponding to the URL according to the URL.

Further, the above-mentioned interface testing device also includes: an interface document generation module;

The interface document generation module is used for coding and annotation using the swagger framework components to generate online interface documents.

Further, the above-mentioned interface testing device also includes: a recording module and an output module;

The recording module is configured to record each modification of the interface test case according to the interface test case;

The output module is configured to generate and output the interface test case modification log according to the modification situation of each time.

The present invention also provides an interface testing system, comprising: a processor and a memory connected to the processor;

The memory is used for storing a computer program, and the computer program is at least used for the above-mentioned interface testing method;

The processor is used to invoke and execute the computer program.

An interface testing method, device and system, receiving an interface test instruction carrying an interface identifier of an interface to be tested sent by a test user; according to the interface testing instruction, acquiring an online interface document corresponding to the interface identifier and an online interface document for joint debugging. Adjust data; parse the online interface document to determine the formatted interface document, so as to ensure the uniform format of the interface test document. According to the joint debugging data and formatted interface documents, use the preset interface test case generation rules to automatically generate interface test cases and assertions; use the interface test cases and assertions to test the interface under test to obtain the test results. In this way, the interface test case can be automatically generated to perform the interface test. Compared with the manual or semi-automatic writing of the interface test case script in the prior art, manpower and time can be saved, and the test efficiency of the interface test can be improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention.

Description of drawings

In order to explain the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative efforts.

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

2 is a schematic structural diagram provided by an embodiment of an interface testing device of the present invention;

FIG. 3 is a schematic structural diagram provided by an embodiment of an interface testing system of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention will be described in detail below. Obviously, the described embodiments are only some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other implementations obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present invention.

FIG. 1 is a flowchart provided by an embodiment of an interface testing method of the present invention. As shown in FIG. 1 , the interface testing method of this embodiment may specifically include the following steps:

S101. Receive an interface test instruction sent by a test user; the interface test instruction carries an interface identifier of the interface to be tested;

When the test user is testing the data interface, the test user will send an interface test instruction to the server, and the server will receive the interface test instruction, and the interface test instruction will carry the interface identifier of the interface to be tested.

S102, according to the interface test instruction, obtain the online interface document corresponding to the interface identifier and the joint debugging data for joint debugging using the online interface document;

After receiving the interface test instruction, the server obtains the online interface document corresponding to the interface identifier from the interface document repository according to the interface identifier of the interface to be tested carried in the interface test instruction. When testing the data interface, it is necessary to use the online interface document to jointly debug the interface. Therefore, it is necessary to obtain the joint debugging data for the interface joint debugging using the online interface document, wherein the joint debugging data is the interface-related information sent by the test user. Relevant information may include request address, request header, request body, request parameter, request type, whether the item is required, value range, response header, response body, return format, return parameter type, etc.

Further, the specific steps of obtaining the online interface document corresponding to the interface identifier include:

First, according to the interface identifier carried by the interface test instruction, obtain the Uniform Resource Locator URL of the online interface document corresponding to the interface identifier;

After the interface test instruction is obtained, it is necessary to obtain the Uniform Resource Locator URL of the online interface document corresponding to the interface identifier of the interface to be tested according to the interface identifier of the interface to be tested carried in the interface test instruction.

Second, according to the URL, access and obtain the online interface document corresponding to the URL.

After obtaining the URL of the online interface document, you need to access and obtain the online interface document corresponding to the URL in the interface document repository according to the URL.

Further, the above-mentioned online interface document is an interface document generated by using swagger framework components to encode and annotate.

S103, parse the online interface document, and determine the formatted interface document;

After obtaining the online interface document, the online interface document needs to be parsed to determine the formatted interface document. Each online interface document in the interface document repository may have different formats. Therefore, during the data interface test, the obtained online interface document needs to be parsed to convert the online interface document into a unified format document, that is, formatted Interface documentation. The formatted interface document may be a file in XML format, txt format or excel format.

S104, according to the joint debugging data and the formatted interface document, using a preset interface test case generation rule to automatically generate an interface test case and an assertion;

After obtaining the joint debugging data for joint debugging using the online interface document, and parsing the formatted interface document, according to the joint debugging data corresponding to the interface to be tested and the formatted interface document, use the preset interface test case generation rules to automatically generate Interface test cases and assertions. The preset interface test case generation rules include: equivalence class division rules and/or boundary value rules, that is, when generating interface test cases, only the equivalence class division rules or the boundary value rules can be used. , and the combination of equivalence class partitioning rules and boundary value rules can also be used.

S105 , using the interface test case and the assertion to test the interface to be tested to obtain a test result.

After the interface test case and assertion are generated by the interface test case generation rule, the interface to be tested is tested by the interface test case and the assertion, and the test result is obtained, so that the test user can view the test result and debug the data interface according to the test result. Among them, the interface test case of this embodiment is provided by the swagger framework through the annotation method in development, the ability to write annotations, automatically and timely generate online interface documents and interface joint debugging, and generate standard format formatted interface documents through analysis. Interface joint debugging data automatically generates reusable interface test cases, which can improve the efficiency of interface testing.

Further, the interface testing method of this embodiment may further include the following steps after automatically generating the interface test case and assertion:

First, according to the interface test case, record each change of the interface test case;

When testing the data interface, analyze and record each modification of the interface test case according to the interface test case generated by each interface test.

Second, according to each change, generate and output the interface test case change log.

After recording each change of the interface test case, generate the interface test case change log according to each change, and output the interface test case change log, so that the test user can view the interface test case change log, and test according to the interface test case. The change log adjusts the coding and annotation of online interface documents, improves the accuracy of interface test case generation, improves the reusability of interface test cases, and thus improves test efficiency. Among them, the interface test change log can be output in the form of files, such as txt, html, and excel.

Because the code is implemented in the update mode, the interface test case is generated for the first time, and the log records are all changes. The second repeated generation will compare the previous generation version and output some of the changes. If you want to regenerate without updating records, just restart a thread group on the interface testing tool. Among them, the interface testing tools can use postman, jmeter, soupui, etc.

The interface testing method of this embodiment receives an interface test instruction that carries an interface identifier of the interface to be tested and is sent by a test user; according to the interface test instruction, obtains an online interface document corresponding to the interface identifier and joint debugging data for joint debugging using the online interface document ; Analyze the online interface document and determine the formatted interface document, so as to ensure the uniform format of the interface test document. According to the joint debugging data and formatted interface documents, use the preset interface test case generation rules to automatically generate interface test cases and assertions; use the interface test cases and assertions to test the interface under test to obtain the test results. In this way, the interface test case can be automatically generated to perform the interface test. Compared with the manual or semi-automatic writing of the interface test case script in the prior art, manpower and time can be saved, and the test efficiency of the interface test can be improved. In addition, according to the interface test case, record each modification of the interface test case; according to each modification, generate and output the interface test case modification log, which enables the test user to adjust the coding and annotation of the online interface document and improve the interface test case. The accuracy of the generated and the reusability of the interface test cases, thereby improving the test efficiency.

To be more comprehensive, corresponding to the interface testing method provided by the embodiments of the present invention, the present application also provides a middle interface testing device.

FIG. 2 is a schematic structural diagram provided by an embodiment of the interface testing apparatus of the present invention. As shown in FIG. 2 , the interface testing apparatus of this embodiment includes: a receiving module 101 , an acquiring module 102 , an interface document parsing module 103 , and a test case generation Module 104 and Test Module 105.

A receiving module 101, configured to receive an interface test instruction sent by a test user; the interface test instruction carries an interface identifier of the interface to be tested;

The obtaining module 102 is used for obtaining the online interface document corresponding to the interface identifier and the joint debugging data for joint debugging using the online interface document according to the interface test instruction;

The interface document parsing module 103 is configured to parse the online interface document and determine the formatted interface document;

The test case generation module 104 is configured to automatically generate interface test cases and assertions by using preset interface test case generation rules according to the joint debugging data and formatted interface documents;

The testing module 105 is used to test the interface to be tested by using the interface test case and assertion to obtain the test result.

Further, in the interface testing apparatus of this embodiment, the obtaining module 102 includes: a URL obtaining unit and an accessing unit.

The URL obtaining unit is configured to obtain the Uniform Resource Locator URL of the online interface document corresponding to the interface identification according to the interface identification carried by the interface testing instruction;

The access unit is used to access and obtain the online interface document corresponding to the URL according to the URL.

Further, the interface testing device of this embodiment further includes an interface document generating module;

The interface document generation module is used to encode and annotate using swagger framework components to generate online interface documents.

Further, the interface testing device of this embodiment further includes a recording module and an output module.

The recording module is used to record each change of the interface test case according to the interface test case;

The output module is used to generate and output the interface test case change log according to each change.

In the interface testing apparatus of this embodiment, the receiving module 101 receives an interface testing instruction that carries the interface identifier of the interface to be tested and sent by the test user; the acquiring module 102 acquires the online interface document corresponding to the interface identifier according to the interface testing instruction, and uses the online interface document to perform The joint debugging data of the joint debugging; the interface document parsing module 103 parses the online interface document, and determines the formatted interface document, thereby ensuring that the format of the interface test document is uniform. The test case generation module 104 uses preset interface test case generation rules to automatically generate interface test cases and assertions according to the joint debugging data and formatted interface documents; the test module 105 uses the interface test cases and assertions to test the interface to be tested, and obtains Test Results. In this way, the interface test case can be automatically generated to perform the interface test. Compared with the manual or semi-automatic writing of the interface test case script in the prior art, manpower and time can be saved, and the test efficiency of the interface test can be improved. In addition, the recording module records each modification of the interface test case according to the interface test case; the output module generates and outputs the modification log of the interface test case according to each modification, which enables the test user to adjust the coding and annotation of the online interface document. Improve the accuracy of interface test case generation and the reusability of interface test cases, thereby improving test efficiency.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

FIG. 3 is a schematic structural diagram provided by an embodiment of an interface testing system of the present invention. As shown in FIG. 3 , the interface testing system includes a processor 22 and a memory 21 connected to the processor 22 .

The memory 21 is used to store a computer program, and the computer program is at least used to execute the interface testing method described in the above embodiment;

The processor 22 is used to call and execute the computer program stored in the memory 21, that is, the processor 22 is used to call and execute the interface testing method described in the above embodiments.

In the interface test system of this embodiment, the processor 22 invokes and executes the interface test method stored in the memory 21, and can automatically generate interface test cases, thereby performing interface tests. Compared with the manual or semi-automatic writing of interface test scripts in the prior art In other words, it can save manpower and time and improve the test efficiency of interface testing. In addition, each modification of the interface test case can be recorded according to the interface test case; according to each modification, the interface test case modification log can be generated and output, which enables the test user to adjust the coding and annotation of the online interface document and improve the interface The accuracy of test case generation, thereby improving test efficiency.

It can be understood that, the same or similar parts in the above embodiments may refer to each other, and the content not described in detail in some embodiments may refer to the same or similar content in other embodiments.

It should be noted that, in the description of the present invention, the terms "first", "second", etc. are only used for the purpose of description, and should not be construed as indicating or implying relative importance. Furthermore, in the description of the present invention, unless otherwise specified, the meaning of "plurality" means at least two.

Any description of a process or method in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing a specified logical function or step of the process , and the scope of the preferred embodiments of the invention includes alternative implementations in which the functions may be performed out of the order shown or discussed, including performing the functions substantially concurrently or in the reverse order depending upon the functions involved, which should It is understood by those skilled in the art to which the embodiments of the present invention belong.

It should be understood that various parts of the present invention may be implemented in hardware, software, firmware or a combination thereof. In the above-described embodiments, various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or a combination of the following techniques known in the art: Discrete logic circuits, application specific integrated circuits with suitable combinational logic gates, Programmable Gate Arrays (PGA), Field Programmable Gate Arrays (FPGA), etc.

Those skilled in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, and the program can be executed when the program is executed. , including one or a combination of the steps of the method embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, and the like.

In the description of this specification, description with reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc., mean specific features described in connection with the embodiment or example , structure, material or feature is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although the embodiments of the present invention have been shown and described above, it should be understood that the above-mentioned embodiments are exemplary and should not be construed as limiting the present invention. Embodiments are subject to variations, modifications, substitutions and variations.

Claims (10)

1. An interface testing method, comprising:

receiving an interface test instruction sent by a test user; the interface test instruction carries an interface identifier of an interface to be tested;

acquiring an online interface document corresponding to the interface identifier and joint debugging data for joint debugging by using the online interface document according to the interface test instruction;

analyzing the online interface document to determine a formatted interface document;

automatically generating an interface test case and assertion according to the joint debugging data and the formatted interface document by using a preset interface test case generation rule;

and testing the interface to be tested by using the interface test case and the assertion to obtain a test result.

2. The interface testing method according to claim 1, wherein the obtaining of the online interface document corresponding to the interface identifier includes:

acquiring a Uniform Resource Locator (URL) of the online interface document corresponding to the interface identifier according to the interface identifier carried by the interface test instruction;

and accessing and obtaining the online interface document corresponding to the URL according to the URL.

3. The interface testing method of claim 2, wherein the online interface document is an interface document generated by encoding and annotating with swagger framework components.

4. The interface testing method according to claim 1, wherein after automatically generating the interface test case and the assertion, the method further comprises:

recording each change condition of the interface test case according to the interface test case;

and generating and outputting an interface test case change log according to the change condition of each time.

5. The interface test method according to claim 1, wherein the interface test case generation rule includes: equivalence class partitioning rules and/or boundary value rules.

6. An interface testing apparatus, comprising:

the receiving module is used for receiving an interface test instruction sent by a test user; the interface test instruction carries an interface identifier of an interface to be tested;

the acquisition module is used for acquiring an online interface document corresponding to the interface identifier and joint debugging data for joint debugging by using the online interface document according to the interface test instruction;

the interface document analysis module is used for analyzing the online interface document and determining a formatted interface document;

the test case generation module is used for automatically generating an interface test case and assertion according to the joint debugging data and the formatted interface document by using a preset interface test case generation rule;

and the test module is used for testing the interface to be tested by using the interface test case and the assertion to obtain a test result.

7. The interface test apparatus of claim 6, wherein the obtaining module comprises: a URL acquisition unit and an access unit;

the URL obtaining unit is used for obtaining a Uniform Resource Locator (URL) of the online interface document corresponding to the interface identifier according to the interface identifier carried by the interface test instruction;

and the access unit is used for accessing and obtaining the online interface document corresponding to the URL according to the URL.

8. The interface test apparatus of claim 7, further comprising: an interface document generation module;

and the interface document generation module is used for coding and annotating by using the swagger framework component to generate an online interface document.

9. The interface test apparatus of claim 6, further comprising: a recording module and an output module;

the recording module is used for recording each change condition of the interface test case according to the interface test case;

and the output module is used for generating and outputting an interface test case change log according to the change condition of each time.

10. An interface test system, comprising: the system comprises a processor and a memory connected with the processor;

the memory for storing a computer program for performing at least the interface testing method of any of claims 1-5;

the processor is used for calling and executing the computer program.

Images