CN112052182A

CN112052182A - Interface automation test method and device, computer equipment and storage medium

Info

Publication number: CN112052182A
Application number: CN202011033216.XA
Authority: CN
Inventors: 邱晓帆
Original assignee: Ping An Trust Co Ltd
Current assignee: Ping An Trust Co Ltd
Priority date: 2020-09-27
Filing date: 2020-09-27
Publication date: 2020-12-08

Abstract

The invention discloses an interface automatic testing method, an interface automatic testing device, computer equipment and a storage medium. The method comprises the following steps: acquiring an interface test request, wherein the interface test request comprises an interface identifier to be executed; acquiring an original case code according to the interface identifier to be executed, and extracting interface parameter information corresponding to an interface parameter field in the original case code; if the interface parameter information contains a variable reference identifier, acquiring a parameter interface variable; inquiring interface parameter output information in an interface test information table based on the parameter input interface variable to obtain a parameter input path; acquiring a parameter value to be entered based on the parameter path to be entered; and taking the value of the parameter to be entered as an input parameter of the parameter entry field of the interface, forming an effective case code corresponding to the test case to be executed, executing the effective case code, and acquiring an interface test result. The method quantificationally records the interface parameter information, is convenient for operating and maintaining data dependence, and ensures the flexibility of carrying out the interface automatic test under the condition of data dependence.

Description

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

Technical Field

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

Background

The interface automatic test is a means for automatically testing an interface test scene provided by a system to ensure the interface logic function to be correct and improve the regression test coverage rate. In the existing interface automatic test process, the condition of carrying out quantization processing on the data dependency relationship is not considered, for example, the interface a depends on the value book (a1) of the return message of the interface B to test (B1), the interface B return message test (B1) needs to be manually assigned to the original case code of the interface a in the prior art, the return message of the interface B dynamically changes, and the input parameters of the interface a need to be manually configured every time the interface a is undertested, so that the interface automatic test process for storing the data dependency relationship lacks flexibility, and the operation and maintenance process is complex and has low efficiency.

Disclosure of Invention

The embodiment of the invention provides an interface automatic testing method, an interface automatic testing device, computer equipment and a storage medium, and aims to solve the problems of lack of flexibility, complex operation and maintenance process and low efficiency in manual adjustment of input parameters of an interface with a data dependency relationship.

An interface automation test method comprises the following steps:

acquiring an interface test request, wherein the interface test request comprises an interface identifier to be executed;

acquiring an original case code corresponding to the test case to be executed according to the interface identifier to be executed, and extracting interface parameter information corresponding to an interface parameter field in the original case code;

if the interface parameter information contains a variable reference identifier, acquiring a parameter interface variable corresponding to the variable reference identifier;

inquiring interface parameter output information in the interface test information table based on the parameter input interface variable to obtain a parameter input parameter path corresponding to the parameter input interface variable;

acquiring a parameter value to be entered corresponding to the parameter entry interface variable based on the parameter entry path corresponding to the parameter entry interface variable;

and taking the value of the parameter to be entered as an input parameter of the parameter entry field of the interface to form an effective case code corresponding to the test case to be executed, executing the effective case code and acquiring an interface test result.

An interface automated testing apparatus, comprising:

the interface test request acquisition module is used for acquiring an interface test request, and the interface test request comprises an interface identifier to be executed;

an interface parameter information obtaining module, configured to obtain an original case code corresponding to the test case to be executed according to the identifier of the interface to be executed, and extract interface parameter information corresponding to an interface parameter field in the original case code;

the parameter access interface variable acquisition module is used for acquiring parameter access interface variables corresponding to the parameter reference identifiers if the interface parameter access information contains the parameter reference identifiers;

a parameter input path acquiring module, configured to query interface parameter output information in the interface test information table based on the parameter input interface variable, and acquire a parameter input path corresponding to the parameter input interface variable;

the parameter entry interface variable acquiring module is used for acquiring a parameter entry interface variable corresponding to the parameter entry interface variable;

and the interface test result acquisition module is used for taking the value of the parameter to be input as an input parameter of the interface parameter input field, forming an effective case code corresponding to the test case to be executed, executing the effective case code and acquiring an interface test result.

A computer device comprising a memory, a processor and a computer program stored in said memory and executable on said processor, said processor implementing the steps of the above-mentioned interface automation test method when executing said computer program.

A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method for automated testing of an interface.

The interface automatic test method, the device, the computer equipment and the storage medium identify the original case code of the test case to be executed to determine the interface input parameter information, when the interface input parameter information contains the variable reference identifier, the data dependency of the test case to be executed is shown, namely the data dependency of other output parameters of the in-library interface which is executed in advance is needed, at the moment, the interface test information table can be inquired according to the input parameter interface variable corresponding to the variable reference identifier, the input parameter path corresponding to the input interface variable is determined from the interface output parameter information corresponding to the interface test information table, the value of the input parameter to be input is determined according to the input parameter path and is assigned to the original case code to form an effective case code which does not lack necessary input parameters, and the effective case code is executed to obtain the interface test result. It can be understood that, based on the interface parameter output information in the interface test information table, the output parameters and the parameter output paths thereof corresponding to each in-library interface are quantitatively recorded, which is convenient for operation and maintenance of data dependence, so that when there is data dependence in the execution process of the test case to be executed, the value of the parameter to be entered on which the parameter depends can be quickly determined and assigned to the original case code to form an effective case code, thereby ensuring the flexibility of automatic test of the interface under the condition of data dependence, and avoiding the problems of operation and maintenance difficulty, unstable execution, high cost and the like when manually configuring or writing the value of the parameter to be entered on which there is data dependence.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.

FIG. 1 is a schematic diagram of an application environment of an automated interface testing method according to an embodiment of the present invention;

FIG. 2 is a flow chart of a method for automated testing of an interface according to an embodiment of the invention;

FIG. 3 is another flow chart of a method for automated testing of an interface according to an embodiment of the invention;

FIG. 4 is another flow chart of a method for automated testing of an interface according to an embodiment of the present invention;

FIG. 5 is another flow chart of a method for automated testing of an interface according to an embodiment of the present invention;

FIG. 6 is another flow chart of a method for automated testing of an interface according to an embodiment of the present invention;

FIG. 7 is another flow chart of a method for automated testing of an interface according to an embodiment of the present invention;

FIG. 8 is another flow chart of a method for automated testing of an interface according to an embodiment of the present invention;

FIG. 9 is a schematic diagram illustrating depth traversal in the automated interface testing method according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of an automated interface test equipment according to an embodiment of the present invention;

FIG. 11 is a diagram of a computing device in accordance with an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The interface automatic testing method provided by the embodiment of the invention can be applied to the application environment shown in fig. 1. Specifically, the interface automatic test method is applied to an interface automatic test system, which comprises a client and a server as shown in fig. 1, wherein the client and the server communicate through a network and are used for recording all interface parameter output information of interfaces in a library by adopting a quantization means, so that when the interfaces with data dependency relationship are automatically tested, the dependent input parameters can be dynamically determined according to the interface parameter output information recorded in an interface test information table in advance, the test efficiency and flexibility of the interface automatic test with the data dependency relationship are improved, and the operation and maintenance are convenient. The client is also called a user side, and refers to a program corresponding to the server and providing local services for the client. The client may be installed on, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server may be implemented as a stand-alone server or as a server cluster consisting of a plurality of servers.

In an embodiment, as shown in fig. 2, an interface automation testing method is provided, which is described by taking the server in fig. 1 as an example, and includes the following steps:

s201: and acquiring an interface test request, wherein the interface test request comprises an interface identifier to be executed.

The interface test request is a request for triggering the interface automation test. The identifier of the interface to be executed is used for uniquely identifying the interface to be executed which needs to be subjected to the interface automation test.

As an example, when a certain to-be-executed interface needs to be tested to ensure the normal function of the interface logic, an interface test request may be triggered based on the to-be-executed interface identifier corresponding to the to-be-executed interface, so as to obtain a target test case corresponding to the to-be-executed interface identifier for performing an automated test. The target test case is used for carrying out interface automatic test on the interface to be executed and comprises case codes for realizing the interface logic function corresponding to the interface to be executed.

S202: and acquiring an original case code corresponding to the test case to be executed according to the interface identifier to be executed, and extracting interface parameter information corresponding to the interface parameter field in the original case code.

The original case code is a pre-configured code for implementing interface test on the interface logic function, and it cannot be ensured whether there is a code with uncertain variable values, and if it is executed directly, an interface test error may be caused by lack of necessary input parameters. The interface entry fields are the fields in the original case code that correspond to the input parameters. The interface parameter information corresponding to the interface parameter field is the information recorded in the original case code corresponding to the interface parameter field.

As an example, the server queries the system database according to the interface identifier to be executed, obtains an original case code of the test case to be executed corresponding to the interface identifier to be executed, determines all interface parameter fields from the original case code by using a character string recognition algorithm or other recognition algorithms, and obtains interface parameter information corresponding to all the interface parameter fields. For example, a character string recognition algorithm or other recognition algorithms can be adopted to recognize the assignment code corresponding to the assignment character from the original case code, determine the information on the left side of the assignment code as the interface parameter-entering field, and determine the information on the right side of the assignment code as the interface parameter-entering information, so as to realize fast search and determine the interface parameter-entering information corresponding to all the interface parameter-entering fields.

S203: and if the interface reference information contains the variable reference identifier, acquiring the reference interface variable corresponding to the variable reference identifier.

The variable reference identifier is a preconfigured identifier used for reflecting the output parameters of other interface tests needing to be referenced in the execution process of the original case code. The input interface variable corresponding to the variable reference identifier is an interface variable which needs to reference output parameters of other interface tests as input parameters.

As an example, after acquiring all interface entry parameters, the server firstly identifies whether the interface entry parameters contain variable reference identifiers by using a character string identification algorithm or other identification algorithms to determine whether the interface entry parameters corresponding to the interface entry parameters need to reference output parameters of other interface tests; when the interface parameter-entering information contains the variable reference identifier, the parameter-entering interface variable corresponding to the variable reference identifier needs to be acquired, that is, the interface variable corresponding to the output parameter of the other interface test needs to be referred. For example, if the parameter entering information of a certain interface is $ { msg }, and the preconfigured variable reference identifier is $ { }, the parameter entering interface variable corresponding to the variable reference identifier $ { } is msg, that is, the parameter entering interface variable msg is not only a variable of an input parameter of an original case code of the current interface test, but also a variable of an output parameter of other interface tests.

S204: and inquiring interface parameter output information in the interface test information table based on the parameter input interface variable to obtain a parameter input path corresponding to the parameter input interface variable.

The interface test information table is a data table used for quantitatively recording interface configuration information corresponding to all in-library interfaces. The on-library interface is an interface which is pre-stored in a system database and can carry out automatic interface test.

Generally, after an interface test case corresponding to any library-in interface is stored in a system database, interface configuration information corresponding to the library-in interface needs to be stored in an interface test information table, so that quantitative management of all interface dependency relationships between the library-in interfaces is realized by using the interface test information table. The interface test case is used for carrying out automated test on the library-in interface and comprises case codes for realizing interface logic functions corresponding to the library-in interface. The interface dependency relationship is used for reflecting the relationship of the mutual dependency between different library interfaces, for example, in the three interfaces a → B → C, the interface B operates first depending on the interface a, and the interface C operates first depending on the interface B, then the interface a is the preorder interface of the interface B, the interface C is the postorder interface of the interface B, and the interface dependency relationship between each library interface and the preorder interface thereof can be configured and maintained in the interface test information table, so that the quantitative maintenance of all the interface dependency relationships between the library interfaces is realized, the maintenance operation is convenient, and the cost is low. The preorder interface of the library interface is an interface which needs to operate before the library interface; a subsequent interface to a library interface refers to an interface that needs to run after the library interface.

The interface configuration information is interface-related configuration information and comprises interface parameter output information corresponding to a library interface, the interface parameter output information is information used for being recorded on an interface variable field of an interface test information table, the interface parameter output information comprises parameter output interface variables and corresponding parameter output paths, the parameter output paths are storage paths of parameter output values corresponding to the parameter output interface variables in a system memory, the parameter output values dynamically change, and the parameter output values can be dynamically acquired according to the parameter output paths.

Furthermore, the interface configuration information further includes interface detail information and interface dependency information, the interface detail information includes, but is not limited to, information related to the interface, such as a configuration interface identifier, a configuration interface name, and a configuration URL. The interface dependency information refers to other information of the library interface which needs to be depended on when the library interface runs, that is, the interface dependency information includes information for reflecting all the preorder interfaces and the interface dependency relationship thereof.

It can be understood that the interface test information table is adopted to record all interface configuration information corresponding to the interfaces in the library in a quantized manner, so that the interface dependency relationship can be maintained conveniently, and the maintenance and execution of the interface automatic test supporting the complex interface dependency relationship or large data volume can be realized.

As an example, after acquiring the entry interface variable, the server firstly processes the entry interface variable by using the query statement generation template to form a target query statement. The query statement generation template is a pre-configured template for automatically generating a query statement based on the reference interface variables. The target query statement is a statement which can realize a query function and is formed by processing the input parameter interface variable by adopting a query statement generation template. Executing a target query statement to query all interface parameter output information corresponding to the interface variable field in the interface test information table, and determining the interface parameter output information corresponding to the parameter output interface variable which is the same as the parameter input interface variable as the target parameter output information; and determining a parameter output path in the target parameter output information as a parameter input path corresponding to the parameter input interface variable, wherein the parameter input path is a path for acquiring an input parameter corresponding to the parameter input interface variable, and the parameter input path can adopt a json format and is convenient to call.

For example, if the interface parameter information corresponding to the interface variable field in the interface configuration information corresponding to library interface a is msg ═ results [0]. rettmsg, and the interface parameter information corresponding to the interface variable field in the interface configuration information corresponding to library interface B is mss ═ results [1]. rettms; if the parameter input interface variable of the interface to be executed is msg, after an interface test information table is queried based on a target query statement formed by the parameter input interface variable msg, determining msg as result [0]. retmsg as target parameter output information; in the target parameter output information, an assignment symbol is that information on the left is an input parameter interface variable msg of an original case code of the current interface test and is also a variable of an output parameter of other interface tests, and information on the right is an input parameter path result [0]. rettmsg corresponding to the input parameter interface variable, so that the purpose of quickly determining the input parameter path is achieved.

S205: and acquiring a to-be-parameter variable value corresponding to the parameter input interface variable based on the parameter input parameter path corresponding to the parameter input interface variable.

As an example, the server may query the system memory based on the parameter input path corresponding to the parameter input interface variable, extract data returned by the parameter input path from the system memory, and determine the parameter to be input variable value corresponding to the parameter input interface variable, so as to quickly determine the parameter to be input variable value corresponding to the parameter input interface variable in the original case code.

For example, if the interface parameter output information corresponding to the interface variable field in the interface configuration information corresponding to the library interface a is msg ═ results [0]. retmsg, it is described that when the interface test case corresponding to the library interface a is executed in advance, the output parameter corresponding to the parameter output in the library interface a is already stored in the system memory, the parameter output path of the output parameter in the system memory is obtained, and the interface parameter output information corresponding to the library interface a is formed based on the parameter output and the parameter output path. In the process of running the original case code corresponding to the test case to be executed, when the parameter of the parameter access interface is determined to be msg, a parameter access path result [0]. rettmsg can be determined according to msg ═ results [0]. rettmsg, and a system memory is queried based on the parameter access path result [0]. rettmsg, so that the parameter value to be accessed corresponding to the parameter access interface variable is obtained. For example, when the parameter entry path is a json format path, the value of the parameter to be entered corresponding to the parameter entry interface variable may be determined from the values returned by the parameter entry path.

S206: and taking the value of the parameter to be entered as an input parameter of the parameter entry field of the interface, forming an effective case code corresponding to the test case to be executed, executing the effective case code, and acquiring an interface test result.

As an example, after acquiring a parameter value to be entered corresponding to a parameter entry interface variable, a server takes the parameter value to be entered as an input parameter of the parameter entry interface variable corresponding to an interface parameter entry field, assigns the parameter entry interface variable, and determines an original case code after assignment as an effective case code; then, the effective case code is executed to obtain the interface test result, so that the condition that the original case code lacks necessary input parameters to cause interface test errors can be avoided, and the reliability of each test case test to be executed is favorably ensured.

In the interface automated testing method provided by this embodiment, an original case code of a test case to be executed is identified to determine interface entry parameter information, and when the interface entry parameter information includes a variable reference identifier, it is described that the test case to be executed has data dependency, that is, needs to depend on other output parameters of an in-library interface executed in advance, at this time, an interface test information table may be queried according to an entry interface variable corresponding to the variable reference identifier, an entry parameter path corresponding to an entry interface variable is determined from interface exit parameter information corresponding to the interface test information table, an entry parameter variable value is determined according to the entry parameter path, and is assigned to the original case code, so as to form an effective case code that does not lack necessary input parameters, and the effective case code is executed to obtain an interface test result. It can be understood that, based on the interface parameter output information in the interface test information table, the output parameters and the parameter output paths thereof corresponding to each in-library interface are quantitatively recorded, which is convenient for operation and maintenance of data dependence, so that when there is data dependence in the execution process of the test case to be executed, the value of the parameter to be entered on which the parameter depends can be quickly determined and assigned to the original case code to form an effective case code, thereby ensuring the flexibility of automatic test of the interface under the condition of data dependence, and avoiding the problems of operation and maintenance difficulty, unstable execution, high cost and the like when manually configuring or writing the value of the parameter to be entered on which there is data dependence.

In an embodiment, as shown in fig. 3, step S205, namely, obtaining a value of a parameter to be entered corresponding to an entry interface variable based on an entry parameter path corresponding to the entry interface variable, specifically includes:

s301: and inquiring a system memory based on a parameter input path corresponding to the parameter input interface variable, and judging whether the system memory stores a historical variable value corresponding to the parameter input interface variable.

The historical variable value is a numerical value corresponding to the parameter output interface variable, which is executed and output by the interface test case corresponding to the library interface before the current time of the system. Generally speaking, if an interface test case corresponding to a library interface is executed before the current time of the system, the output parameter of the parameter output interface variable is stored in the system memory as the historical variable value, the parameter output path is determined according to the storage address of the historical variable value in the system memory, and the parameter output interface variable and the parameter output path are used as interface parameter output information formed in the execution process of the interface test case corresponding to the library interface.

As an example, after the server obtains the parameter input path corresponding to the parameter input interface variable, since the parameter input path corresponding to the parameter input interface variable is a parameter output path in the interface parameter output information corresponding to the library interface before the current time of the system, it is required to query whether a history variable value corresponding to the parameter input interface variable is stored in the memory of the system based on the parameter input path to determine whether the interface test case corresponding to the library interface is executed before the current time of the system.

And S302, if the historical variable value corresponding to the parameter input interface variable is stored, determining the historical variable value corresponding to the parameter input interface variable as the parameter value to be input corresponding to the parameter input interface variable.

As an example, the server stores historical variable values corresponding to the input interface variables in the system memory, identifies the interface test case corresponding to the library interface executed before the current time of the system, the historical variable value is the output parameter output by the interface test case corresponding to the interface of the library which is executed last time, at this time, the historical variable value can be directly determined as the value of the parameter to be input corresponding to the input parameter interface variable, the method and the device realize dynamic output of the value of the parameter to be input according to the test operation result of the interface test case corresponding to the interface in the library, are beneficial to ensuring that the test case to be executed can dynamically acquire the input parameters of the interface parameter field with data dependence, improve the automatic test efficiency and the flexibility of the interface, and avoid the problems of low efficiency, complex operation and maintenance and easy error caused by manual configuration of the input parameters.

S303: if the historical variable value corresponding to the parameter input interface variable is not stored, the interface test information table is deeply traversed based on the target dependency information corresponding to the parameter input interface variable, at least two dependency test cases and an interface execution sequence are determined, at least two test cases to be executed are sequentially executed according to the interface execution sequence, and the parameter value to be input corresponding to the parameter input interface variable is obtained.

As an example, the server does not store the historical variable value corresponding to the input interface variable in the system memory, and determines that the interface test case corresponding to the library interface has not been executed before the current time of the system, at this time, the interface output parameter corresponding to the output interface variable that is the same as the input interface variable is the target output parameter, the library interface corresponding to the target output parameter is determined as the target interface, and the interface dependency information in the interface configuration information corresponding to the target interface is determined as the target dependency information. The target dependency information is used to record all the corresponding preorder interfaces of the target interface and the interface dependency relationship thereof. The target dependency information corresponding to the target interface can be quickly and effectively determined through the interface test information table, the execution sequence of the interface does not need to be manually adjusted, the operation and maintenance efficiency is improved, the automatic interface test efficiency is improved, and test operation errors caused by omission are avoided.

The dependent execution case is an interface test case corresponding to the dependent interface, the dependent interface is a data-dependent interface corresponding to the interface to be executed of the automatic test of the current interface, and the data dependence here can be understood as that the output parameter of the dependent interface is the input parameter of the interface to be executed. The interface execution sequence is the sequence in the execution process of all the dependent execution cases.

As an example, after determining the target dependency information, the server needs to deeply traverse the interface test information table based on the target dependency information, that is, all interface dependency relationships quantized and recorded in the deep traversal interface test information table, determine a target interface on which an interface to be executed directly depends, determine all preamble interfaces on which the target interface depends, determine the target interface and all the preamble interfaces as dependent interfaces, determine an interface execution sequence based on the interface dependency relationships between all the dependent interfaces, and determine an interface test case corresponding to the dependent interface as a dependent execution case. Since the dependent interface includes the target interface and the preceding interfaces on which the target interface depends, the dependent execution cases include the target test case and the preceding test cases on which the target test case depends. The target test case is an interface test case corresponding to the target interface, and the preorder test case is an interface test case corresponding to a preorder interface on which the target interface depends. It is understood that the target interface is the last dependent interface of all the dependent interfaces corresponding to the execution order of the interfaces.

The method has the advantages that the traversal search efficiency is improved by traversing the interface test information table in the target dependent information depth corresponding to the target interface identification, all dependent execution cases and the interface execution sequence can be determined quickly and effectively, the interface execution sequence does not need to be adjusted manually, the automatic interface test efficiency is improved, and test operation errors caused by omission or errors of the manual interface execution sequence adjustment are avoided.

As an example, after determining at least two dependent execution cases and the interface execution sequence corresponding to the dependent execution cases, the server sequentially executes the at least two dependent execution cases to complete the interface automation test according to the interface execution sequence, and since the target interface is the last dependent interface in all the dependent interfaces corresponding to the interface execution sequence, the output parameter of the parameter output interface variable in the target test case corresponding to the target interface may be determined as the parameter value to be input corresponding to the parameter input interface variable. It can be understood that the output parameter of the parameter output interface variable can also be stored in the system memory according to a preset parameter output path, so that the output parameter can be dynamically acquired as the parameter value to be entered corresponding to the parameter entry interface variable in the interface automated testing process based on the interface to be executed, and the acquisition efficiency and flexibility of the parameter value to be entered are ensured.

In the interface automated testing method provided by this embodiment, based on the parameter of the input interface, the corresponding target dependency information is determined from the interface testing information table, so that the efficiency of obtaining the target dependency information corresponding to the target interface is improved, and the efficiency of testing the interface automated testing is improved; according to the target dependent information depth traversal interface test information table, the traversal search efficiency is improved, at least two dependent execution cases and corresponding interface execution sequences can be determined quickly and effectively, manual adjustment of the interface execution sequences is not needed, the automatic interface test efficiency is improved, and test operation errors caused by omission or errors of the manual adjustment of the interface execution sequences are avoided; and finally, sequentially executing at least two dependent execution cases and the to-be-entered parameter value corresponding to the to-be-entered interface variable according to the interface execution sequence determined by the depth traversal interface test information table, so that the acquisition efficiency and flexibility of the to-be-entered parameter value are ensured, the automation of the interface test is ensured, and the automatic interface test efficiency is improved.

In an embodiment, as shown in fig. 4, in step S303, the deeply traversing the interface test information table based on the target dependency information corresponding to the entry-join interface variable, and determining at least two dependency test cases and an interface execution order, include:

s401: and identifying the target dependency information corresponding to the access interface variable, and determining whether the target dependency information contains a legal delimiter.

The legal separator is a character which is configured in advance and used for separating two adjacent dependent interface identifications.

As an example, the server invokes a string recognition algorithm, recognizes the target dependency information based on a preconfigured legal delimiter, to determine whether the target dependency information corresponding to the input interface variable includes the legal delimiter, and to perform subsequent steps according to the recognition result. The character string recognition algorithm is an algorithm for recognizing a specific character string in text.

S402: if the target dependency information comprises legal separators, determining at least two dependency interface identifications and a peer dependency sequence from the target dependency information; acquiring a preorder test case and a depth dependence sequence corresponding to each dependence interface identification based on at least two dependence interface identification depth traversal interface test information tables; determining at least two dependent execution cases based on a target test case corresponding to the target interface identification and all the preorder test cases; and determining an interface execution order based on the depth dependency order and the peer dependency order corresponding to the at least two dependent interface identifications.

The dependency interface identifier is an identifier corresponding to a preamble interface used for uniquely identifying the direct dependency of the target interface in the target dependency information record. Generally, if the target dependency information includes a legal delimiter, the dependent interface identifier may be determined based on the content of the character string delimited by the legal delimiter, and the dependent interface identifier is an identifier corresponding to a preamble interface on which the target interface directly depends.

Wherein, the dependency sequence of the same level is the sequence between the corresponding preamble interfaces of at least two dependency interface identifications. Generally, at least two dependent interface identifications are isolated by legal separators, and when a character string recognition algorithm is used for recognizing target dependent information, the corresponding peer dependency sequence of the at least two dependent interface identifications can be determined according to the sequence from left to right.

The depth dependence order is the sequence of all the preamble test cases corresponding to each dependence interface identification determined based on each dependence interface identification depth traversal interface test information table. Generally, when the interface test information table is deeply traversed based on each dependency interface identifier, the depth dependency order is determined from the back to the front according to the sequence of all configuration interface identifiers traversed by the depth.

For example, if the target interface identifier is T15, the information corresponding to the dependency relationship field of the target interface identifier T15 in the interface test information table is "T10; t9; t11 ", wherein"; "is a legal separator, the following detailed description of step S302 with reference to fig. 9 specifically includes the following steps:

(1) at the target dependency information "T10; t9; t11 "includes legal delimiters"; "from the target dependency information" T10; t9; in T11 ", the dependency interfaces are identified as T10, T9 and T11, and their corresponding sibling dependency orders are determined as T10 → T9 → T11.

(2) And respectively traversing the interface test information table in depth based on three dependent interface identifiers T10/T9/T11 to obtain a preamble test case and a depth dependent sequence corresponding to each dependent interface identifier. As shown in fig. 9, the interface dependency information of the dependent interface identification T10 is "T7; t5 ", the interface dependency information of the configuration interface identifier T7 is" T1 ", the interface dependency information corresponding to the configuration interface identifier T5 is" T2 ", the interface dependency information corresponding to the configuration interface identifier T2 is" T1 ", the preamble test case corresponding to the dependency interface identifier T10 includes the interface test cases corresponding to the configuration interface identifiers T10, T7, T1, T5, and T2, and the depth dependency order corresponding to the dependency interface identifier T10 is determined from the back to the front as T1 → T7 → T2 → T5 → T10 according to the precedence order of all configuration interface identifiers traversed by the depth. If the interface dependency information of the dependent interface identifier T9 and the dependent interface identifier T11 is null, the interface test cases corresponding to the dependent interface identifier T9 and the dependent interface identifier T11 are directly determined as the preamble test cases, and the depth dependency order thereof is itself.

Then, determining target test cases corresponding to the target interface identification T15 and preamble test cases corresponding to all preamble interface identifications T10/T9/T11/T7/T5/T1/T2 as dependent execution cases; the depth-dependent sequences corresponding to the three dependent interface identifications T10/T9/T11 are respectively 'T1 → T7 → T2 → T5 → T10', 'T9' and 'T11', all the depth-dependent sequences are connected depending on the dependency sequence of the same level, the target test case is determined to be the last dependent execution case, the interface execution sequence is determined to be T1 → T7 → T2 → T5 → T10 → T9 → T11 → T15, the depth traversal search mode is adopted, all the dependent execution cases and the interface execution sequence are determined quickly and effectively, the interface execution sequence does not need to be adjusted manually, the efficiency of interface automatic testing is improved, and test operation errors caused by missing or errors of the manually adjusted interface execution sequence in the interface automatic testing process are avoided.

S403: if the target dependency information does not contain a legal separator, determining a dependency interface identifier from the target dependency information, traversing an interface test information table based on the dependency interface identifier depth, acquiring a pre-order test case and a depth dependency order corresponding to the dependency interface identifier, and determining at least two dependency execution cases based on the target test case and all pre-order test cases corresponding to the target interface identifier; and determining the execution order of the interfaces based on the depth dependence order corresponding to the dependent interface identification.

As an example, if the target dependency information does not include a legal delimiter, it may be determined that the target dependency information only includes one dependency interface identifier, and at this time, the server needs to first traverse the interface test information table based on the dependency interface identifier to obtain a preamble test case and a depth dependency order corresponding to the dependency interface identifier. As shown in fig. 9, if the target interface identifier is T15, and the information corresponding to the dependency relationship field of the target interface identifier T15 in the interface test information table is "T10", it is only necessary to traverse the interface test information table based on the dependency interface identifier T10 in depth, and obtain the preamble test cases corresponding to the dependency interface identifier T10 as the interface test cases corresponding to T10, T7, T1, T5, and T2, and the depth dependency order corresponding to the preamble test cases is T1 → T7 → T2 → T5 → T10. Then, the server determines at least two dependent execution cases based on the target test case corresponding to the target interface identifier and all the preorder test cases; based on the depth dependence sequence corresponding to the dependent interface identifier, determining an interface execution sequence, namely after the target test case is added to the depth dependence sequence, determining the target test case as the last dependent execution case to achieve the purpose of quickly and effectively determining all the dependent execution cases and the interface execution sequence by adopting a depth traversal search mode without manually adjusting the interface execution sequence, which is beneficial to improving the interface automation test efficiency and avoiding test operation errors caused by missing or errors of the manually adjusted interface execution sequence in the interface automation test process.

In an embodiment, as shown in fig. 5, before step S201, that is, before obtaining the interface test request, the interface automated test method further includes:

s501: and acquiring original case codes and original configuration information corresponding to the interface to be put in storage.

The interface to be warehoused is the interface which needs warehousing at this time, namely the interface test case corresponding to the interface needs to be stored in the system database. The original case code is a pre-configured code for implementing interface testing of the interface logic function. The original configuration information is used for recording information corresponding to the interface to be warehoused, which is autonomously configured by a user in the process of storing the interface test case corresponding to the interface to be warehoused into a system database.

Generally, the original configuration information includes a configuration interface identification, a configuration interface name, a configuration URL, and interface dependency information. The configuration interface identifier is an identifier which is autonomously configured by a user and is used for uniquely identifying the interface to be warehoused. Generally, the configuration interface identifier is a unique identifier generated based on a pre-interface generation rule, for example, the configuration interface identifier is in a format of "identifier character + sequence number character", as in T15, where T is an identifier character and 15 is a sequence number character. The configuration interface name is the name of the interface to be warehoused, which is autonomously configured by the user. And configuring the URL as the URL corresponding to the interface test case corresponding to the interface to be put in storage. The interface dependence information is information of recording preamble interface which is configured and maintained by user.

S502: and identifying the original case code to obtain interface parameter information corresponding to the interface to be put in storage.

As an example, after obtaining an original case code, the server identifies the original case code by using a character string identification algorithm, identifies a numerical value return code corresponding to an output character in the original case code, determines a corresponding parameter output interface variable and parameter output path according to the numerical value return code, and determines interface parameter output information corresponding to an interface to be put in storage based on all the parameter output interface variables and parameter output paths. It can be understood that the interface parameter output information corresponding to the interface to be warehoused may reflect that after the original case code corresponding to the interface to be warehoused is executed, the output parameter corresponding to the parameter of the parameter to be warehoused is stored in the parameter output path of the system memory, that is, the output parameter may be dynamically changed, but the parameter output path is not changed, so as to facilitate subsequent dynamic maintenance. Where the output characters are the characters in the original case code used to identify and locate the output parameters, e.g., return represents the return value. The numeric value return code is a code for returning a result numeric value in the original case code, and is generally set corresponding to an output character, as set after the output character.

Furthermore, after identifying the numerical value return code corresponding to the output character in the original case code, the duplication elimination processing needs to be performed on all the export interface variables appearing in all the numerical value return codes, where the duplication elimination processing can be performed on the export interface variables in the interface to be warehoused, and can also be performed on all the export interface variables in the interface to be warehoused in the system database, so as to ensure that all the export interface variables in the system database have uniqueness, and avoid the problem of variable coverage when an interface test case corresponding to the interface to be warehoused is executed subsequently, which leads to the problem that the interface test cannot be performed smoothly.

S503: and carrying out format verification on the original configuration information to obtain an information verification result.

Because the original configuration information is configured by the user in the process of storing the interface test case corresponding to the interface to be warehoused into the system database, the information corresponding to the interface to be warehoused can not be recorded if the original configuration information is directly stored in the interface test information table, and whether the original configuration information configured by the user can not be ensured to be successfully subjected to the interface automatic test due to the format problem or not can not be ensured. Therefore, when the interface test case corresponding to each interface to be warehoused is stored in the system database, the server needs to perform format check on the original configuration information corresponding to the interface to be warehoused, and needs to perform format check on information such as the configuration interface identifier, the configuration interface name, the configuration URL, the interface dependency information and the like by adopting format check logic so as to judge that the original configuration information of the interface to be warehoused meets warehousing conditions and acquire an information check result.

S504: and if the information verification result is that the verification is passed, determining the original configuration information as interface configuration information, and storing the interface configuration information and the interface parameter information in an interface test information table in an associated manner.

As an example, when the information verification result is that the verification passes, it may be determined that the original configuration information of the interface to be warehoused meets the pre-configured warehousing condition, at this time, the original configuration information may be determined as the interface configuration information corresponding to the interface to be warehoused and stored in the interface test information table, so as to implement quantitative maintenance on the interface detail information and the interface dependency information corresponding to the interface to be warehoused, and implement maintenance and execution of an interface automated test that supports a complex interface dependency relationship or a large data volume through the interface test information table. Correspondingly, when the information verification result is that the verification is passed, the interface parameter information of the interface to be warehoused can be stored in the interface test information table, so that in the process of carrying out the interface automatic test on the interface to be executed which needs to depend on the output parameter of the interface to be warehoused, the input parameter which depends on the interface test information table can be dynamically determined based on the interface test information table, the test efficiency and flexibility of the interface automatic test with the data dependency relationship are improved, and the operation and the maintenance are convenient.

In an embodiment, as shown in fig. 6, step S502 is to perform identification processing on an original case code, and acquire interface parameter information corresponding to an interface to be put into storage, where the method includes:

s601: and identifying the original case code to obtain at least one numerical value return code, wherein each numerical value return code comprises a parameter output interface variable and a parameter output path.

As an example, after acquiring an original case code, the server identifies the original case code by using a character string identification algorithm, identifies a numerical value return code corresponding to an output character in the original case code, and determines a corresponding parameter output interface variable and a parameter output path according to the numerical value return code. It can be understood that each original case code includes at least one output character, and each output character corresponds to one numeric return code, so that the server identifies the original case code and can obtain at least one numeric return code, where each numeric return code includes a parameter output interface variable and a parameter output path corresponding to a storage address of an output parameter corresponding to the parameter output interface variable in the system memory. It is understood that the number of the out-reference interface variables in each value return code may be one or more.

S602: and performing duplicate removal verification on all the output parameter interface variables to obtain a duplicate removal verification result.

As an example, the server may perform deduplication checking on all the out-of-reference interface variables appearing in the original case code to determine whether the original case code contains repeated out-of-reference interface variables, and obtain a deduplication checking result.

As another example, the server may perform deduplication checking on all the export interface variables appearing in the original case code and all the export interface variables of the library interfaces in the system database, and obtain a deduplication checking result.

It should be noted that the deduplication check here may be a process of matching all the parameter output interface variables by using a string matching algorithm to determine whether there is a duplicate parameter output interface variable, where the deduplication check result includes a pass check and a fail check, where the pass check is that there is no duplicate parameter output interface variable, and the fail check is that there is a duplicate parameter output interface variable.

S603: and if the duplicate removal verification result is that the verification is passed, synthesizing the parameter output paths corresponding to the parameter output interface variables and the parameter output paths corresponding to the parameter output interface variables by using a synthesizing tool to obtain original parameter output information.

The synthesis tool is a tool for implementing character synthesis, and may be a preset code that can implement a synthesis function.

As an example, the server uses a synthesis tool to perform synthesis processing on each parameter of the parameter output interface and the parameter output path corresponding to the parameter output interface, specifically, the parameter output interface and the parameter output path are connected by using an assignment symbol ═ to form original parameter output information corresponding to each parameter output interface. For example, if a certain parameter of the parameter-output interface is msg and the corresponding parameter-output path is results [0]. rettmsg, the parameter-output interface variable and the parameter-output path are merged by using the assignment symbol "═ to obtain the original parameter-output information of msg ═ results [0]. rettmsg. The original parameter-output information is the information synthesized by a single parameter-output interface variable and a parameter-output path.

S604: and if the number of the original parameter information is one, determining the original parameter information as the interface parameter information corresponding to the interface to be stored.

As an example, if only one parameter of the parameter output interface corresponding to the interface to be warehoused is provided, that is, the number of the formed original parameter output information is one, at this time, the original parameter output information can be directly determined as the interface parameter output information corresponding to the interface to be warehoused, the interface parameter output information is the original parameter output information which is subjected to deduplication verification and is formed by adopting a synthesis tool according to a standard format, and the occurrence of a situation that the output parameter cannot be called by other interfaces to be executed subsequently due to a form problem can be effectively avoided.

S605: and if the number of the original parameter information is at least two, combining the at least two original parameter information by adopting a preset separator to obtain interface parameter information corresponding to the interface to be warehoused.

The preset separator is a preset character for separating two adjacent original parameter information.

As an example, if the number of the parameter output interface variables corresponding to the to-be-warehoused interface is at least two, that is, the number of the original parameter output information formed by the to-be-warehoused interface is at least two, at this time, a preset delimiter is adopted to merge two adjacent original parameter output information in all the original parameter output information to determine the interface parameter output information corresponding to the to-be-warehoused interface, the interface parameter output information is the original parameter output information which is subjected to deduplication verification and is formed by adopting a synthesis tool according to a standard format, and the information formed by merging all the original parameter output information by adopting the preset delimiter is adopted, so that the occurrence of a situation that the output parameters cannot be called by other to-be-executed interfaces in the subsequent process due to the form problem can be effectively avoided.

In one embodiment, the original configuration information includes a configuration interface identification, a configuration interface name, a configuration URL, and interface dependency information. Accordingly, as shown in fig. 8, step S503 is to perform format verification on the original configuration information, and obtain an information verification result, including:

s701: and carrying out uniqueness check on the configuration interface identifier and the configuration interface name to obtain a uniqueness check result.

As an example, after receiving original configuration information, the server needs to compare a configuration interface identifier and a configuration interface name of the interface to be warehoused with a configuration interface identifier and a configuration interface name of an in-warehouse interface in an interface test information table, and if there is no in-warehouse interface with the same configuration interface identifier and/or configuration interface name, the interface to be warehoused is determined to have uniqueness, and a uniqueness check result that the check passes is obtained; if the in-library interface with the same configuration interface identifier and/or configuration interface name exists, namely the configuration interface identifier and/or configuration interface name does not have uniqueness, the uniqueness check result that the check fails is obtained.

S702: and carrying out feasibility verification on the configuration URL to obtain a feasibility verification result.

As an example, after acquiring original configuration information, the server needs to perform feasibility verification on a configuration URL, then triggers an access request based on the configuration URL, and if receiving corresponding preset time within preset time, acquires a feasibility verification result that the verification passes; and if the corresponding preset time is not received within the preset time, acquiring a feasibility verification result that the verification fails.

S703: and carrying out content verification on the interface dependence information to obtain a dependence verification result.

As an example, after acquiring original configuration information, the server needs to perform content verification on interface dependent information autonomously configured by a user by using a pre-configured content verification logic, and if the interface dependent information meets a format condition corresponding to the content verification logic, a dependency verification result that the verification passes is acquired; and if the interface dependency information does not meet the format condition corresponding to the content verification logic, acquiring a dependency verification result which is not verified.

S704: and if the uniqueness check result, the feasibility check result and the dependency check result are all passed through, acquiring the passed information check result.

As an example, if the uniqueness check result, the feasibility check result, and the dependency check result are all passed through, it is determined that the original configuration information of the interface to be warehoused meets the warehousing condition, and the information check result passed through the check is obtained, at this time, the original configuration information may be stored in the interface test information table as the interface configuration information in association with the interface export parameter information. Correspondingly, if at least one of the uniqueness check result, the feasibility check result and the dependency check result is not passed, the original configuration information of the interface to be warehoused is determined not to meet the warehousing condition, the information check result that the check is not passed is obtained, the original configuration information cannot be stored in the interface test information table as the interface configuration information and the interface output parameter information in an associated mode, and at the moment, the configuration error reminding information is generated and controlled by the client to be displayed, so that the user can correct the configuration error reminding information.

The original configuration information which passes the uniqueness check result as the check is stored in the interface test information table, so that uniqueness is guaranteed when the interface test information table is subsequently inquired, and the influence on the automatic interface test efficiency caused by incapability of inquiring or large number of inquiry results is avoided. The original configuration information of which the feasibility verification result is that the verification is passed is stored in the interface test information table, so that the corresponding configuration URL can be accessed in the subsequent execution process of the dependence execution case, and the feasibility of the interface automatic test is guaranteed. The original configuration information which passes the verification as the dependency verification result is stored in the interface test information table, which is beneficial to ensuring the accuracy of the interface dependency information of the interface to be warehoused, thereby ensuring the feasibility of performing deep traversal on the interface test information table based on the target dependency information and ensuring the feasibility of the interface automatic test.

In an embodiment, as shown in fig. 8, in step S703, performing content verification on the interface dependency information to obtain a dependency verification result, including:

s801: and if the interface dependency information is empty, acquiring a dependency verification result passing the verification.

As an example, when the server recognizes that the interface dependency information in the original configuration information is null, which indicates that the user does not configure the pre-order interface on which the interface depends for the interface to be warehoused, the server directly obtains the dependency verification result that the verification passes.

S802: and if the interface dependency information is not null, identifying whether the interface dependency information contains an illegal character string by adopting a character string matching algorithm.

The string matching algorithm is an algorithm for matching a specific string in the text content, and includes, but is not limited to, BF algorithm and KMP algorithm. An illegal string refers to a character other than the dependent interface identification and the legal delimiter. Because the dependent interface identifier is also a unique identifier generated based on the interface generation rule, the format of the dependent interface identifier is 'identifier character + serial number character', and the legal separator is a character which is configured in advance and used for separating two adjacent dependent interface identifiers, it can be known that the interface dependent information corresponding to each interface to be put in storage generally only comprises 'identifier character', 'serial number character' and 'legal separator', and all the other character strings are illegal character strings.

As an example, when recognizing that the interface dependency information in the original configuration information is not empty, the server recognizes the interface dependency information by using a character string matching algorithm, and determines whether the interface dependency information includes an illegal character string except for an "identification character", a "serial number character", and a "legal delimiter", so as to obtain a corresponding dependency check result.

S803: and if the interface dependency information contains the illegal character string, acquiring a dependency verification result which cannot be verified.

As an example, if the interface dependency information includes an illegal character string except for an "identification character", a "serial number character" and a "legal delimiter", directly obtaining a dependency verification result that the verification fails to pass, so as to send configuration error reminding information to the client, so that the user corrects the configuration error reminding information and deletes the corresponding illegal character string, thereby ensuring the feasibility of performing deep traversal on the interface test information table based on the target dependency information, and ensuring the feasibility of the interface automation test.

S804: and if the interface dependency information does not contain the illegal character string, extracting the dependency interface identifier from the interface dependency information, and judging whether the dependency interface identifier is the in-library interface identifier or not.

The library interface identifier is a configuration interface identifier corresponding to the library interface, the library interface is an interface which stores the interface test case in the system database before the current time of the system, and the interface configuration information is stored in the interface test information table.

As an example, when the interface dependency information does not contain an illegal character string, a character string recognition algorithm may be used to extract all the dependent interface identifications from the interface dependency information; whether the dependent interface identification is the in-library interface identification needs to be judged so as to avoid the situation that the preorder test case corresponding to the target test case cannot be determined when the interface test information table is deeply traversed based on the target dependent information, and the feasibility of the automatic interface test is favorably ensured.

S805: if the dependent interface identifier is the in-library interface identifier, acquiring the number of the dependent interface identifiers in the interface dependent information; when the number of the dependent interface identifiers is one, obtaining a dependent verification result which passes verification; and when the number of the dependent interface identifications is at least two, judging whether a legal separator is arranged between two adjacent dependent interface identifications, and if the legal separator is arranged between two adjacent dependent interface identifications, acquiring the dependent verification result of which the verification passes.

As an example, when the dependent interface identifier is the in-library interface identifier, the number of the dependent interface identifiers needs to be obtained. And if the number of the dependent interface identifications is one, directly obtaining a dependent verification result which passes the verification so as to carry out deep traversal on the interface test information table based on one dependent interface identification in the following process. If the number of the dependency interface identifications is at least two, whether a legal separator is arranged between two adjacent dependency interface identifications or not is needed, and if the legal separator is arranged between two adjacent dependency interface identifications, a dependency check result passing the check is obtained, so that the situation that at least two dependency interface identifications in the target dependency information cannot be identified based on the legal separator in the follow-up process due to the fact that the two adjacent dependency interface identifications are isolated without adopting the legal separator is avoided, and the feasibility of deeply traversing the interface test information table based on the at least two dependency interface identifications is guaranteed.

S806: and if the dependent interface identifier is not the library interface identifier, or a legal separator is not arranged between two adjacent dependent interface identifiers, acquiring a dependent verification result which cannot pass the verification.

As an example, if the dependent interface identifier is not the in-library interface identifier, obtaining a dependent verification result that the verification fails to pass, so as to send configuration error reminding information to the client, so that the user can correct the configuration error reminding information according to the configuration error reminding information, thereby avoiding the occurrence of a situation that a preorder test case corresponding to a target test case cannot be determined when the interface test information table is deeply traversed based on the target dependent information, and being beneficial to ensuring the feasibility of the interface automated test.

As an example, under the condition that the dependent interface identifiers are library-in interface identifiers and the number of the dependent interface identifiers is at least two, if no legal separator is arranged between two adjacent dependent interface identifiers, a dependency verification result that the verification fails is obtained so as to send configuration error reminding information to the client, so that a user can correct the configuration error reminding information according to the configuration error reminding information, thereby avoiding the situation that at least two dependent interface identifiers in target dependency information cannot be identified based on the legal separator in the follow-up process due to the fact that the two adjacent dependent interface identifiers are isolated without adopting the legal separator, and ensuring the feasibility of traversing the interface test information table based on at least two dependent interface identifiers.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In an embodiment, an interface automatic testing apparatus is provided, which corresponds to the interface automatic testing method in the above embodiments one to one. As shown in fig. 10, the interface automation test apparatus includes an interface test request obtaining module 101, an interface parameter entry information obtaining module 102, a parameter entry interface variable obtaining module 103, a parameter entry path obtaining module 104, a parameter value to be entered obtaining module 105, and an interface test result obtaining module 106. The functional modules are explained in detail as follows:

the interface test request obtaining module 101 is configured to obtain an interface test request, where the interface test request includes an identifier of an interface to be executed.

The interface parameter information obtaining module 102 is configured to obtain an original case code corresponding to a test case to be executed according to the interface identifier to be executed, and extract interface parameter information corresponding to an interface parameter field in the original case code.

And the parameter access interface variable acquiring module 103 is configured to acquire a parameter access interface variable corresponding to the variable reference identifier if the interface parameter access information includes the variable reference identifier.

And a parameter entry path obtaining module 104, configured to query interface parameter exit information in the interface test information table based on the parameter entry interface variable, and obtain a parameter entry path corresponding to the parameter entry interface variable.

And a parameter-to-be-entered variable value obtaining module 105, configured to obtain a parameter-to-be-entered variable value corresponding to the parameter-to-be-entered interface variable based on the parameter-to-be-entered parameter path corresponding to the parameter-to-be-entered interface variable.

The interface test result obtaining module 106 is configured to use the value of the parameter to be entered as an input parameter of the interface parameter entry field, form an effective case code corresponding to the test case to be executed, execute the effective case code, and obtain an interface test result.

Preferably, the parameter value to be entered obtaining module 105 includes:

and the historical variable value query unit is used for querying the system memory based on the parameter input path corresponding to the parameter input interface variable and judging whether the system memory stores the historical variable value corresponding to the parameter input interface variable.

And the first variable value determining unit is used for determining the historical variable value corresponding to the parameter input interface variable as the value of the parameter to be input corresponding to the parameter input interface variable if the historical variable value corresponding to the parameter input interface variable is stored.

And the second variable value determining unit is used for determining at least two dependence test cases and an interface execution sequence based on the target dependence information corresponding to the parameter input interface variable and the interface test information table in a deep traversal mode if the historical variable value corresponding to the parameter input interface variable is not stored, sequentially executing at least two test cases to be executed according to the interface execution sequence, and acquiring the parameter input variable value corresponding to the parameter input interface variable.

Preferably, the second variable value determining unit includes:

and the separator identifier subunit is used for identifying the target dependency information corresponding to the access interface variable and determining whether the target dependency information contains a legal separator.

The first traversal processing subunit is used for determining at least two dependency interface identifications and a peer dependency sequence from the target dependency information if the target dependency information comprises a legal delimiter; acquiring a preorder test case and a depth dependence sequence corresponding to each dependence interface identification based on at least two dependence interface identification depth traversal interface test information tables; determining at least two dependent execution cases based on a target test case corresponding to the target interface identification and all the preorder test cases; and determining an interface execution order based on the depth dependency order and the peer dependency order corresponding to the at least two dependent interface identifications.

The second traversal processing subunit is used for determining a dependent interface identifier from the target dependent information if the target dependent information does not contain a legal separator, acquiring a pre-order test case and a depth-dependent order corresponding to the dependent interface identifier based on a depth traversal interface test information table of the dependent interface identifier, and determining at least two dependent execution cases based on the target test case and all the pre-order test cases corresponding to the target interface identifier; and determining the execution order of the interfaces based on the depth dependence order corresponding to the dependent interface identification.

Preferably, the interface automation test device further comprises:

and the code information acquisition device is used for acquiring the original case code and the original configuration information corresponding to the interface to be put in storage.

And the interface parameter information acquisition module is used for identifying and processing the original case code and acquiring the interface parameter information corresponding to the interface to be put in storage.

And the information verification result acquisition module is used for carrying out format verification on the original configuration information and acquiring an information verification result.

And the interface information association storage module is used for determining the original configuration information as interface configuration information if the information verification result is that the verification is passed, and storing the interface configuration information and the interface parameter information in an interface test information table in an association manner.

Preferably, the interface parameter information obtaining module includes:

and the numerical value return code acquisition unit is used for identifying the original case code and acquiring at least one numerical value return code, and each numerical value return code comprises a parameter output interface variable and a parameter output path.

And the duplication-elimination-check result acquisition unit is used for carrying out duplication elimination check on all the output parameter interface variables and acquiring duplication-elimination check results.

And the original parameter-output information acquisition unit is used for synthesizing the parameter-output paths corresponding to the parameter-output interface variables and the parameter-output interface variables by adopting a synthesis tool if the duplication-elimination check result is that the verification is passed, and acquiring the original parameter-output information.

And the first parameter information acquisition unit is used for determining the original parameter information as the interface parameter information corresponding to the interface to be warehoused if the number of the original parameter information is one.

And the second parameter information acquiring unit is used for merging the at least two original parameter information by adopting a preset separator if the number of the original parameter information is at least two, and acquiring the interface parameter information corresponding to the interface to be warehoused.

Preferably, the information verification result obtaining module includes:

and the uniqueness check result acquisition unit is used for carrying out uniqueness check on the configuration interface identifier and the configuration interface name to acquire a uniqueness check result.

And the feasibility verification result acquisition unit is used for performing feasibility verification on the configuration URL and acquiring a feasibility verification result.

And the dependence check result acquisition unit is used for carrying out content check on the interface dependence information and acquiring a dependence check result.

And the verification passing result acquiring unit is used for acquiring the information verification result which passes the verification if the uniqueness verification result, the feasibility verification result and the dependence verification result are all verification passing.

Preferably, the dependency check result obtaining unit includes:

and the first passing result acquiring subunit is used for acquiring the dependence checking result of passing the checking if the interface dependence information is empty.

And the illegal character string judging subunit is used for identifying whether the interface dependent information contains the illegal character string by adopting a character string matching algorithm if the interface dependent information is not empty.

And the first non-passing result acquiring subunit is used for acquiring a dependence checking result of which the checking is not passed if the interface dependence information contains an illegal character string.

And the library interface identifier judging subunit is used for extracting the dependent interface identifier from the interface dependent information and judging whether the dependent interface identifier is the library interface identifier or not if the interface dependent information does not contain the illegal character string.

The second pass result acquiring subunit is used for acquiring the number of the dependent interface identifiers in the interface dependent information if the dependent interface identifiers are the library-in interface identifiers; when the number of the dependent interface identifiers is one, obtaining a dependent verification result which passes verification; and when the number of the dependent interface identifications is at least two, judging whether a legal separator is arranged between two adjacent dependent interface identifications, and if the legal separator is arranged between two adjacent dependent interface identifications, acquiring the dependent verification result of which the verification passes.

And the second non-passing result obtaining subunit is used for obtaining the dependence check result which cannot pass the check if the dependence interface identifier is not the in-library interface identifier or a legal separator is not arranged between two adjacent dependence interface identifiers.

For specific limitations of the interface automated testing apparatus, reference may be made to the above limitations of the interface automated testing method, which are not described herein again. All or part of each module in the interface automatic testing device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for executing data adopted or generated in the process of the interface automatic test method, and the data comprises but is not limited to an interface test information table. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method for automated testing of an interface.

In an embodiment, a computer device is provided, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and when the processor executes the computer program, the steps of the interface automation test method in the foregoing embodiments are implemented, for example, steps S201 to S206 shown in fig. 2 or steps shown in fig. 3 to 8, which are not described herein again to avoid repetition. Alternatively, the functions of each module/unit in the embodiment of the interface automatic testing apparatus are realized when the processor executes the computer program, for example, the functions of the interface test request obtaining module 101, the interface parameter entering information obtaining module 102, the parameter entering interface variable obtaining module 103, the parameter entering path obtaining module 104, the parameter value to be entered obtaining module 105, and the interface test result obtaining module 106 shown in fig. 10 are not described herein again to avoid repetition.

In an embodiment, a computer-readable storage medium is provided, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the interface automation testing method in the foregoing embodiments are implemented, for example, steps S201 to S206 shown in fig. 2 or steps shown in fig. 3 to fig. 8, which are not described herein again to avoid repetition. Alternatively, the computer program, when executed by the processor, implements the functions of each module/unit in the embodiment of the interface automatic testing apparatus, for example, the functions of the interface test request obtaining module 101, the interface parameter entering information obtaining module 102, the parameter entering interface variable obtaining module 103, the parameter entering path obtaining module 104, the parameter value to be entered obtaining module 105, and the interface test result obtaining module 106 shown in fig. 10, which are not described herein again to avoid repetition.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.

Claims

1. An automated interface testing method, comprising:

2. The method for automatically testing the interface according to claim 1, wherein the obtaining the value of the parameter to be entered corresponding to the parameter of the parameter-entering interface based on the parameter path corresponding to the parameter-entering interface variable comprises:

inquiring a system memory based on a parameter input path corresponding to the parameter input interface variable, and judging whether the system memory stores a historical variable value corresponding to the parameter input interface variable;

if the historical variable value corresponding to the parameter input interface variable is stored, determining the historical variable value corresponding to the parameter input interface variable as the parameter value to be input corresponding to the parameter input interface variable;

if the historical variable value corresponding to the parameter input interface variable is not stored, the interface test information table is traversed deeply based on the target dependency information corresponding to the parameter input interface variable, at least two dependency test cases and an interface execution sequence are determined, the at least two test cases to be executed are executed in sequence according to the interface execution sequence, and the parameter input variable value corresponding to the parameter input interface variable is obtained.

3. The method for automatically testing the interface of claim 2, wherein the deeply traversing the interface test information table based on the target dependency information corresponding to the input-parameter interface variable to determine at least two dependent test cases and an interface execution order comprises:

identifying target dependency information corresponding to the access parameter interface variable, and determining whether the target dependency information contains a legal delimiter;

if the target dependency information comprises legal delimiters, determining at least two dependency interface identifications and a peer dependency sequence from the target dependency information; traversing the interface test information table based on at least two dependency interface identifications in a depth manner, and acquiring a preamble test case and a depth dependency sequence corresponding to each dependency interface identification; determining at least two dependent execution cases based on the target test case corresponding to the target interface identification and all the preorder test cases; determining an interface execution order based on a depth dependency order and a peer dependency order corresponding to at least two dependency interface identifications;

if the target dependency information does not contain a legal separator, determining a dependency interface identifier from the target dependency information, traversing the interface test information table based on the dependency interface identifier in a deep manner, acquiring a preamble test case and a deep dependency sequence corresponding to the dependency interface identifier, and determining at least two dependency execution cases based on the target test case corresponding to the target interface identifier and all the preamble test cases; and determining the execution sequence of the interfaces based on the depth dependence sequence corresponding to the dependent interface identification.

4. The interface automation test method of claim 1 wherein prior to the obtaining the interface test request, the interface automation test method further comprises:

acquiring an original case code and original configuration information corresponding to an interface to be put in storage;

identifying the original case code to obtain interface parameter information corresponding to the interface to be put in storage;

carrying out format verification on the original configuration information to obtain an information verification result;

and if the information verification result is that the verification is passed, determining the original configuration information as interface configuration information, and storing the interface configuration information and the interface parameter information in an interface test information table in an associated manner.

5. The method for automatically testing the interface according to claim 4, wherein the identifying the original case code to obtain the interface parameter information corresponding to the interface to be put in storage comprises:

identifying the original case code to obtain at least one numerical value return code, wherein each numerical value return code comprises a parameter output interface variable and a parameter output path;

performing duplicate removal verification on all the parameter output interface variables to obtain a duplicate removal verification result;

if the duplication removal verification result is that the verification is passed, synthesizing the parameter output paths corresponding to the parameter output interface variables and the parameter output paths corresponding to the parameter output interface variables by using a synthesizing tool to obtain original parameter output information;

if the number of the original parameter information is one, determining the original parameter information as interface parameter information corresponding to the interface to be warehoused;

and if the number of the original parameter information is at least two, combining the at least two original parameter information by adopting a preset separator to obtain interface parameter information corresponding to the interface to be warehoused.

6. The method for automatically testing an interface of claim 4, wherein the performing format verification on the original configuration information and obtaining an information verification result comprises:

carrying out uniqueness check on the configuration interface identifier and the configuration interface name to obtain a uniqueness check result;

carrying out feasibility verification on the configuration URL to obtain a feasibility verification result;

performing content verification on the interface dependence information to obtain a dependence verification result;

and if the uniqueness check result, the feasibility check result and the dependency check result are all passed, acquiring an information check result passed by the check.

7. The method for automatically testing the interface according to claim 6, wherein the performing the content verification on the interface dependency information and obtaining the dependency verification result comprises:

if the interface dependency information is empty, acquiring a dependency verification result passing the verification;

if the interface dependency information is not empty, identifying whether the interface dependency information contains an illegal character string by adopting a character string matching algorithm;

if the interface dependency information contains an illegal character string, acquiring a dependency verification result which cannot be verified;

if the interface dependency information does not contain the illegal character string, extracting a dependency interface identifier from the interface dependency information, and judging whether the dependency interface identifier is an in-library interface identifier or not;

if the dependent interface identifier is the in-library interface identifier, acquiring the number of the dependent interface identifiers in the interface dependent information; when the number of the dependent interface identifiers is one, obtaining a dependent verification result which passes verification; when the number of the dependent interface identifications is at least two, judging whether a legal separator is arranged between every two adjacent dependent interface identifications, and if the legal separator is arranged between every two adjacent dependent interface identifications, acquiring a dependent verification result passing the verification;

and if the dependent interface identifier is not the in-library interface identifier or a legal separator is not arranged between two adjacent dependent interface identifiers, acquiring a dependent verification result which cannot pass the verification.

8. An automated interface testing device, comprising:

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the interface automation test method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method for automated testing of an interface according to any one of claims 1 to 7.