Interface test method, device and equipment and computer readable storage medium

By disassembling and reassembling interface test messages, and combining error and correct parameters in the database, the problem of traditional interface testing being unable to assess abnormal scenarios is solved, thus achieving higher quality interface testing.

CN115562999BActive Publication Date: 2026-06-23AGRICULTURAL BANK OF CHINA

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
AGRICULTURAL BANK OF CHINA
Filing Date
2022-10-25
Publication Date
2026-06-23

AI Technical Summary

Technical Problem

Traditional API testing methods can only test the capabilities of an API under normal scenarios, and cannot effectively test the performance of an API under abnormal scenarios, resulting in poor test quality.

Method used

By disassembling the first message, multiple first fields are obtained, and the second fields of incorrect and correct parameters are matched in the database. The second message is then concatenated and sent to the target interface. The verification information fed back by the interface is received and analyzed to determine the test result.

Benefits of technology

It improves the quality of interface testing, enables the evaluation of the interface's ability to cope with abnormal scenarios, and enhances the comprehensiveness and accuracy of testing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115562999B_ABST
    Figure CN115562999B_ABST
Patent Text Reader

Abstract

The application provides an interface test method, device and equipment and a computer readable storage medium. The method comprises the following steps: disassembling a first message to obtain a plurality of first fields, and determining each second field matched with the first field in a database; determining a third field corresponding to the first field according to the first field and each matched second field; splicing each third field to obtain a second message, and sending the second message to a target interface; receiving check information of the second message fed back by the target interface, and determining a test result of the target interface according to the check information. In the application, the second message comprises a field representing a correct parameter and a field representing an error parameter, so that the interface can cope with an abnormal scene based on the error parameter, and the interface can cope with a normal scene based on the correct parameter, thereby improving the test quality of the interface test.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to interface testing technology, and more particularly to an interface testing method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] An interface is the window through which a system interacts with external devices. Interface testing can detect the data interaction, transmission, and control management processes between the system and external devices.

[0003] Traditional API testing is forward testing. Forward testing refers to sending a message containing the correct parameters to the API, and then the API verifies the parameters in the message after receiving it.

[0004] However, system errors often occur in abnormal scenarios. Forward testing can only test the ability of the interface to operate in normal scenarios, but cannot test the interface's ability to cope with abnormal scenarios, which makes the interface testing fail to achieve the expected results, that is, the test quality of the interface testing is poor. Summary of the Invention

[0005] This invention provides an interface testing method, apparatus, device, and computer-readable storage medium to solve the problem of poor test quality in interface testing.

[0006] On the one hand, the present invention provides an interface testing method, including:

[0007] The first message is decomposed to obtain multiple first fields, and each second field that matches the first field is determined in the database. Each second field that matches the first field includes the field corresponding to the error parameter and the field corresponding to the correct parameter.

[0008] The third field corresponding to the first field is determined based on the first field and each of the matched second fields;

[0009] The third fields are concatenated to obtain the second message, and the second message is sent to the target interface;

[0010] The system receives the verification information of the second message fed back by the target interface and determines the test result of the target interface based on the verification information.

[0011] In one embodiment, the step of determining each of the second fields in the database that matches the first field includes:

[0012] Determine the type of the parameter represented by the first field;

[0013] Retrieve each field corresponding to the type from the database and use it as the second field that matches the first field.

[0014] In one embodiment, before the step of retrieving the fields corresponding to the type from the database, the method further includes:

[0015] Obtain the fourth field of each input and the fifth field of each first interface;

[0016] Obtain the first metadata of the fourth field and the second metadata of the fifth field, wherein the first metadata includes the type of the fourth field and the second metadata includes the type of the fifth field;

[0017] Each of the fourth fields and its corresponding first metadata are stored in the database, and each of the fifth fields and its corresponding second metadata are also stored in the database.

[0018] In one embodiment, the step of disassembling the first message to obtain multiple first fields includes:

[0019] Identify the symbols in the first message;

[0020] Extract the fields between each of the symbols as the first field.

[0021] In one embodiment, the step of concatenating the various third fields to obtain a second message and sending the second message to the target interface includes:

[0022] By concatenating the various third fields multiple times, different second messages are obtained;

[0023] Each of the second messages is sent to the target interface.

[0024] In one embodiment, after the step of sending the second message to the target interface, the method further includes:

[0025] Receive query information sent by the target interface, wherein the query information is the query result fed back by the query system based on the second message sent by the target interface;

[0026] The query performance of the query system is determined based on the query information.

[0027] In another aspect, the present invention also provides an interface testing apparatus, comprising:

[0028] The disassembly module is used to disassemble the first message to obtain multiple first fields, and determine each second field that matches the first field in the database. Each second field that matches the first field includes the field corresponding to the error parameter and the field corresponding to the correct parameter.

[0029] The determining module is used to determine the third field corresponding to the first field based on the first field and each matched second field;

[0030] The splicing module is used to splice the various third fields to obtain a second message, and send the second message to the target interface;

[0031] The receiving module is used to receive the verification information of the second message fed back by the target interface, and determine the test result of the target interface based on the verification information.

[0032] In another aspect, the present invention also provides an interface testing device, including: a memory and a processor;

[0033] The memory stores computer-executed instructions;

[0034] The processor executes the computer execution instructions stored in the memory, causing the processor to perform the interface testing method as described above.

[0035] In another aspect, the present invention also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the interface testing method described above.

[0036] In another aspect, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the interface testing method described above.

[0037] The interface testing method, apparatus, device, and computer-readable storage medium provided by this invention decompose a first message to obtain multiple first fields, determine each second field matching the first fields in a database, and obtain a third field based on the first fields and the matching second fields. Then, the third fields are concatenated to obtain a second message, which is then sent to the target interface. Finally, the test result of the target interface is determined by the verification information of the second message returned by the target interface. In this invention, the second message includes fields representing correct parameters and fields representing incorrect parameters, thereby enabling the interface to handle abnormal scenarios based on incorrect parameters and normal scenarios based on correct parameters, thus improving the test quality of the interface. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0039] Figure 1 The system architecture diagram involved in the interface testing method provided in the embodiments of the present invention;

[0040] Figure 2 This is a flowchart illustrating the first embodiment of the interface testing method of the present invention;

[0041] Figure 3 This is a flowchart illustrating the second embodiment of the interface testing method of the present invention;

[0042] Figure 4 This is a flowchart illustrating the third embodiment of the interface testing method of the present invention;

[0043] Figure 5 This is a flowchart illustrating the fourth embodiment of the interface testing method of the present invention;

[0044] Figure 6 This is a schematic diagram of the interface testing device of the present invention;

[0045] Figure 7 This is a schematic diagram of the hardware structure of the interface testing device of the present invention.

[0046] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0047] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0048] An interface is the window through which a system interacts with external devices. Interface testing can detect the data interaction, transmission, and control management processes between the system and external devices.

[0049] The inventors of this patent discovered that traditional interface testing is forward testing. Forward testing refers to sending a message containing correct parameters to the interface, and the interface then verifies the parameters in the message after receiving it. However, system errors often occur in abnormal scenarios. Forward testing can only test the interface's ability to operate in normal scenarios, but it cannot test the interface's ability to cope with abnormal scenarios, resulting in interface testing failing to achieve the expected results, or in other words, poor test quality.

[0050] The inventors of this patent therefore conceived of setting fields representing correct parameters and fields representing incorrect parameters in the message, thereby enabling the interface to handle abnormal scenarios based on incorrect parameters and to handle normal scenarios based on correct parameters, thus improving the testing quality of the interface.

[0051] Reference Figure 1 , Figure 1 This is a system architecture diagram related to the interface testing method of the present invention. The interface testing device 100 acquires a first message, then decomposes the first message to obtain multiple first fields. The interface testing device 100 retrieves multiple second fields matching the first fields from the database 200, and obtains a third field based on the first fields and each matching second field. The interface testing device 100 then concatenates the third fields to obtain a second message. The interface testing device 100 sends the second message to the target interface 300. The target interface 300 verifies the third field in the second message to obtain verification information, and then sends the verification information back to the interface testing device 100. Furthermore, the target interface 300 also sends the second message to the query system 400. The query system 400 performs a query based on the third field in the second message and then sends the query information back to the target interface 300. The target interface 300 then sends the query information back to the interface testing device 100.

[0052] The technical solutions of the present invention and how they solve the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0053] Reference Figure 2 , Figure 2 This is a first embodiment of the interface testing method of the present invention. The interface testing method includes the following steps:

[0054] Step S201: The first message is disassembled to obtain multiple first fields, and each second field that matches the first field is determined in the database. The second fields that match the first field include the field corresponding to the error parameter and the field corresponding to the correct parameter.

[0055] In this embodiment, the execution entity is an interface testing device. For ease of description, the term "device" will be used to refer to the interface testing device below. The device can be any terminal device with testing capabilities.

[0056] The device acquires a first message, which is used for testing the interface. This first message can be pre-stored in the device or input from an external device. The first message contains multiple fields, defined as first fields, each representing a parameter. For example, the first field could represent a user's ID number, login account, or phone number. The device then decomposes the first message to obtain these multiple first fields.

[0057] The database stores multiple fields, which correspond to different interface input and output parameters. After obtaining each first field, the device determines the corresponding second fields in the database. The attributes of the second fields matching the first field are the same as those of the first field. For example, if the first field describes a user account, then the matching second fields also describe a user account. It should be noted that the matching second fields include fields corresponding to incorrect parameters and fields corresponding to correct parameters. For example, if the first field represents an ID card number (18 digits), then at least one of the second fields must contain an 18-digit ID card number (correct parameter), and at least one must contain an ID card number less than 17 digits (incorrect parameter). Furthermore, the matching second fields also include second fields with missing fields, redundant fields, and empty fields.

[0058] Step S202: Determine the third field corresponding to the first field based on the first field and each matched second field.

[0059] Step S203: Concatenate the third fields to obtain the second message, and send the second message to the target interface.

[0060] The device assigns the values ​​of each second field to the first field to obtain the third field. The device then concatenates the third fields to obtain the second message; the third fields can be concatenated in any order.

[0061] After receiving the second message, the device sends it to the target interface, which is the interface to be tested. The target interface verifies each third field in the second message to obtain verification information.

[0062] It should be noted that since the third field includes normal fields, missing fields, redundant fields, fields with correct data, fields with incorrect data, and fields with empty data, while the fields corresponding to error parameters also include fields with missing data, redundant fields, fields with correct data, fields with incorrect data, and fields with empty data, the proportion of reverse cases in the interface testing process is increased, thereby enabling the testing of the interface's ability to handle abnormal scenarios. The reverse cases are the fields corresponding to the error parameters.

[0063] Step S204: Receive the verification information of the second message fed back by the target interface, and determine the test result of the target interface based on the verification information.

[0064] The target interface verifies the second message to obtain verification information, and then sends the verification information to the device. The verification information can be a checksum. The device can determine the test interface of the target interface based on the checksum. For example, if the checksum is 0, the test result of the target interface is that the test passed; if the checksum is 1, the test result of the target interface is that the test failed.

[0065] In this embodiment, the second message includes fields representing correct parameters and fields representing incorrect parameters, thereby enabling the interface to handle abnormal scenarios based on incorrect parameters and to handle normal scenarios based on correct parameters, thus improving the testing quality of the interface.

[0066] Reference Figure 3 , Figure 3 This is a second embodiment of the interface testing method of the present invention. Based on the first embodiment, step S202 includes:

[0067] Step S301: Determine the type of the parameter represented by the first field.

[0068] In this embodiment, the database includes multiple storage partitions, each storing a field of one type. After obtaining the first field, the device determines the type of the parameter represented by the first field.

[0069] Step S302: Retrieve the fields corresponding to the type from the database and use them as the second field that matches the first field.

[0070] After determining the type corresponding to the first field, the device identifies the corresponding storage partition in the database and then retrieves each field from the storage partition as the corresponding second fields to match the first field. When retrieving fields from the storage partition, the device needs to select fields with normal data, missing data, redundant data, correct data, incorrect data, and empty data as the corresponding second fields. In other words, the device tries to select as many fields of incorrect types as possible as the corresponding second fields to match the first field.

[0071] The database is a field-based database based on a metadata model; the metadata model is the database itself. Therefore, before retrieving the fields of type pairs from the database, a metadata model needs to be created. Specifically, the device retrieves the fourth field input and the fifth field output from each first interface, and retrieves the first metadata for each fourth field and the second metadata for each fifth field. Metadata is data that describes data; for example, metadata is used to describe data attributes, and metadata is used to support functions such as indicating storage location, historical data, resource lookup, and file records. The first interface can be any interface.

[0072] The first metadata must include at least the type of the fourth field, and the second metadata must include at least the type of the fifth field. In addition, the first and second metadata also include field lengths, value specifications, etc.

[0073] The device stores each fourth field and its corresponding first metadata in the database, that is, stores each fourth field and its corresponding first metadata in the metadata model; the device then stores each fifth field and its corresponding second metadata in the database, that is, stores each fifth field and its corresponding second metadata in the metadata model. The metadata model can store instance data and also store data creation statements. Instance data refers to the fourth and fifth fields, while data creation statements are created fields, not fields output or input by the first interface.

[0074] In this embodiment, the device determines the type of the parameter represented by the first field, and then retrieves the corresponding fields from the database as the second fields, thereby quickly finding the fields that match the first field and improving the efficiency of interface testing.

[0075] Reference Figure 4 , Figure 4 In the third embodiment of the interface testing method of the present invention, based on the first or second embodiment, step S201 includes:

[0076] Step S401: Determine each symbol in the first message.

[0077] Step S402: Extract the fields between each symbol as the first field.

[0078] In this embodiment, the device is equipped with a message decomposition script. The device uses the message decomposition script to decompose the first message to obtain each first character.

[0079] Specifically, the first message includes symbols such as "", / / , and 《》, and the spaces between these symbols are fields. The message decomposition script traverses the first message, identifies each symbol within it, and then extracts the fields between the symbols as the first field.

[0080] It should be noted that when the message decomposition script decomposes the first field, it records the symbol corresponding to the first field. When concatenating the various third fields, the third field is placed among the symbols corresponding to the first field in the third field. That is, each third field has a symbol. Then, the second message is obtained by concatenating the various third fields with symbols.

[0081] In this embodiment, the device determines each symbol in the first message and then extracts the first field from each symbol to avoid extracting incomplete fields.

[0082] Reference Figure 5 , Figure 5 In the fourth embodiment of the interface testing method of the present invention, based on any one of the first to third embodiments, step S203 includes:

[0083] Step S501: Concatenate each third field multiple times to obtain different second messages.

[0084] In this embodiment, the device can combine and concatenate the various third fields to obtain different second messages. For example, the device obtains three third fields, A, B, and C. These three third fields A, B, and C can be combined and concatenated in six ways: ABC, ACB, BAC, BCA, CAB, and CBA, thus obtaining six different second messages.

[0085] Step S502: Send each second message to the target interface.

[0086] After receiving multiple second messages, the device can send each second message to the target interface. The target interface then needs to verify each second message and send the verification information corresponding to each second message back to the device. In other words, the device needs to determine the test result of the target interface based on the verification information of multiple second messages.

[0087] Existing interface testing technologies typically employ a one-to-one model, where one interface corresponds to one message, and one message corresponds to one piece of data. In this embodiment, however, one interface corresponds to multiple messages, and one message corresponds to one piece of data. Therefore, one interface corresponds to multiple pieces of data, achieving many-to-many interface testing. This allows the interface to verify multiple messages simultaneously, improving testing efficiency.

[0088] In one embodiment, after the device sends the second message to the target interface, the device receives query information sent by the target interface, and then determines the query performance of the query system based on the query information. The query information is the query result returned by the query system based on the second message sent by the target interface.

[0089] Specifically, after receiving the second message, the target interface sends it to the query system. The query system performs a query based on the third field in the second message to obtain the query results corresponding to the second message. For example, if the third field includes an ID card number, the query system will query the name and contact information of the user whose ID card number belongs; the user's name and contact information are the query results. The query system feeds back the query results as query information to the target interface, which then sends the query information to the device. The device can then determine the query performance of the query system based on the query information.

[0090] Specifically, the third field includes incorrect parameters. If the query system has a parameter validation function, it will validate the third field and output the validation result. The query result is then obtained by combining the validation result. For example, if the third field is a 17-digit ID card number, and the query system has a validation function, it can detect that the ID card number has 17 digits, which is an incorrect ID card number. The query result will be: "ID card number is incorrect, query cannot be performed." Based on this query result, the device can determine that the query system has excellent query performance and a high ability to validate incorrect parameters.

[0091] If the query system lacks validation functionality for incorrect parameters, or is unable to detect incorrect parameters, it will repeatedly query based on the third field, resulting in the query message: "Multiple queries, no name found corresponding to the ID number." Based on this query result, it can be determined that the query system has low query performance and a poor ability to validate incorrect parameters.

[0092] In this embodiment, the device can accurately determine the query performance of the query system through the query information in the second message.

[0093] The present invention also provides an interface testing device, with reference to Figure 6 The interface testing device 600 includes:

[0094] The disassembly module 610 is used to disassemble the first message to obtain multiple first fields and determine each second field that matches the first field in the database. The second fields that match the first field include the field corresponding to the error parameter and the field corresponding to the correct parameter.

[0095] The determination module 620 is used to determine the third field corresponding to the first field based on the first field and each matched second field;

[0096] The splicing module 630 is used to splice the various third fields to obtain the second message and send the second message to the target interface;

[0097] The receiving module 640 is used to receive the verification information of the second message fed back by the target interface, and determine the test result of the target interface based on the verification information.

[0098] In one embodiment, the interface testing apparatus 600 includes:

[0099] Module 620 is used to determine the type of the parameter represented by the first field;

[0100] Retrieve the fields corresponding to the type from the database and use them as the second field to match the first field.

[0101] In one embodiment, the interface testing apparatus 600 includes:

[0102] The acquisition module is used to acquire the fourth field of the input and the fifth field of the output of each first interface;

[0103] The acquisition module is used to acquire the first metadata of the fourth field and the second metadata of the fifth field. The first metadata includes the type of the fourth field, and the second metadata includes the type of the fifth field.

[0104] The storage module is used to store each fourth field and its corresponding first metadata to the database, and to store each fifth field and its corresponding second metadata to the database.

[0105] In one embodiment, the interface testing apparatus 600 includes:

[0106] The determination module 620 is used to determine each symbol in the first message;

[0107] The extraction module is used to extract the fields between each symbol as the first field.

[0108] In one embodiment, the interface testing apparatus 600 includes:

[0109] The splicing module 630 is used to splice the various third fields multiple times to obtain different second messages;

[0110] The sending module is used to send each second message to the target interface.

[0111] In one embodiment, the interface testing apparatus 600 includes:

[0112] The receiving module 640 is used to receive query information sent by the target interface, wherein the query information is the query result fed back by the query system based on the second message sent by the target interface;

[0113] The determination module 620 is used to determine the query performance of the query system based on the query information.

[0114] Figure 7This is a hardware structure diagram of an interface testing device according to an exemplary embodiment.

[0115] The interface testing device 700 may include: a processor 701, such as a CPU, a memory 702, and a transceiver 703. Those skilled in the art will understand that... Figure 7 The structure shown does not constitute a limitation on the interface test equipment and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Memory 702 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0116] The processor 701 can call the computer program stored in the memory 702 to complete all or part of the steps of the interface testing method described above.

[0117] Transceiver 703 is used to receive information sent by external devices and to send information to external devices.

[0118] A non-transitory computer-readable storage medium, wherein when the instructions in the storage medium are executed by the processor of an interface testing device, the interface testing device is able to perform the aforementioned interface testing method.

[0119] A computer program product includes a computer program that, when executed by the processor of an interface testing device, enables the interface testing device to perform the aforementioned interface testing method.

[0120] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0121] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. An interface testing method, characterized in that, include: Obtain the fourth field of each input and the fifth field of each first interface; Obtain the first metadata of the fourth field and the second metadata of the fifth field, wherein the first metadata includes the type of the fourth field and the second metadata includes the type of the fifth field; Each of the fourth fields and its corresponding first metadata is stored in the database, and each of the fifth fields and its corresponding second metadata is also stored in the database; wherein, the database is a field database based on a metadata model; The first message is decomposed to obtain multiple first fields, and the type of the parameter represented by the first field is determined; each field corresponding to the type is obtained from the database as a second field that matches the first field, wherein each second field that matches the first field includes the field corresponding to the error parameter and the field corresponding to the correct parameter; The third field corresponding to the first field is determined based on the first field and each of the matched second fields; The third fields are concatenated to obtain the second message, and the second message is sent to the target interface; The system receives the verification information of the second message fed back by the target interface and determines the test result of the target interface based on the verification information.

2. The interface testing method according to claim 1, characterized in that, The step of disassembling the first message to obtain multiple first fields includes: Identify the symbols in the first message; Extract the fields between each of the symbols as the first field.

3. The interface testing method according to claim 1, characterized in that, The step of concatenating the third fields to obtain the second message and sending the second message to the target interface includes: By concatenating the various third fields multiple times, different second messages are obtained; Each of the second messages is sent to the target interface.

4. The interface testing method according to any one of claims 1-3, characterized in that, After the step of sending the second message to the target interface, the method further includes: Receive query information sent by the target interface, wherein the query information is the query result fed back by the query system based on the second message sent by the target interface; The query performance of the query system is determined based on the query information.

5. An interface testing device, characterized in that, include: The acquisition module is used to acquire the fourth field of the input and the fifth field of the output of each first interface; The acquisition module is used to acquire the first metadata of the fourth field and the second metadata of the fifth field, wherein the first metadata includes the type of the fourth field and the second metadata includes the type of the fifth field; A storage module is used to store each of the fourth fields and the corresponding first metadata into a database, and to store each of the fifth fields and the corresponding second metadata into the database; wherein, the database is a field database based on a metadata model; The disassembly module is used to disassemble the first message to obtain multiple first fields, determine the type of the parameter represented by the first field, and retrieve each field corresponding to the type from the database as a second field that matches the first field. The second fields that match the first field include fields corresponding to erroneous parameters and fields corresponding to correct parameters. The determining module is used to determine the third field corresponding to the first field based on the first field and each matched second field; The splicing module is used to splice the various third fields to obtain a second message, and send the second message to the target interface; The receiving module is used to receive the verification information of the second message fed back by the target interface, and determine the test result of the target interface based on the verification information.

6. An interface testing device, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the interface testing method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the interface testing method as described in any one of claims 1 to 4.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the interface testing method according to any one of claims 1-4.