CN113448836A

CN113448836A - Software interface testing method and device, electronic equipment and storage medium

Info

Publication number: CN113448836A
Application number: CN202011092197.8A
Authority: CN
Inventors: 刘志
Original assignee: Soyoung Technology Beijing Co Ltd
Current assignee: Soyoung Technology Beijing Co Ltd
Priority date: 2020-10-13
Filing date: 2020-10-13
Publication date: 2021-09-28

Abstract

The application provides a software interface testing method and device, electronic equipment and a storage medium. Wherein the method comprises the following steps: the method comprises the steps of obtaining an interface call log requested by a client, generating a test case of an interface to be tested according to the interface call log, and executing the test case to test the interface to be tested. According to the technical scheme, interface self-service testing is achieved, interface information does not need to be captured through packet capturing agent software, a scene interface test case can be generated according to an interface call log of a client side, and compared with an existing interface testing method, the interface self-service testing method has the advantages that the testing process is simplified, the testing efficiency is improved, the testing difficulty is reduced, and the competitiveness of products is enhanced.

Description

Software interface testing method and device, electronic equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a software interface testing method and apparatus, an electronic device, and a storage medium.

Background

Interfaces (software-like interfaces) refer to the type of reference that defines an agreement, primarily the sub-modules or parts of the interaction and interaction between the sub-systems. An interface specifies the members that must be provided by a class or other interface that implements it. Similar to classes, interfaces may contain methods, attributes, indexers, and events as members.

The interface test is a test for testing interfaces between components of the system, and is mainly used for testing interfaces between the system and other external systems and interfaces between submodules in the system. The key points of the test are to check the correctness of the interface parameter transmission, the correctness of the interface function realization, the correctness of the output result, and the integrity and the rationality of the fault-tolerant processing of various abnormal conditions.

However, the existing interface testing method has the problems that a testing person manually operates a testing interface, so that a large amount of labor time is consumed, software defects are caused by non-ideal and objective testing judgment of human factors, personal subjectivity and the like, and the interface cannot be recorded through the packet capturing agent software due to the encryption of the interface, so that the testing cannot be performed, and the like.

Disclosure of Invention

The application provides a software interface testing method, a software interface testing device, electronic equipment and a storage medium, so as to realize self-service testing of an interface.

A first aspect of the present application provides a software interface testing method, including:

acquiring an interface call log requested by a client;

generating a test case of the interface to be tested according to the interface call log;

and executing the test case to test the interface to be tested.

In some embodiments of the present application, the generating a test case of an interface to be tested according to the interface call log includes:

filtering the interface call log to obtain interface information of the interface to be tested;

and generating a test case of the interface to be tested according to the interface information.

In some embodiments of the present application, the filtering the interface call log to obtain the interface information of the interface to be tested includes:

acquiring the equipment identification and/or the network address of the client;

and reading and matching the interface call logs line by line according to the equipment identification and/or the network address to obtain the interface information of the interface to be tested.

In some embodiments of the present application, the generating a test case of the interface to be tested according to the interface information includes:

determining a test case template;

and generating the test case of the interface to be tested according to the test case template and the interface information.

In some embodiments of the present application, the executing the test case to test the interface to be tested includes:

executing the test case at fixed time; and/or

And when the to-be-tested interface is monitored to be updated, executing the test case.

In some embodiments of the present application, the method further comprises:

and generating and outputting a test report of the interface to be tested.

In some embodiments of the present application, the interface information includes an interface request method, a request path, and a request parameter.

A second aspect of the present application provides a software interface testing apparatus, including:

the acquisition module is used for acquiring an interface call log requested by the client;

the generating module is used for generating a test case of the interface to be tested according to the interface calling log;

and the test module is used for executing the test case so as to test the interface to be tested.

A third aspect of the present application provides an electronic device comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the computer program when executing the computer program to perform the method of the first aspect of the application.

A fourth aspect of the present application provides a computer readable storage medium having computer readable instructions stored thereon which are executable by a processor to implement the method of the first aspect of the present application.

Compared with the prior art, the software interface testing method, the software interface testing device, the electronic device and the storage medium provided by the embodiment of the application obtain the interface call log requested by the client, generate the test case of the interface to be tested according to the interface call log, and execute the test case to test the interface to be tested. According to the technical scheme, interface self-service testing is achieved, interface information does not need to be captured through packet capturing agent software, a scene interface testing case can be generated according to an interface calling log of a client side, and compared with an existing interface testing method, the interface self-service testing method has the advantages that the testing process is simplified, the testing efficiency is improved, the testing difficulty is reduced, and the competitiveness of products is enhanced.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

FIG. 1 is a flow chart illustrating a software interface testing method provided by the present application;

FIG. 1a is a schematic diagram illustrating IP address query of a PC client as a client device;

fig. 1b is a schematic diagram illustrating an IP address query by a client device as a mobile phone;

fig. 1c is a schematic diagram of an acquired notify log;

FIG. 1d is a diagram illustrating a generated Jmeter use case;

FIG. 2 is a flow chart illustrating another software interface testing method provided herein;

FIG. 3 is a flow chart illustrating yet another software interface testing method provided by the present application;

fig. 4 and fig. 5 are schematic diagrams illustrating test results after a software interface provided by the present application is inspected;

FIG. 6 is a schematic diagram of a software interface testing apparatus provided herein;

FIG. 7 is a schematic diagram of another software interface testing apparatus provided herein;

FIG. 8 illustrates a schematic diagram of an electronic device provided herein;

FIG. 9 shows a schematic diagram of a computer-readable storage medium provided herein.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which this application belongs.

In addition, the terms "first" and "second", etc. are used to distinguish different objects, rather than to describe a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

The existing software interface test scheme has the following defects:

at present, whether the interface function is correct or not is tested by manual operation access in most cases, which not only consumes manpower and time, but also causes software defects due to non-ideal and objective test judgment of human factors, personal subjectivity and the like. At present, most interfaces are subjected to safe encryption processing for interface safety, interface information cannot be captured through packet capturing agent software, and therefore the interfaces cannot be tested. The manually added interface test case cannot generate a complete scenario case, and sometimes a service logic defect caused by the fact that an interface is not added exists, so that the quality of software is influenced. Part of the interface test has no test report.

In view of the above, embodiments of the present application will provide a software interface testing method, and an apparatus, an electronic device, a storage medium, and the like based on the method. In the scheme of the embodiment of the application, an interface call log of a client is obtained; generating a test case of the interface to be tested according to the interface call log; and executing the test case to test the interface to be tested. According to the technical scheme, interface self-service testing is achieved, interface information does not need to be captured through packet capturing agent software, a scene interface testing case can be generated according to an interface calling log of a client side, and compared with an existing interface testing method, the interface self-service testing method has the advantages that the testing process is simplified, the testing efficiency is improved, the testing difficulty is reduced, and the competitiveness of products is enhanced.

To further illustrate aspects of embodiments of the present application, reference is made to the following description taken in conjunction with the accompanying drawings. It is to be understood that, in the following embodiments, the same or corresponding contents may be mutually referred to, and for simplicity and convenience of description, the subsequent descriptions are not repeated.

Referring to fig. 1, a flowchart of a software interface testing method provided in some embodiments of the present application is shown, where an execution subject of the method may be a server, and specifically may be a testing server. As shown in fig. 1, the software interface testing method may include the following steps S101 to S103:

step S101: and acquiring an interface call log requested by the client.

In this step, a service logic is executed at a client such as APP or web, and the server starts to generate an interface call log of a user request or a call interface, for example, a notice log, which includes interface information such as an interface request method (corresponding information to keywords such as host, post, get), a request path (corresponding information to uri keywords), and a request parameter (for example, response time of an interface).

For example, before this step, the user may query the device identifier of the client device, or query the network address of the client device, or query the device identifier and the network address of the client device. The device identifier refers to a physical identifier (device _ id) of the client device, and the network address refers to an IP address of the client device. For example, inquiring the IP address of the client device, as shown in fig. 1a, an IP address inquiry diagram in which the client device is a PC terminal; fig. 1b is a schematic diagram illustrating an IP address query of a mobile phone terminal by a client device.

The user configures the queried IP address at the server, inputs the IP address on the front web interface, the server receives the IP address, the user starts to execute the service logic at the APP or the web, and the server starts to generate a notify log of the user request interface, such as notify log information marked by a white frame in fig. 1 c.

Step S102: and generating a test case of the interface to be tested according to the interface call log.

Step S103: and executing the test case to test the interface to be tested.

At present, for interface safety, most interfaces are subjected to safety encryption processing, interface information cannot be captured through packet capturing agent software, and therefore the interfaces cannot be tested.

In practical application, if a program runs on a server deployed by NGINX, a background server can directly read an interface call log; if the program runs on an independent server, the script can be executed by the timed task through the script which can send the interface call log to the background server so as to read the interface call log.

In this step, the interfaces to be tested may be "login", "start-up acquisition configuration", "version update", "home page interface", and the like, and the number of the interfaces to be tested may cover the actual interface to be tested, which is convenient for the subsequent overall evaluation of the software interface. In this step, a test case of the corresponding interface to be tested, for example, a "login" interface test case and a "version update" interface test case, may be generated according to the interface call log.

This step can be implemented in particular as: filtering the interface call log to obtain interface information of the interface to be tested; and generating a test case of the interface to be tested according to the interface information.

Specifically, acquiring a device identifier of the client; and reading and matching the interface calling log line by line according to the equipment identification to obtain the interface information of the interface to be tested.

Or, acquiring the network address of the client; and reading and matching the interface calling log line by line according to the network address to obtain the interface information of the interface to be detected.

Or, acquiring the device identifier and the network address of the client; and reading and matching the interface call log line by line according to the equipment identification and the network address to obtain the interface information of the interface to be detected.

Further, determining a test case template; and generating the test case of the interface to be tested according to the test case template and the interface information.

In this embodiment, the device identifier and/or the network address of the client are read and matched line by line, the user operation log of the corresponding client may be filtered from the interface call log, and interface information such as an interface request method, a request path, a request parameter, and the like may be analyzed from the user operation log to generate a scenario, that is, a script case in a corresponding order is generated according to a normal sequence of a user operation service.

For example, referring to fig. 1c, after an interface call log requested by a client and shown in fig. 1c is obtained, line-by-line matching is performed through device _ id and an IP address, the matched data is stored, and then interface information (information marked by a white box) such as uri, host, post, get and the like is analyzed from the matched data.

In this embodiment, a relevant interface testing tool is used for testing subsequently, so that a use case with a format required by the interface testing tool, such as a Jmeter use case, can be generated according to the filtered interface information, as shown in the content of the Jmeter use case shown in the white box of fig. 1 d. The Jmeter is an open source item of pure Java, and can be used for performing both interface test and performance test, and the related test processes are not described herein again.

In practical application, after a test case is generated, a test case script and a command for executing the test case can be added into a timing task, and the test case command is executed through the timing task to realize the execution of a timing trigger case; or after the test case is generated, when a tester needs to execute the test case, the script of the test case is manually operated to realize the execution of the trigger case; or after the test case is generated, the test case is automatically triggered and executed by associating the test case with the hook webhook when the corresponding interface of the Gitlab is submitted.

Compared with the prior art, the interface test method has the advantages that the interface call log of the client is obtained, the test case of the interface to be tested is generated according to the interface call log, the test case is executed, the interface to be tested is tested, the interface self-service test is realized, interface information does not need to be captured through the packet capturing agent software, and the scene interface test case can be generated according to the interface call log of the client.

Referring to fig. 2, a flow chart of another software interface testing method provided in some embodiments of the present application is shown. As shown in fig. 2, based on the foregoing embodiments, in other embodiments of the present application, the foregoing step S103 may be implemented as:

s103a, executing the test case regularly.

S103b, when the interface to be tested is monitored to be updated, executing the test case.

Of course, according to the user's needs, only the step of executing the test case at regular time may be selected, or only the step of executing the test case when it is monitored that the interface to be tested is updated may be selected, which is not limited in the present application.

In step S103a, the generated test case is added to a timing task, that is, the case is executed at a timing by setting time, so as to meet the interface inspection requirement in the actual application.

In step S103b, the update of the interface to be tested may be monitored by setting a hook webhook in the server, and when it is monitored that the interface to be tested is updated, the test case is automatically executed to perform the interface test on the updated interface to be tested.

Referring to fig. 3, a flow chart of another software interface testing method provided by some embodiments of the present application is shown. As shown in fig. 3, based on the foregoing embodiments, in other embodiments of the present application, the software interface testing method may further include:

and S104, generating and outputting a test report of the interface to be tested.

In this embodiment, steps S101 to S103 are already described in detail above, and are not described herein again.

In step S104, a test report is generated and output, and the output may be by sending the test result to the interface developer and the tester by mail.

The mail report contents are shown in fig. 4 and 5. Specifically, fig. 4 shows test environment information, and fig. 5 shows test result statistical information. The report information in the mail report content may be summarized information so that the user may look concise and clear, for example, the report information may include: the specific executor (who triggers execution of the use case), the name of the interface, the summary of the interface, the parameters of the interface, the request mode of the interface, the execution time consumption of the interface, the execution result of the interface, the success rate/failure rate of the interface, and the like.

The mail report content can help development and testing personnel to quickly know and judge the interface test result, for example, the overall quality of interface development is evaluated through the case success rate; of course, more detailed web reports can be provided, which are detailed test contents and logs, and can help development and testing personnel to know information and locate problems in detail, and further, an email report can be linked to the web report, such as "detailed test result report, please click to view here" in fig. 4.

Compared with the prior art, the interface call log of the client is acquired, the test case of the interface to be tested is generated according to the interface call log, the test case is executed to test the interface to be tested, the test report of the interface to be tested is generated and output, the interface self-service test is realized, interface information does not need to be grabbed through packet grabbing agent software, a scene interface test case can be generated according to the interface call log of the client, and a test result report of a comprehensive system is output.

In the foregoing embodiment, a software interface testing method is provided, and correspondingly, a software interface testing apparatus is also provided in the present application. Please refer to fig. 6, which illustrates a schematic diagram of another software interface testing apparatus according to some embodiments of the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for relevant points. The device embodiments described below are merely illustrative.

As shown in fig. 6, the software interface testing device 10 may include:

an obtaining module 101, configured to obtain an interface call log of a client;

the generating module 102 is configured to generate a test case of the interface to be tested according to the interface call log;

the test module 103 is configured to execute the test case to test the interface to be tested.

According to some embodiments of the present application, the generating module 102 is specifically configured to:

determining a test case template;

According to some embodiments of the present application, the test module 103 is specifically configured to:

executing the test case at fixed time; and/or

According to some embodiments of the present application, the interface information includes an interface request method, a request path, and a request parameter.

Referring to fig. 7, according to some embodiments of the present application, the apparatus 10 further includes:

and a report output module 104, configured to generate and output a test report of the interface to be tested.

Compared with the prior art, the method and the device have the advantages that the interface self-service test is realized, the interface information does not need to be captured through the packet capturing agent software, the scene interface test case can be generated according to the interface call log of the client, and meanwhile, the test result report of the comprehensive system is output.

The present application further provides an electronic device, such as a mobile phone, a notebook computer, a tablet computer, a desktop computer, etc., corresponding to the software interface testing method provided in the foregoing embodiments, so as to execute the software interface testing method.

Please refer to fig. 8, which illustrates a schematic diagram of an electronic device according to some embodiments of the present application. As shown in fig. 8, the electronic device 20 includes: the system comprises a processor 200, a memory 201, a bus 202 and a communication interface 203, wherein the processor 200, the communication interface 203 and the memory 201 are connected through the bus 202; the memory 201 stores a computer program that can be executed on the processor 200, and the processor 200 executes the software interface testing method provided by any one of the foregoing embodiments when executing the computer program.

The Memory 201 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 203 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like can be used.

Bus 202 can be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. The memory 201 is used for storing a program, and the processor 200 executes the program after receiving an execution instruction, and the software interface testing method disclosed in any embodiment of the present application may be applied to the processor 200, or implemented by the processor 200.

The processor 200 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 200. The Processor 200 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 201, and the processor 200 reads the information in the memory 201 and completes the steps of the method in combination with the hardware thereof.

The electronic device provided by the embodiment of the application and the software interface testing method provided by the embodiment of the application have the same inventive concept and have the same beneficial effects as the method adopted, operated or realized by the electronic device.

Referring to fig. 9, the computer readable storage medium is an optical disc 30, and a computer program (i.e., a program product) is stored thereon, and when being executed by a processor, the computer program executes the software interface testing method provided by any of the foregoing embodiments.

It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory, or other optical and magnetic storage media, which are not described in detail herein.

The computer-readable storage medium provided by the above-mentioned embodiment of the present application and the software interface testing method provided by the embodiment of the present application have the same beneficial effects as the method adopted, operated or implemented by the application program stored in the computer-readable storage medium.

It should be noted that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It is clear to 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.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units 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 application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should 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 or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present disclosure, and the present disclosure should be construed as being covered by the claims and the specification.

Claims

1. A software interface testing method is characterized by comprising the following steps:

acquiring an interface call log requested by a client;

and executing the test case to test the interface to be tested.

2. The method according to claim 1, wherein the generating a test case of the interface to be tested according to the interface call log comprises:

3. The method according to claim 2, wherein the filtering the interface call log to obtain the interface information of the interface to be tested comprises:

4. The method according to claim 2, wherein the generating a test case of the interface to be tested according to the interface information includes:

determining a test case template;

5. The method of claim 1, wherein the executing the test case to test the interface to be tested comprises:

executing the test case at fixed time; and/or

6. The method of claim 1, further comprising:

and generating and outputting a test report of the interface to be tested.

7. The method of any one of claims 1 to 6, wherein the interface information comprises an interface request method, a request path, and a request parameter.

8. A software interface testing apparatus, comprising:

the acquisition module is used for acquiring an interface call log of the client;

9. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor executes when executing the computer program to implement the method according to any of claims 1 to 7.

10. A computer readable storage medium having computer readable instructions stored thereon which are executable by a processor to implement the method of any one of claims 1 to 7.