WO2020019490A1

WO2020019490A1 - Interface testing method, electronic device and storage medium

Info

Publication number: WO2020019490A1
Application number: PCT/CN2018/107912
Authority: WO
Inventors: 王翼
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-07-27
Filing date: 2018-09-27
Publication date: 2020-01-30
Also published as: CN109117368A

Abstract

Disclosed in the embodiments of the present application are an interface testing method, an electronic device and a storage medium. The method comprises: determining a target interface to be tested; acquiring a target test case, and executing the target test case to test the target interface; obtaining a test report concerning the target interface; performing static scanning on the target interface definition code to obtain a scan report. The present invention is able to realize an automated test of an interface, reduce the workload of a test person, improve test efficiency, and is able to monitor potential risks of the interface as well, in detail to a code level.

Description

Interface test method, electronic equipment and storage medium

This application claims the priority of a Chinese patent application filed on July 27, 2018 with the Chinese Patent Office, with the application number 201810841915.3, and the application name being "An Interface Test Method, Electronic Equipment, and Storage Medium", the entire contents of which are incorporated by reference. In this application.

Technical field

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

Background technique

Interface test is a test for testing the interface between system components. Interface test is mainly used to detect the interaction points between external systems and systems and internal subsystems. The focus of the test is to check the exchange of data, transfer and control management Processes, and the mutual logical dependencies between systems. Due to the increasing complexity of today's systems, the cost of traditional test methods has increased dramatically and test efficiency has decreased dramatically, so interface testing is required. At present, the front-end and back-end architectures of many systems are separated. From a security perspective, relying only on the front-end to restrict the system cannot meet the system's security requirements. The back-end also needs to be controlled. In this case, interface-level verification is required.

For different interfaces, different test tools need to be used, and preparations need to be performed separately on each test tool. Testers need to manually write a large number of program cases one by one for testing. The process of writing is prone to errors, which leads to the complexity of the interface test process. Test efficiency is low.

Summary of the Invention

The embodiments of the present application provide an interface test method, an electronic device, and a storage medium.

In a first aspect, an embodiment of the present application provides an interface test method. The method includes:

Determine the target interface to be tested;

Acquiring a target test case, and executing the target test case to test the target interface;

Obtaining a test report of the target interface;

Perform a static scan on the target interface definition code to obtain a scan report.

In a second aspect, an embodiment of the present application provides an electronic device including: a determining module, a testing module, a test report generating module, and a scanning module, where:

The determining module is configured to determine a target interface to be tested;

The test module is configured to obtain a target test case and execute the target test case to test the target interface;

The test report generating module is configured to obtain a test report of the target interface;

The scanning module is configured to perform static scanning on the target interface definition code to obtain a scanning report.

According to a third aspect, an embodiment of the present application further provides an electronic device including a processor, an input device, an output device, and a memory. The processor, the input device, the output device, and the memory are connected to each other. The memory is used for A computer program is stored, where the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect and any possible implementation manner thereof.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by a processor, cause all the The processor executes the method of the first aspect and any possible implementation manners.

The embodiments of the present application can realize the automatic testing of the interface, reduce the workload of testers, improve the testing efficiency, and at the same time, monitor the potential risks of the interface down to the code level.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic flowchart of an interface test method according to an embodiment of the present application;

2 is a schematic flowchart of an interface test method according to another embodiment of the present application;

3 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of another electronic device according to an embodiment of the present application.

detailed description

In the following, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of them. Reference to "an embodiment" herein means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they separate or alternative embodiments that are mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

In order to better understand the embodiments of the present application, the method of applying the embodiments of the present application will be described below.

The electronic devices mentioned in the embodiments of the present application may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices (such as smart watches, smart bracelets, pedometers, etc.), computing devices, or connected to a wireless modem Other processing equipment, as well as various forms of user equipment (User Equipment, UE), mobile station (Mobile Station, MS), terminal equipment (terminal device), and so on. For ease of description, the devices mentioned above are collectively referred to as electronic devices.

Please refer to FIG. 1, which is a schematic flowchart of an interface test method according to an embodiment of the present application. The method may be applied to an electronic device. As shown in FIG. 1, the method may include:

101. Determine a target interface to be tested.

Before testing, you need to determine the interface to be tested. You can add the interface to the test platform of the electronic device. When a test instruction is detected, determine that the interface targeted by the test instruction is the target interface to be tested; or,

When the parameter change of the interface where the parameter change is detected meets the test conditions, it is determined that the interface whose parameter is changed is the target interface to be tested

Specifically, the selection and determination of the target interface may be manually set, that is, first, a tester may set one or more interfaces on an interface test platform on an electronic device, and select an interface to be tested among these interfaces. The target interface can automatically start the execution of the test function; testers can also set the execution method, including: setting the test execution time, that is, the platform can immediately start executing the test task, or automatically execute the target interface at the set test execution time Test; set the background execution, set the number of test cycles and so on.

The selection and determination of the target interface for performing the test in this step can also be automatic. The platform can store the above test conditions. The platform has a detection function. When a preset change condition is detected, the test can be triggered, such as detecting the interface. The parameters change and the parameter changes meet the preset test conditions. The platform for executing the interface test method in this application can be understood as an automation environment. The code warehouse where the interface is placed can be connected to the automation environment. The code for the interface test can be placed in the code warehouse (an open source version control system), such as git or svn, then submit, that is, the tester chooses to enable monitoring, and the platform can periodically detect whether the code warehouse has changed to trigger the test of the interface.

After the target interface is determined, step 102 may be performed.

102. Obtain a target test case and execute the target test case to test the target interface.

The above test cases can be written by developers based on actual projects. Each project needs to use the interface test cases that match it. Test cases can be provided to testers on the platform. Test cases can be set to popular expressions. , Such as modifying the naming or annotating, categorizing, etc., for testers to choose.

Specifically, the platform can also run the selected interface test case according to the selected execution method. For example, the tester sets the test execution time, and the platform can execute the target interface test at the set test execution time. Set the number of test cycles to be performed in the background or to follow the test.

The request parameters of the test case can be set according to the normal input parameter format of the interface. If multiple test case parameters of an interface need to achieve data separation, it can be achieved by unifying the data format in the specified file, which can be stored in the form of a data format table (such as what parameters are represented in the first column of the table, and the second column What parameters represent, etc.).

Optionally, test cases for interfaces can be added or deleted. Users can add new interface test cases as needed. If you need to add new interface test cases, you only need to add new interface test cases to the interface test case project and upload them, and delete similar ones.

Optionally, before using the target test case to test the target interface, the method further includes: obtaining test configuration parameters of the target interface.

Before the interface test runs, the tester can configure the test configuration parameters of the target interface. The test configuration parameters may include: system domain name and / or port, http implementation version and protocol type, input parameters, and response.

In essence, any website is accessed through the combination of the server's IP (xxx.xxx.xxx) and port number (xx). Because the server's IP number is too difficult to remember and is not visual, the term "domain name" appears. The meaning of a domain name is to represent a server IP address in the form of a string such as xxx.xxx.xx. In essence, they use mapping binding resolution to handle this. Domain names need to be specially registered and registered, and they must not conflict. In the embodiment of the present application, a domain name is used for setting, which is convenient for testers to manage.

A port can be considered as an outlet for communication between the device and the outside world. Ports can be divided into virtual ports and physical ports. What is referred to in this application are virtual ports, that is, ports inside a computer or a switch router, which are not visible. For example, 80 ports, 21 ports, 23 ports, etc. in the computer. The Domain Name System (DNS) is used to name computers and network services that are organized into a domain hierarchy. DNS port number is an abbreviation of port number. There is a one-to-one correspondence between domain names and IP addresses on the Internet. Although domain names are easy for people to remember, machines can only recognize each other's IP addresses. The conversion between them is called the domain name. Resolution, domain name resolution needs to be completed by a dedicated domain name resolution server.

Interface testing can include input parameter testing: testing the input parameters, or testing that assumes the incorrectness of the interface parameters, ensuring that the interface handles any type of input accordingly: input parameters are valid, input parameters Illegal, the input parameter is empty, the input parameter is null, and the input parameter is too long; therefore, you need to set the input parameter and the corresponding response to determine whether the interface is operating correctly.

After obtaining the test configuration parameters, the target interface can be tested using the target test case according to the test configuration parameters.

There can be multiple test cases for an interface, and some or all of the test cases stored in the platform can be selected for execution. The platform can also select appropriate test cases, such as prompting the user to choose a used test solution, that is, the tester can Set a shortcut to save the configured interface test configuration parameters and test cases. After this test is completed, you can use the historical test scheme with a one-click setting method, which simplifies the test operation steps.

103. Obtain a test report of the target interface.

After the interface test is completed, a test report can be generated, and the output report can be sent to the relevant responsible persons on a regular basis. The corresponding contact information of the responsible person (email address, or the corresponding user account of the platform can be set on the platform. Users can use the terminal Log in to the user account and receive push messages). The test report can be displayed in a graphical interface to clearly and intuitively find problems. For example, the test report can be displayed as a list of interface test conditions, which shows whether each interface has passed, and whether there are problems.

104. Perform static scanning on the target interface definition code to obtain a scanning report.

The target interface definition code is used to describe the target interface. Static scanning refers to static source code scanning. It is one of the software application security solutions that have been mentioned in recent years. It means that in software engineering, programmers do not need to compile after compiling the source code. Scan it directly with some scanning tools to find solutions to some semantic defects and security vulnerabilities in the code.

There are two general types of static scanning:

(1) Pattern matching: Match token flow, abstract syntax tree (AST) and intermediate code during code compilation. According to experience, it is recognized that certain styles of code are vulnerabilities.

(2) Data flow analysis: Based on the control flow graph (CFG), the data flow analysis technology scans each instruction of the control flow graph in a certain way in an attempt to understand the behavior of the instruction to determine the loopholes in the program.

The static scanning mainly involved in this application is implemented by means of pattern matching, which can include lexical analysis, syntax analysis, and intermediate code analysis, as follows:

The lexical analysis phase is the first phase of the compilation process and is the basis of compilation. The task of this stage is to read the source program one character from left to right, that is, to scan the character stream that constitutes the source program and then recognize words (also known as word symbols or symbols) according to the word formation rules, that is, you can scan and identify Words are given qualitative and fixed-length processing. You can use the static code scanning tool Cppcheck to use lexical analysis for code scanning. It supports C and C ++ code. It mainly matches token streams. It does not need to be compiled during scanning, and the execution speed is fast.

Grammar analysis is a logical stage of the compilation process. The main task is to combine word sequences into various types of grammatical phrases, such as programs, statements, expressions, and so on, based on lexical analysis. A parser determines whether the program is structurally correct. You can use the code error analysis tool PMD of JAVA code to scan using syntax analysis. PMD can scan folders and find ".java" files under the folder for analysis. The main principle is to match abstract syntax trees.

Intermediate code is where the writer hopes to generate an intermediate identification form closer to the target code from the syntax tree, or use such an intermediate representation instead of the syntax tree, and then execute this new intermediate representation to generate the target code. The intermediate code serves as a bridge between the front-end and the back-end of the compiler. The function of the intermediate code is to make the structure of the compiler more logical and simple. In particular, it makes the optimization of the target code easier to implement the intermediate code, that is, the intermediate language program. The complexity of the intermediate language lies between the source language and the machine language. You can use the open source analysis tool findbugs to analyze Java code errors. The analysis object of findbugs is java intermediate code-bytecode. Therefore, in the process of using the command line to call the tool, you need to pass in the compiled class file or jar package.

Through static scanning, the tester only needs to receive the scanning report of the static scanning to obtain the code-level risks and problems. Pre-testing can shorten the test cycle and minimize the code risk.

Step 103 in the embodiment of the present application may be performed simultaneously during the execution of step 102 to increase the speed of the entire interface test, obtain corresponding test reports and scan reports, and display the results to the user.

In the embodiment of the present application, after the target interface to be tested is determined, a target test case is obtained, the target interface is tested using the target test case, a test report of the target interface is obtained, and a static scan is performed on the target interface definition code to obtain a scan report. Realize automated testing of interfaces, reduce the workload of testers, improve testing efficiency, and monitor the potential risks of interface details down to the code level.

Referring to FIG. 2, which is a schematic flowchart of another interface test method provided by an embodiment of the present application. The embodiment shown in FIG. 2 may be obtained based on the embodiment shown in FIG. 1, as shown in FIG. 2. The method may include:

201. Determine a target interface to be tested.

For the foregoing step 201, reference may be made to the detailed description in step 101 of the embodiment shown in FIG. 1, and details are not described herein again.

202. Obtain a test execution time of the target interface, and obtain a target test case.

Specifically, the tester can set the test execution time of the interface (for example, after 2 hours, 14:00 on the day, or immediately), and after obtaining the test execution time of the target interface, step 203 can be performed; optionally, the tester You can also set the target interface's test cycle (such as 1 hour). After obtaining the test execution time and test cycle of the target interface, you can use the target test case to test the target interface every time from the test execution time. Record the test results in a test report. Optionally, the tester can also set the number of test cycles for the interface test (for example, 3 times). After obtaining the above number of test cycles, the test can be performed according to the set number of test cycles. That is, the target test case can be run according to the execution mode selected by the user, which improves the test flexibility and test efficiency.

203. Execute the target test case at the test execution time to test the target interface.

204. Obtain a test report of the target interface.

For the above steps of using the target test case to test the target interface and obtaining a test report of the target interface, reference may be made to specific descriptions in

steps

102 and 103 of the embodiment shown in FIG. 1, and details are not described herein again.

205: Perform a static scan on the target interface definition code to obtain a scan report.

For the foregoing step 204, reference may be made to the detailed description in step 104 of the embodiment shown in FIG. 1, and details are not described herein again.

206. Perform a code coverage test on the target interface and the target test case to obtain code coverage.

At the same time or after the static scan, the coverage of the target test cases and target interfaces can also be detected, which can be reflected in what code is not covered after the test case is executed.

Code coverage can be injected into the bytecode file through a probe according to a certain injection strategy. Through dynamic instrumentation, coverage data is generated in the JVM virtual machine, stored in memory, and the coverage data is dumped through a port. Form a report locally.

Optionally, the target interface definition code specification can also be detected. Code specification problems can use various rules of checkstyle to scan the code to get code specification reports.

Through the detection of the above code coverage and code specifications, you can understand the problems at the code layer in detail, so as to add or change test cases to improve the test task, and further ensure the quality of the interface test. The above indicators can still be reflected in the above scan report.

207. Obtain a first email address for receiving the test report and a second email address for receiving the scan report.

The user can set a first email address for receiving the test report in advance, so that it can be sent to the first email address after generating the test report, and the user can set a second email address for receiving the scan report in advance, so that After the test report is generated, it can be sent to the second email address. After the test report and the scan report are obtained, step 206 may be performed. The first email address and the second email address may be the same or different, that is, the test report and the scan report may be sent to different persons in charge, or they may be integrated and sent together.

208. Send a first email including the test report content to the first email address, and send a second email including the scan report content to the second email address.

Optionally, the above email can be sent at a preset time, that is, the email sending time can be set, and the above email including the test report and the email including the scan report can be sent to the user regularly. The user can receive and view the interface test status at the preset time. .

In the embodiment of the present application, the target execution time of the target interface is obtained, the target test case is obtained, the target test case is executed at the test execution time to test the target interface, the test report of the target interface is obtained, and the code of the target interface is defined. Perform a static scan to obtain a scan report, perform a code coverage test on the target interface and the target test case, obtain a code coverage, obtain a first email address for receiving the test report, and a second email address for receiving the scan report. An email address, sending a first email containing the test report content to the first email address, and sending a second email containing the scan report content to the second email address, which can implement automated testing of the interface and facilitate regular reception by testers Viewing the test report by email reduces the workload of the tester and improves the testing efficiency. At the same time, the potential risks of the interface detail to the code level can be monitored.

Please refer to FIG. 3. FIG. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device 300 includes a determining module 310, a testing module 320, a test report generating module 330, and a scanning module 340, where:

The determining module 310 is configured to determine a target interface to be tested;

The test module 320 is configured to obtain a target test case and execute the target test case to test the target interface;

The test report generating module 330 is configured to obtain a test report of the target interface;

The scanning module 340 is configured to perform static scanning on the target interface definition code to obtain a scanning report.

As a possible implementation manner, the above-mentioned electronic device 300 further includes a configuration module 350 for acquiring a test configuration parameter of the target interface;

The test module 320 is specifically configured to execute the target test case to test the target interface according to the test configuration parameters.

As a possible implementation manner, the electronic device 300 further includes:

A coverage test module 360 is configured to perform a code coverage test on the target interface and the target test case to obtain a code coverage rate when the target interface is tested using the target test case.

As a possible implementation manner, the configuration module 350 is further configured to obtain a test execution time of the target interface;

The test module 320 is specifically configured to execute the target test case at the test execution time to test the target interface.

As a possible implementation manner, the configuration module 350 is further configured to obtain a test period of the target interface;

The test module 320 is specifically configured to execute the target test case every test period to test the target interface from the test execution time.

As a possible implementation manner, the foregoing electronic device 300 further includes:

The mail sending module 370 is configured to obtain a first mail address used to receive the test report and a second mail address used to receive the scan report, and to send the test report to the first mail address including the test report. A first mail of the content, and a second mail including the content of the scan report is sent to the second mail address.

As a possible implementation manner, the foregoing determining module 310 is specifically configured to determine that an interface targeted by the test instruction is a target interface to be tested when a test instruction of the user against the interface is detected; or,

When the parameter change of the interface where the parameter change is detected meets the test conditions, it is determined that the interface where the parameter change is the target interface to be tested.

According to the specific implementation of the embodiment of the present application, steps 101 to 104 and 201 to 207 related to the interface test method shown in FIG. 1 and FIG. 2 may be performed by each module in the electronic device 300 shown in FIG. 3. For example, steps 101 to 104 in FIG. 1 may be performed by the determination module 310, the test module 320, the test report generation module 330, and the scan module 340 shown in FIG. 3, respectively.

Through the electronic device 300 in the embodiment of the present application, the electronic device 300 can determine a target interface to be tested, obtain a target test case, execute the target test case to test the target interface, obtain a test report of the target interface, and perform a test on the target interface. Defining code for static scanning and obtaining scanning reports can realize automatic testing of the interface, reduce the workload of testers, improve testing efficiency, and monitor the potential risks of the interface down to the code level.

Please refer to FIG. 4, which is a schematic structural diagram of another electronic device disclosed in an embodiment of the present application. As shown in FIG. 4, the electronic device 400 includes a processor 401 and a memory 402. The electronic device 400 may further include a bus 403. The processor 401 and the memory 402 may be connected to each other through the bus 403. The bus 403 may be a peripheral component and each other. Connects to a standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industrial Architecture (EISA) bus). The bus 403 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 4, but it does not mean that there is only one bus or one type of bus. The electronic device 400 may further include an input-output device 404, and the input-output device 404 may include a display screen, such as a liquid crystal display screen. The memory 402 is configured to store one or more programs containing instructions; the processor 401 is configured to call the instructions stored in the memory 402 to execute some or all of the method steps mentioned in the embodiments of FIG. 1 and FIG. 2.

It should be understood that, in the embodiment of the present application, the processor 401 may be a central processing unit (CPU), and the processor may also be another general-purpose processor or a digital signal processor (DSP). , Application specific integrated circuit (ASIC), ready-made programmable gate array (Field-Programmable GateArray, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The input device 402 may include a touch panel, a fingerprint sensor (for collecting fingerprint information and orientation information of a user), a microphone, and the like, and the output device 403 may include a display (LCD, etc.), a speaker, and the like.

The memory 404 may include a read-only memory and a random access memory, and provide instructions and data to the processor 401. A portion of the memory 404 may also include non-volatile random access memory. For example, the memory 404 may also store device type information.

Through the electronic device 400 in the embodiment of the present application, the electronic device 400 can determine a target interface to be tested, obtain a target test case, execute the target test case to test the target interface, obtain a test report of the target interface, and perform a test on the target interface. Defining code for static scanning and obtaining scanning reports can realize automatic testing of the interface, reduce the workload of testers, improve testing efficiency, and monitor the potential risks of the interface down to the code level.

An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, and the computer program causes a computer to execute any one of the interfaces described in the foregoing method embodiments. Some or all steps of the test method.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not described in detail in one embodiment, reference may be made to related descriptions in other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or may be combined. Integration into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or modules, and may be electrical or other forms.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the objective of the solution of this embodiment.

When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of the present application essentially or part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory, Several instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The foregoing memory includes: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk, and other media that can store program codes.

Claims

An interface testing method, characterized in that the method includes:

Determine the target interface to be tested;

Acquiring a target test case, and executing the target test case to test the target interface;

Obtaining a test report of the target interface;

Perform a static scan on the target interface definition code to obtain a scan report.
The method according to claim 1, wherein the static scanning of the target interface definition code comprises lexical analysis, syntax analysis, and / or intermediate code analysis of the target interface definition code.
The method according to claim 2, wherein before the executing the target test case to test the target interface, the method further comprises:

Obtaining test configuration parameters of the target interface;

The executing the target test case to test the target interface includes:

And execute the target test case to test the target interface according to the test configuration parameters.
The method according to claim 3, wherein the content of the scan report includes code coverage, and the method further comprises:

Perform a code coverage test on the target interface and the target test case to obtain the code coverage.
The method according to claim 4, further comprising:

Obtaining a test execution time of the target interface;

The executing the target test case to test the target interface includes executing the target test case at the test execution time to test the target interface.
The method according to claim 5, further comprising:

Obtaining a test period of the target interface;

The executing the target test case to test the target interface at the test execution time includes:

From the test execution time, the target test case is executed every test cycle to test the target interface.
The method according to claim 4, further comprising:

Obtaining the number of test cycles of the target interface;

The executing the target test case to test the target interface includes executing the target test case in accordance with the number of test cycles to test the target interface.
The method according to claim 7, further comprising:

Obtaining a first email address for receiving the test report and a second email address for receiving the scan report;

Send a first mail containing the test report content to the first mail address, and send a second mail containing the scan report content to the second mail address.
The method according to any one of claims 1-8, wherein performing the determining the target interface to be tested on the target interface definition code comprises:

When a test instruction is detected, determining that the interface targeted by the test instruction is a target interface to be tested; or

When the parameter change of the interface where the parameter change is detected meets the test conditions, it is determined that the interface where the parameter change is the target interface to be tested.
An electronic device, comprising: a determining module, a testing module, a test report generating module, and a scanning module, wherein:

The determining module is configured to determine a target interface to be tested;

The test module is configured to obtain a target test case and execute the target test case to test the target interface;

The test report generating module is configured to obtain a test report of the target interface;

The scanning module is configured to perform static scanning on the target interface definition code to obtain a scanning report.
The electronic device according to claim 10, wherein the scanning module is specifically configured to perform lexical analysis, syntax analysis, and / or intermediate code analysis on the target interface definition code.
The electronic device according to claim 11, further comprising a configuration module for acquiring a test configuration parameter of the target interface;

The test module is specifically configured to execute the target test case to test the target interface according to the test configuration parameters.
The electronic device according to claim 12, further comprising a coverage test module for performing a code coverage test on the target interface and the target test case to obtain a code coverage.
The electronic device according to claim 13, wherein the configuration module is further configured to obtain a test execution time of the target interface;

The test module is specifically configured to execute the target test case at the test execution time to test the target interface.
The electronic device according to claim 14, wherein the configuration module is further configured to obtain a test cycle of the target interface;

The test module is specifically configured to execute the target test case every test period to test the target interface from the test execution time.
The electronic device according to claim 13, wherein the configuration module is further configured to obtain the number of test cycles of the target interface;

The test module is specifically configured to execute the target test case according to the number of test cycles to test the target interface.
The electronic device according to claim 16, further comprising a mail sending module, configured to:

Obtaining a first email address for receiving the test report and a second email address for receiving the scan report;

Send a first mail containing the test report content to the first mail address, and send a second mail containing the scan report content to the second mail address.
The electronic device according to any one of claims 10 to 17, wherein the determining module is specifically configured to:

When a test instruction is detected, determining that the interface targeted by the test instruction is a target interface to be tested; or

When the parameter change of the interface where the parameter change is detected meets the test conditions, it is determined that the interface where the parameter change is the target interface to be tested.
An electronic device is characterized by comprising a processor, an input device, an output device, and a memory, and the processor, the input device, the output device, and the memory are mutually connected, wherein the memory is used to store a computer program, and the computer The program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1-9.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes A method according to any one of 1-9 is required.