CN112540924A

CN112540924A - Interface automation test method, device, equipment and storage medium

Info

Publication number: CN112540924A
Application number: CN202011476106.0A
Authority: CN
Inventors: 纪海杰
Original assignee: Ping An Life Insurance Company of China Ltd
Current assignee: Ping An Life Insurance Company of China Ltd
Priority date: 2020-12-15
Filing date: 2020-12-15
Publication date: 2021-03-23

Abstract

The invention relates to the technical field of pedestal operation and maintenance, and discloses an interface automatic testing method, device, equipment and storage medium. The method comprises the following steps: creating a test item; receiving an interface automation test case generation instruction, and generating a plurality of interface automation test cases; when an interface automatic test request is received, a corresponding interface to be tested is determined according to the interface automatic test request, an interface test is carried out on a target interface automatic test case to obtain a test result, and the test result is arranged into a test report to be displayed on a front-end page. The scheme supports the automatic test access of the multi-project interface, reduces the cost of manual entry and maintenance, and solves the technical problem of resource preemption of the test machine when multiple projects are tested simultaneously, thereby improving the efficiency of interface test and the use experience of users.

Description

Interface automation test method, device, equipment and storage medium

Technical Field

The invention relates to the technical field of pedestal operation and maintenance, in particular to an interface automatic test method, device, equipment and storage medium.

Background

At present, with the increasing development of computer technology, more and more systems providing various application functions to people are provided, and in order to ensure the stability of system operation, corresponding tests are usually performed on interfaces of the systems in the development process. The http-(s) -oriented universal test framework is a universal test framework for http-(s) -oriented protocols, and a tester only needs to write and maintain yml test scripts to realize interface testing.

Interface testing is a test that tests an interface between components of a system. The interface test is mainly used for detecting interaction points between external systems and between internal subsystems. The key point of the test is to check the exchange of data, transfer and control management processes, mutual logic dependency relationship between systems and the like. When the httprener frame is locally used for interface test, the workload of interface information input and maintenance is large; and 3, the test report is inconvenient to store and check, the historical test results are difficult to compare, and much inconvenience is brought to the test of a user.

Disclosure of Invention

The invention mainly aims to solve the technical problems of resource preemption of a tester and low operation efficiency when httprener framework multiple items are tested simultaneously in the industry.

The invention provides an interface automatic testing method in a first aspect, which comprises the following steps:

creating a test item, wherein the test item comprises at least one test object;

receiving an interface automatic test case generation instruction, and generating an interface automatic test case;

receiving an interface automatic test request, analyzing the interface automatic test request, and generating a corresponding interface to be tested;

sending the interface automation test case to the interface to be tested for testing to obtain a test result;

and generating a test report according to the test result, and sending the test report to a front-end page.

Optionally, in a first implementation manner of the first aspect of the present invention, after the creating a test item, the method further includes:

acquiring all test objects contained in the test items;

and setting the test parameters of the test objects, and setting the test flow corresponding to the test objects according to the number of the test objects and a preset execution sequence.

Optionally, in a second implementation manner of the first aspect of the present invention, the receiving an interface automation test case generation instruction, and generating an interface automation test case includes:

receiving an interface automation test case generation request, and acquiring an interface parameter document;

determining an array corresponding to the interface information according to the interface document data, wherein the array comprises: interface address path, transfer mode, and parameter of entering parameter;

assigning the array to a corresponding interface, and loading the array to a script to obtain an execution script, wherein the script is created on an interface test tool in advance;

and performing interface test on the interface test tool through the execution script to generate an interface automation test case.

Optionally, in a third implementation manner of the first aspect of the present invention, the receiving an interface automation test request, and analyzing the interface automation test request to generate a corresponding interface to be tested includes:

receiving an interface automatic test request, and analyzing the interface automatic test request to obtain corresponding to-be-tested interface information;

and calling an initial interface in an automatic testing platform, and configuring the initial interface according to the information of the interface to be tested so as to generate a corresponding interface to be tested.

Optionally, in a fourth implementation manner of the first aspect of the present invention, the sending the interface automation test case to the interface to be tested for testing, and obtaining a test result includes:

acquiring a preset interface test template corresponding to the interface to be tested;

updating the test parameters in the interface automation test template according to the interface automation test request, and screening out a target interface automation test case corresponding to the update result from the interface automation test cases according to the update result;

calling an interface to be tested corresponding to the target interface automatic test case;

testing the interface to be tested through the target interface automatic test case to obtain an interface execution result;

and dynamically judging the interface execution result through preset result verification data to obtain the test result of the target interface automatic test case.

Optionally, in a fifth implementation manner of the first aspect of the present invention, before the obtaining a preset interface test template corresponding to the interface to be tested, the method further includes:

inquiring an interface code corresponding to the interface to be tested;

identifying a data flow path of the interface to be tested according to the interface code;

determining a corresponding path division condition according to the data flow path;

and generating the test parameters according to the path division conditions, and constructing the interface test template according to the test parameters.

The second aspect of the present invention provides an interface automation testing apparatus, including:

the system comprises a creating module, a judging module and a judging module, wherein the creating module is used for creating a test item, and the test item comprises at least one test object;

the generating module is used for receiving an interface automatic test case generating instruction and generating an interface automatic test case;

the analysis module is used for receiving an interface automatic test request, analyzing the interface automatic test request and generating a corresponding interface to be tested;

the test module is used for sending the interface automation test case to the interface to be tested for testing to obtain a test result;

and the sending module is used for generating a test report according to the test result and sending the test report to a front-end page.

Optionally, in a first implementation manner of the second aspect of the present invention, the interface automation test apparatus further includes:

the acquisition module is used for acquiring all test objects contained in the test items;

and the execution module is used for setting the test parameters of the test objects and setting the test flow corresponding to the test objects according to the number of the test objects and the preset execution sequence.

Optionally, in a second implementation manner of the second aspect of the present invention, the generating module is specifically configured to:

Optionally, in a third implementation manner of the second aspect of the present invention, the parsing module is specifically configured to:

Optionally, in a fourth implementation manner of the second aspect of the present invention, the test module includes:

the acquisition unit is used for acquiring a preset interface test template corresponding to the interface to be tested;

the screening unit is used for updating the test parameters in the interface automation test template according to the interface automation test request and screening out a target interface automation test case corresponding to the update result from the interface automation test cases according to the update result;

the calling unit is used for calling the interface to be tested corresponding to the target interface automatic test case;

the test unit is used for testing the interface to be tested through the target interface automatic test case to obtain an interface execution result;

and the judging unit is used for dynamically judging the interface execution result through preset result verification data to obtain the test result of the target interface automatic test case.

Optionally, in a fifth implementation manner of the second aspect of the present invention, the interface automation test apparatus further includes:

the query module is used for querying the interface code corresponding to the interface to be tested;

the identification module is used for identifying the data flow path of the interface to be tested according to the interface code;

a determining module, configured to determine a corresponding path division condition according to the data flow path; and the interface test template is constructed according to the test parameters.

A third aspect of the present invention provides an interface automation test apparatus, including: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line;

the at least one processor calls the instructions in the memory to cause the interface automation test equipment to execute the interface automation test method.

A fourth aspect of the present invention provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute the above-mentioned interface automation test method.

In the technical scheme provided by the invention, a test project is created; receiving an interface automation test case generation instruction, and generating a plurality of interface automation test cases; when an interface automatic test request is received, a corresponding interface to be tested is determined according to the interface automatic test request, an interface test is carried out on a target interface automatic test case to obtain a test result, and the test result is arranged into a test report to be displayed on a front-end page. The scheme supports the automatic test access of the multi-project interface, reduces the cost of manual entry and maintenance, and solves the technical problem of resource preemption of the test machine when multiple projects are tested simultaneously, thereby improving the efficiency of interface test and the use experience of users.

Drawings

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

FIG. 2 is a diagram of a second embodiment of the interface automatic test method according to the present invention;

FIG. 3 is a diagram of an interface automated testing method according to a third embodiment of the present invention;

FIG. 4 is a diagram of a fourth embodiment of the interface automatic test method according to the present invention;

FIG. 5 is a diagram of a fifth embodiment of the interface automatic test method according to the present invention;

FIG. 6 is a schematic diagram of a first embodiment of an automated interface testing apparatus according to the present invention;

FIG. 7 is a schematic diagram of a second embodiment of an automated interface testing apparatus according to the present invention;

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

Detailed Description

The embodiment of the invention provides an interface automatic test method, a device, equipment and a storage medium, wherein in the technical scheme of the invention, a test project is firstly created; receiving an interface automation test case generation instruction, and generating a plurality of interface automation test cases; when an interface automatic test request is received, a corresponding interface to be tested is determined according to the interface automatic test request, an interface test is carried out on a target interface automatic test case to obtain a test result, and the test result is arranged into a test report to be displayed on a front-end page. The scheme supports the automatic test access of the multi-project interface, reduces the cost of manual entry and maintenance, and solves the technical problem of resource preemption of the test machine when multiple projects are tested simultaneously, thereby improving the efficiency of interface test and the use experience of users.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," or "having," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

For convenience of understanding, a detailed flow of the embodiment of the present invention is described below, and referring to fig. 1, a first embodiment of an interface automation test method in the embodiment of the present invention includes:

101. creating a test item, wherein the test item comprises at least one test object;

in the embodiment, firstly, at least one title character string in a specific format is acquired from a requirement document corresponding to a test project; searching a target process keyword matched with the acquired title character string in a preset process keyword set; and generating a test execution flow corresponding to the test item according to at least one target flow keyword, wherein the test execution flow comprises test flow steps corresponding to the at least one target flow keyword respectively.

In this embodiment, the character content of each line in the requirement document may be read, and whether the character at the preset character position in the character content of each line in the requirement document corresponding to the test item is matched with the preset character is detected; if the character at the preset character position is matched with the preset character, determining the residual character excluding the character at the preset character position in the character content of the line as the title character string; traversing a database where the preset process keyword set is located, sequentially matching the title character strings obtained from the required document with the traversed process keywords, and storing the target process keywords when the obtained title character strings are the same as the target process keywords in the preset process keyword set; and determining the subordination relation among the title character strings according to the positions of the lines of the title character strings, and further determining the subordination relation among the target process keywords. Optionally, a tree structure may be obtained according to the dependency relationship between the title character strings of the requirement document, and the dependency relationship between the target process keywords may be obtained according to the tree structure, so as to complete the creation of the test execution process corresponding to each target process keyword.

A test item refers to a description of a test task for a particular software product, embodying test schemes, methods, techniques, and strategies, i.e., a particular set of input data, operations, or various environmental settings, and desired results, provided to the system under test for conducting the test. The content of the test case comprises a test target, a test environment, input data, a test step, a preset condition, a case number, an expected result and the like. For example, a plurality of functional software, such as WeChat, Paibao, Taobao, etc., may be installed on a terminal, such as a mobile phone or a computer, and the functions of these functional software may be implemented by program codes, so as to facilitate installation and maintenance of the program codes, a plurality of Application Programming Interfaces (API) are set in the codes, where the API is a predefined function, and the purpose is to provide the capability of an Application and a developer to access a set of routines based on certain software or hardware, without accessing the source code or understanding details of an internal working mechanism.

Before each function is marketed for users to use, in order to ensure the normal implementation of the function, the interface needs to be tested, the test items are some functions to be tested corresponding to each functional software, the test objects are specific test contents, and one test object corresponds to at least one specific test case. Taking an interface for realizing a payment function as an example, when an account name and an input payment password are correct, successful payment can be realized, and only one scene may be available; however, when the account or the password has an error, the payment is not successful, which includes various scenarios, for example, the account name and the password are both wrong or the account name or the password has an error, and the payment is not successful. Testing is needed for the successful or failed payment, parameters used when the payment is successful and various payments are unsuccessful are edited into interface document data and stored in a document library of terminal equipment such as a computer or a mobile phone. The account name and the password are used as parameter variables of the interface document data, and the error or correct value of the parameter variable is a variable value.

102. Receiving an interface automatic test case generation instruction, and generating an interface automatic test case;

in this embodiment, an interface automation test case generation instruction is received, where the generation instruction carries parameter information corresponding to a test case, and interface document data corresponding to the interface automation test case is determined according to the parameter information carried in the generation instruction.

Further, analyzing the interface document data, and determining an array of each interface based on the interface document data, wherein the array includes: interface address path, transfer mode, and entry parameters. The function code can be utilized to analyze the interface document data by writing the function code, for example, the address of the interface document data is used as the parameter, and then the code is written to obtain the array of each interface in the interface document data by page grabbing. After the arrays are assigned to the interfaces, the arrays assigned to the interfaces can form a data packet, and the interface test tool refers to the data packet through the plug-in. The method comprises the following steps of loading arrays assigned to each interface to a script to obtain an execution script, wherein the steps of: circularly traversing the arrays assigned to the interfaces, and taking out the values assigned to the arrays; making new variable names for all the values taken out of the array; and loading the measured parameter values acquired from the interface test tool in advance into the new variable names to be used as variables to obtain the execution script. And finally generating an interface test case through an interface test tool by utilizing each variable in the execution script. In order to record each variable change conveniently, after the interface automation test case is generated, each change condition of the interface automation test case is recorded and stored to form an interface case change log, and the interface automation test case change log is output in a file form. The change log of the interface automation test case can be output in a txt, html and excl form.

In this embodiment, the interface automation test is to perform maintenance and detection on functions that have been developed and brought online by developers, firstly, maintain the usability of the existing functions, and secondly, detect whether the newly developed interface has an influence on the original functions after deployment, so that the original functions are not usable. Meanwhile, as the response time of the interface is short, developers can quickly locate the interface with the abnormity, thereby quickly repairing the abnormity and accelerating the iteration cycle of the version.

103. Receiving an interface automatic test request, analyzing the interface automatic test request, and generating a corresponding interface to be tested;

in this embodiment, when a user needs to perform an automated test on a single interface on an automated test platform, an interface automated test request may be sent to the management server, where the interface automated test request may generally include information of the interface that the user needs to perform the test, and the like. After receiving the interface test automation request, the management server can directly analyze the interface test automation request, so as to obtain the information of the interface to be tested in the interface test automation request.

In this embodiment, the automatic test platform may be equipped with a plurality of initial interfaces capable of performing testing, so as to determine a corresponding interface to be tested according to the requirements of a user, so as to complete a corresponding test. Therefore, the management server can call the initial interface of the automatic test platform and carry out corresponding configuration on the initial interface according to the information of the interface to be tested, so that the corresponding interface to be tested can be generated.

104. Sending the interface automation test case to an interface to be tested for testing to obtain a test result;

in this embodiment, when a user needs to test a single interface on the automated testing platform, an interface automated testing request may be sent to the management server, where the interface automated testing request may generally include information of the interface that the user needs to test.

In this embodiment, after the target interface automated test case corresponding to the interface automated test request is obtained, the interface to be tested is called, specifically, the interface automated test case may be executed through a TestNG test suite, an Ant script, or a Jenkins tool, the corresponding interface to be tested is called through the interface automated test case, and further, the interface to be tested is automatically tested according to the interface test, so as to obtain an interface execution result. The interface test result of the interface in the test case is obtained by sequentially executing the execution script corresponding to each test interface in the target interface automatic test case, wherein if the test result is consistent with the expected result, the result indicates that some APP function corresponding to the test can normally run; if the test result is inconsistent with the expected result, it indicates that some APP corresponding to the test has a functional defect and cannot normally operate, and improvement and maintenance are required.

105. And generating a test report according to the test result, and sending the test report to a front-end page.

In this embodiment, the test result generated after each interface test script is executed is written into a preset test report, and the test report is stored and pushed to a front-end page for display, so that developers can conveniently check the test result, and compare the test result with a historical test result to analyze the defects and the stability of the interface to be tested.

According to the embodiment of the invention, a test project is created; receiving an interface automation test case generation instruction, and generating a plurality of interface automation test cases; when an interface automatic test request is received, a corresponding interface to be tested is determined according to the interface automatic test request, an interface test is carried out on a target interface automatic test case to obtain a test result, and the test result is arranged into a test report to be displayed on a front-end page. The scheme supports the automatic test access of the multi-project interface, reduces the cost of manual entry and maintenance, and solves the technical problem of resource preemption of the test machine when multiple projects are tested simultaneously, thereby improving the efficiency of interface test and the use experience of users.

In the embodiment of the invention, the test items are created; receiving an interface automation test case generation instruction, and generating a plurality of interface automation test cases; when an interface automatic test request is received, a corresponding interface to be tested is determined according to the interface automatic test request, an interface test is carried out on a target interface automatic test case to obtain a test result, and the test result is arranged into a test report to be displayed on a front-end page. The scheme supports the automatic test access of the multi-project interface, reduces the cost of manual entry and maintenance, and solves the technical problem of resource preemption of the test machine when multiple projects are tested simultaneously, thereby improving the efficiency of interface test and the use experience of users.

Referring to fig. 2, a second embodiment of the method for automatically testing an interface according to the embodiment of the present invention includes:

201. creating a test item;

202. acquiring all test objects contained in the test items;

in this embodiment, all test objects included in the created test item are obtained. The test items are some functions which need to be tested and correspond to each functional software, and the test objects are specific test contents.

In this embodiment, the test content specifically refers to a plurality of functional software installed on a terminal such as a mobile phone or a computer, for example, a WeChat, Paibao, Taobao, and the like, where functions of the functional software may be implemented by a program code, and in order to facilitate installation and maintenance of the program code, a plurality of API interfaces (also called Application Programming interfaces) are set in the code, and are predefined functions, and are intended to provide capabilities of an Application and a developer to access a set of routines based on certain software or hardware, without accessing a source code or understanding details of an internal working mechanism.

Further, before each function is marketed for users, the interface needs to be tested in order to ensure its proper functioning. Taking an interface for realizing a payment function as an example, when an account name and an input payment password are correct, successful payment can be realized, and only one scene may be available; however, when an account or a password has an error, the payment is not successful, which includes various scenarios, for example, the account name and the password are both wrong or the account name or the password has an error, neither payment is successful, the payment success nor payment failure needs to be tested, parameters used when the payment is successful and various payment failures are edited into interface document data, and the parameters are stored in a document library of a terminal device such as a computer or a mobile phone. The account name and the password are used as parameter variables of the interface document data, and the error or correct value of the parameter variable is a variable value.

203. Setting test parameters of the test objects, and setting test flows corresponding to the test objects according to the number of the test objects and a preset execution sequence;

in this embodiment, the interface test apparatus creates at least one test object based on the protocol base class and the inheritance base class of the test object. The test object refers to a module interface for performing interface test, such as a user interface, a universal gateway interface, a bottom layer service interface, a timing script interface, and the like. The protocol base class here can be HTTP protocol, TCP protocol, or Middle protocol, etc. The inheritance base class is base class information inherited by the existing test object from the parent class. If the parent TrpcClient can realize the content communication protocol, the corresponding test object can directly inherit the TrpcClient.

And then the interface testing device can set the testing parameters of the testing object in a dictionary form, so that a tester can adjust the testing parameters according to an actual scene.

The interface testing device sets a testing flow corresponding to the testing object by taking a basic library interface and a third-party library interface of the common frame database as calling resources based on the number of the testing objects and the execution sequence of the testing objects which are set in advance. The test flow refers to a test flow for performing an interface automation test on the test object, such as an encryption/decryption operation, a protocol conversion operation, a login operation, a remote execution operation, and the like.

204. Receiving an interface automation test case generation request, and acquiring an interface parameter document;

in this embodiment, a plurality of functional software may be installed on a terminal such as a mobile phone or a computer, and functions of the functional software may be implemented by a program code, and in order to facilitate installation and maintenance of the program code, a plurality of API (Application Programming Interface) interfaces are set in the code, where the API interfaces are predefined functions, and are intended to provide an ability for an Application and a developer to access a set of routines based on certain software or hardware without accessing a source code or understanding details of an internal work mechanism. In this embodiment, the automatic generation of the interface automation test case is used to automatically generate the test case for testing the interface, specifically, when the processor obtains an interface case generation request, the interface document data is obtained from a document library on a terminal device such as a mobile phone or a computer, and the preferred interface document data is swagger.

The interface for implementing a certain function may include at least two cases, one is that the function is successfully implemented, and the other is that the function is not successfully implemented, where the successful implementation of the function may be in one scenario, and the unsuccessful implementation of the function may include many scenarios, taking the interface for implementing a payment function as an example, when an account name and an input payment password are both correct, a successful payment may be implemented, and there may be only one scenario; however, when an account or a password has an error, the payment is not successful, which includes various scenarios, for example, the account name and the password are both wrong or the account name or the password has an error, and neither payment is successful, and the payment success or failure needs to be tested, and parameters used when the payment is successful and various payment are unsuccessful are edited into interface document data and stored in a document library of a terminal device such as a computer or a mobile phone. The account name and the password are used as parameter variables of the interface document data, and the error or correct value of the parameter variable is a variable value.

205. Determining an array corresponding to the interface information according to the interface document data;

in this embodiment, the interface document data may be analyzed by writing the function code, for example, using an address of the interface document data as an entry parameter, and then obtaining an array of each interface in the interface document data by writing the function code in a page capture manner.

In this embodiment, an address of interface Document data is obtained, the address of the interface Document data is used as a main entry parameter, a Uniform Resource Locator (URL) of the interface Document data is obtained through the address of the interface Document data, each file on the internet has a Unique Resource Locator (URL), information included in the URL indicates a location of the file and how a browser should process the file, the interface Document data is parsed by a processing method given by the Uniform Resource Locator (URL) of the interface Document data, and a web page where the parsed interface Document data is located is converted into a Document Object Model (DOM for short), which is used to process a standard programming interface of an extensible markup language. It is a platform and language independent Application Program Interface (API) that can dynamically access programs and scripts, and style documents that update their content, structure, and www documents can be further processed, and the results of the processing can be added to the current page. Traversing a Document Object Model (DOM) according to the class and the identity of the DOM, and acquiring tags and elements located in the tags from the DOM, wherein each element located in the tags is data required by an interface; the elements within the tag are assigned to the array.

206. Assigning the array to a corresponding interface, and loading the array to a script to obtain an execution script;

in this embodiment, the arrays may be assigned to the corresponding interfaces according to the order of the interfaces in the interface document data. After the arrays are assigned to the interfaces, the arrays assigned to the interfaces can form a data packet, and the interface test tool refers to the data packet through the plug-in. The method comprises the following steps of loading arrays assigned to each interface to a script to obtain an execution script, wherein the steps of: circularly traversing the arrays assigned to the interfaces, and taking out the values assigned to the arrays; making new variable names for all the values taken out of the array; and loading the measured parameter values acquired from the interface test tool in advance into the new variable names to be used as variables to obtain the execution script.

207. Performing interface test on an interface test tool through an execution script to generate an interface automation test case;

in this embodiment, each variable in the execution script is used to create an interface automation test case through the interface test tool, so as to obtain an interface automation test case set.

208. Receiving an interface automatic test request, analyzing the interface automatic test request, and generating a corresponding interface to be tested;

209. sending the interface automation test case to an interface to be tested for testing to obtain a test result;

210. and generating a test report according to the test result, and sending the test report to a front-end page.

Steps

201, 208 and 210 in this embodiment are similar to

steps

101, 103 and 105 in the first embodiment, and are not described herein again.

Referring to fig. 3, a third embodiment of the method for automatically testing an interface according to the embodiment of the present invention includes:

301. creating a test item;

302. receiving an interface automatic test case generation instruction, and generating an interface automatic test case;

303. receiving an interface automatic test request, and analyzing the interface automatic test request to obtain corresponding to-be-tested interface information;

in this embodiment, the interface automation test request may be a message for requesting an interface automation test to be performed, where the message may include information of an interface to be tested, such as an interface name and an interface number, and identification information of an interface to be tested. And after receiving the interface automatic test request, the server extracts the information of the interface to be tested from the interface automatic test request and determines the interface to be tested.

In this embodiment, when a user needs to test a single interface on the automated testing platform, an interface automated testing request may be sent to the management server, where the interface automated testing request may generally include information of the interface that the user needs to test. After receiving the interface automatic test request, the management server can directly analyze the interface automatic test request, so as to obtain the information of the interface to be tested in the interface automatic test request.

304. Calling an initial interface in the automatic test platform, and configuring the initial interface according to the information of the interface to be tested to generate a corresponding interface to be tested;

305. Sending the interface automation test case to an interface to be tested for testing to obtain a test result;

306. and generating a test report according to the test result, and sending the test report to a front-end page.

The steps 301-.

Referring to fig. 4, a fourth embodiment of the method for automatically testing an interface according to the embodiment of the present invention includes:

401. creating a test item;

402. receiving an interface automatic test case generation instruction, and generating an interface automatic test case;

403. receiving an interface automatic test request, analyzing the interface automatic test request, and generating a corresponding interface to be tested;

404. acquiring a preset interface test template corresponding to an interface to be tested;

in this embodiment, the interface test template is a data file that records test parameters and is set corresponding to various interfaces, and may specifically be an Excel form file, an Txt text file, or an Xml (Extensible Markup Language) file, which may include but is not limited to interface test data such as an interface test serial number, an interface name, a test parameter, a verification result, an execution mode, and a variable. Different test cases can be obtained by configuring the test parameters in the interface test template. Different types of the interfaces can correspond to different test parameters, for example, for Post and Get type interfaces, the interfaces correspond to different execution modes, corresponding test parameters can be set in a targeted manner by configuring corresponding interface test templates for different interfaces, other intermediate processing is not needed, and the test efficiency is improved. After the interface to be tested is determined, a corresponding interface test template can be obtained through query according to the interface identification information such as the type, name, test serial number and the like of the interface to be tested.

405. Updating the test parameters in the interface automation test template according to the interface automation test request, and screening out a target interface automation test case corresponding to the update result from the interface automation test cases according to the update result;

in this embodiment, the interface automation test case is a test file for performing a test task on an interface, and the interface automation test case is executed to perform a related test on the interface. After the interface test template is obtained, the test parameters in the interface test template can be updated according to the test request parameters included in the interface automation test request, so that the required interface automation test case is obtained. In a specific application, the test parameters comprise interface types, execution modes, test data and verification results, the test request parameters are firstly extracted from the interface automatic test requests, various test parameters in the interface test templates are configured one by one according to the test request parameters, and after configuration is completed, corresponding interface automatic test cases are generated according to the updated test templates.

406. Calling an interface to be tested corresponding to the target interface automatic test case;

in this embodiment, the information of the interface to be tested includes, for example, the name of the interface and the serial number of the interface to be tested. And the server extracts the information of the interface to be tested corresponding to the target interface automatic test case from the parameter information corresponding to the target interface automatic test case and determines the interface to be tested.

407. Testing the interface to be tested through the target interface automatic test case to obtain an interface execution result;

in this embodiment, after the target interface automated test case corresponding to the interface automated test request is obtained, the interface to be tested is called, specifically, the interface automated test case may be executed through a TestNG test suite, an Ant script, or a Jenkins tool, the corresponding interface to be tested is called through the interface automated test case, and further, the interface to be tested is automatically tested according to the interface test, so as to obtain an interface execution result.

408. Verifying data through a preset result, and dynamically judging an interface execution result to obtain a test result of the target interface automation test case;

in this embodiment, after the interface to be tested is tested by the interface automated test case to obtain the interface execution result, the interface execution result is compared with the result verification data preset in the interface automated test request to obtain the test result. In addition, the result verification data can also be derived from the interface automation test request in advance, a corresponding result verification data set is constructed, and the interface execution result is compared with the result verification data in the result verification data set to obtain a test result.

Generally, the interface test is a functional test, and by comparing the interface execution result with the preset result verification data, it can be determined whether the interface test result meets the interface function requirement according to the comparison result. In specific application, the success rate of interface test can be counted for executing different interface automatic test cases for multiple times, and the problem of deviation of interface test results caused by abnormal interface execution results can be avoided.

409. And generating a test report according to the test result, and sending the test report to a front-end page.

The

steps

401, 403, 409 in this embodiment are similar to the

steps

101, 103, 105 in the first embodiment, and are not described herein again.

Referring to fig. 5, a fifth embodiment of the method for automatically testing an interface according to the embodiment of the present invention includes:

501. creating a test item;

502. receiving an interface automatic test case generation instruction, and generating an interface automatic test case;

503. receiving an interface automatic test request, analyzing the interface automatic test request, and generating a corresponding interface to be tested;

504. inquiring an interface code corresponding to the interface to be tested;

in this embodiment, the interface test template is preset according to different interfaces, and before the interface test is performed on the interface to be tested, the interface code corresponding to the interface to be tested is queried. The interface code is an interface code program file written by a developer, and data flow processing information, such as a data flow path, of the interface to be tested can be known by analyzing the interface code.

505. Identifying a data flow path of an interface to be tested according to the interface code;

in this embodiment, the data flow path is a branch of the interface to the data processing, which can be identified from the obtained interface code. Specifically, data flow path identification can be performed according to feature codes in the interface codes, such as IF statements commonly used in C language for judging branches. Furthermore, generally, for a program code with complex functions, a developer writes a function interpretation field corresponding to a code segment in the code, and can recognize a data flow path according to the hidden function interpretation field in the interface code.

506. Determining a corresponding path division condition according to the data flow path;

in this embodiment, after the data flow paths are determined, the path division condition of each data flow path is further determined. For example, after a judgment operation is split into 2 data flow paths, the judgment condition is a path division condition corresponding to the 2 data flow paths. By traversing and analyzing each data flow path, the path division condition of the interface to be tested can be obtained.

507. Generating test parameters according to the path division conditions, and constructing an interface test template according to the test parameters;

in this embodiment, after the path division condition is obtained, the corresponding test parameters are generated according to the path division condition, and the corresponding interface test template is constructed according to the generated test parameters. For example, for different types of interfaces such as Get type, Post type, Put type, Delete type, and the like, 4 data flow paths may be divided, that is, the interface type may be used as a test parameter. In specific application, the path division conditions may be subjected to screening processing to control the number of the path division conditions, and appropriate path division conditions are extracted from the path division conditions to generate corresponding test parameters.

In the embodiment, the test parameters are generated by inquiring the interface code of the interface to be tested, and the corresponding interface test template is constructed according to the obtained test parameters, so that the obtained interface test template is closely associated with the interface to be tested, the pertinence is strong, and the processing efficiency of automatically testing the interface of the subsequent interface automatic test case generated by the interface test template can be effectively improved.

508. Acquiring a preset interface test template corresponding to an interface to be tested;

509. updating the test parameters in the interface automation test template according to the interface automation test request, and screening out a target interface automation test case corresponding to the update result from the interface automation test cases according to the update result;

510. calling an interface to be tested corresponding to the target interface automatic test case;

511. testing the interface to be tested through the target interface automatic test case to obtain an interface execution result;

512. verifying data through a preset result, and dynamically judging an interface execution result to obtain a test result of the target interface automation test case;

513. and generating a test report according to the test result, and sending the test report to a front-end page.

Steps 501-503 and 513 in this embodiment are similar to steps 101-104 and 105 in the first embodiment, and steps 508-512 are similar to steps 404-408 in the fourth embodiment, and are not repeated here.

With reference to fig. 6, the method for automatically testing an interface according to an embodiment of the present invention is described above, and an automatic testing apparatus for an interface according to an embodiment of the present invention is described below, where a first embodiment of the automatic testing apparatus for an interface according to an embodiment of the present invention includes:

a creating module 601, configured to create a test item, where the test item includes at least one test object;

the generating module 602 is configured to receive an interface automation test case generating instruction, and generate an interface automation test case;

the analysis module 603 is configured to receive an interface automation test request, analyze the interface automation test request, and generate a corresponding to-be-tested interface;

the testing module 604 is configured to send the interface automation test case to the interface to be tested for testing, so as to obtain a testing result;

a sending module 605, configured to generate a test report according to the test result, and send the test report to a front-end page.

Referring to fig. 7, a second embodiment of an interface automatic test device according to an embodiment of the present invention specifically includes:

In this embodiment, the interface automation test apparatus further includes:

an obtaining module 606, configured to obtain all test objects included in the test item;

the execution module 607 is configured to set the test parameters of the test objects, and set the test flow corresponding to the test object according to the number of the test objects and the preset execution sequence.

In this embodiment, the generating module 602 is specifically configured to:

In this embodiment, the parsing module 603 is specifically configured to:

In this embodiment, the testing module 604 includes:

an obtaining unit 6041, configured to obtain a preset interface test template corresponding to the interface to be tested;

a screening unit 6042, configured to update the test parameters in the interface automation test template according to the interface automation test request, and screen out, from the interface automation test cases, a target interface automation test case corresponding to the update result according to the update result;

a calling unit 6043, configured to call an interface to be tested corresponding to the target interface automation test case;

a test unit 6044, configured to test the interface to be tested through the target interface automation test case to obtain an interface execution result;

and the judging unit 6045 is configured to dynamically judge the interface execution result according to preset result verification data, so as to obtain a test result of the target interface automation test case.

In this embodiment, the interface automation test apparatus further includes:

the query module 608 is configured to query an interface code corresponding to the interface to be tested;

the identification module 609 is used for identifying the data flow path of the interface to be tested according to the interface code;

a determining module 610, configured to determine a corresponding path dividing condition according to the data flow path; and the interface test template is constructed according to the test parameters.

Fig. 6 and fig. 7 describe the interface automation test apparatus in the embodiment of the present invention in detail from the perspective of the modular functional entity, and the interface automation test apparatus in the embodiment of the present invention is described in detail from the perspective of hardware processing.

Fig. 8 is a schematic structural diagram of an interface automatic test equipment according to an embodiment of the present invention, where the interface automatic test equipment 800 may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 810 (e.g., one or more processors) and a memory 820, and one or more storage media 830 (e.g., one or more mass storage devices) storing an application 833 or data 832. Memory 820 and storage medium 830 may be, among other things, transient or persistent storage. The program stored on the storage medium 830 may include one or more modules (not shown), each of which may include a series of instruction operations for the interface automation test equipment 800. Further, the processor 810 may be configured to communicate with the storage medium 830, and execute a series of instruction operations in the storage medium 830 on the interface automation test device 800 to implement the steps of the interface automation test method provided by the above-described method embodiments.

The interface automation test equipment 800 may also include one or more power supplies 840, one or more wired or wireless network interfaces 850, one or more input-output interfaces 860, and/or one or more operating systems 831, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that the interface automated test equipment configuration shown in FIG. 8 does not constitute a limitation of the interface automated test equipment provided herein and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.

The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, or a volatile computer-readable storage medium, having stored therein instructions, which, when executed on a computer, cause the computer to perform the steps of the above-mentioned interface automation test method.

The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

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; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims

1. An interface automation test method is characterized in that the interface automation test method comprises the following steps:

creating a test item, wherein the test item comprises at least one test object;

2. The method for automated testing of interfaces of claim 1, further comprising, after the creating of the test item:

acquiring all test objects contained in the test items;

3. The method according to claim 1, wherein the receiving an interface automation test case generation instruction, and generating an interface automation test case comprises:

4. The method of claim 1, wherein the receiving an interface automated test request and parsing the interface automated test request to generate a corresponding interface to be tested comprises:

5. The method for automatically testing the interface according to claim 1, wherein the sending the interface automation test case to the interface to be tested for testing to obtain the test result comprises:

6. The method for automatically testing the interface according to claim 5, further comprising, before the obtaining a preset interface test template corresponding to the interface to be tested, the steps of:

inquiring an interface code corresponding to the interface to be tested;

7. An interface automation test device, characterized in that the interface automation test device comprises:

8. The interface automation test device of claim 7 further comprising:

9. An interface automation test device, the interface automation test device comprising: a memory having instructions stored therein and at least one processor, the memory and the at least one processor interconnected by a line;

the at least one processor invoking the instructions in the memory to cause the interface automation test equipment to perform the interface automation test method of any one of claims 1-6.

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