CN115509925A - Automatic interface testing method and related device - Google Patents
Automatic interface testing method and related device Download PDFInfo
- Publication number
- CN115509925A CN115509925A CN202211214287.9A CN202211214287A CN115509925A CN 115509925 A CN115509925 A CN 115509925A CN 202211214287 A CN202211214287 A CN 202211214287A CN 115509925 A CN115509925 A CN 115509925A
- Authority
- CN
- China
- Prior art keywords
- interface
- test
- target
- ant
- script
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to an interface automatic testing method and a related device. In the embodiment of the invention, a target business service interface request is created by configuring a target interface test case to a JMeter script, and the target business service interface request is associated with the configured JMeter script; configuring an Ant construction tool, and associating the configured JMeter script with the Ant construction tool; and creating a test task by using a task planning program, calling an Ant construction file after the test task is triggered to execute interface test operation, and generating a test result, thereby realizing the automatic test of the interface. An Ant construction tool can be called every minute by utilizing a task planning program, and the requirement of lightweight minute-level monitoring is met.
Description
Technical Field
The application relates to the technical field of computers, in particular to an interface automation testing method and a related device.
Background
In the overseas game industry, more and more competitive mobile phone games are not limited to a single-machine environment without a network, but need to interact with a server to acquire server data and the like. After the game is formally released online, the server may have risks such as functional failure and high pressure, and if the risks cannot be monitored and solved in time, the game has problems in the running process, so that loss is brought.
An interface testing framework commonly used in the market at present is JMeter + Ant + Jenkins. The JMeter is used as an interface testing tool, has a packaged built-in assembly, is simple to operate, is light and convenient to operate, and has good cross-platform performance. And Ant is used as a construction tool, the test script is executed through the XML configuration file, the test result is output, and the test report is generated through the self-defined report template. Jenkins serves as a continuous integration platform to drive Ant to operate, and therefore the function of automatic interface testing is formed. However, the Jenkins platform is not lightweight, and the requirement of minute-level monitoring is difficult to meet due to the slowness of construction each time.
Disclosure of Invention
In view of the above problems, the present invention is proposed to provide an interface automation test method and related apparatus which overcome the above problems or at least partially solve the above problems.
In a first aspect, an embodiment of the present invention provides an interface automation test method, where the method includes the following steps:
configuring a target interface test case to a JMeter script, creating a target service interface request, and associating the target service interface request with the configured JMeter script;
configuring an Ant construction tool, and associating the configured JMeter script with the Ant construction tool;
and establishing a test task by using a task plan program, and calling an Ant construction file after the test task is triggered so as to execute interface test operation and generate a test result.
In one embodiment, before configuring the target interface test case-to-JMeter script, the method further includes:
configuring the running environment of the JMeter script, and creating a CSV data file for recording the target interface test case data.
In one embodiment, the creating a target business service interface request comprises:
creating a first service interface request, performing response assertion judgment on a first service interface return result, and extracting return data;
and creating a second service interface request, wherein the first service interface is a preposed interface condition of the second service interface, and responding and judging a returned result of the second service interface.
In one embodiment, before configuring the Ant building tool, the method further comprises:
and configuring the running environment of the Ant construction tool.
In one embodiment, the test task is triggered once every preset period, and the call mode of the Ant build file is hidden and unaware.
In one embodiment, the method further comprises:
and generating a link for accessing the test result, and pushing the link to the target environment.
In a second aspect, an embodiment of the present invention provides an interface automation test apparatus, where the apparatus includes:
the script configuration module is used for configuring a target interface test case to the JMeter script, creating a target service interface request and associating the target service interface request with the configured JMeter script;
the construction tool configuration module is used for configuring an Ant construction tool and associating the configured JMeter script with the configured Ant construction tool;
and the starting module is used for creating a test task by using the task planning program, calling an Ant construction file after the test task is triggered so as to execute interface test operation and generate a test result.
In an embodiment, the script configuration module is further configured to configure a running environment of the JMeter script, and create a CSV data file that records target interface test case data.
In one embodiment, the script configuration module comprises:
the first establishing sub-module is used for establishing a first service interface request, performing response assertion judgment on a first service interface return result and extracting return data;
and the second creating submodule is used for creating a second service interface request, the first service interface is a prepositive interface condition of the second service interface, and response assertion judgment is carried out on a return result of the second service interface.
In one embodiment, the build tool configuration module is further configured to configure an execution environment of an Ant build tool.
In one embodiment, the test task is triggered once every preset period, and the Ant constructed file calling mode is hidden and unaware.
In one embodiment, the apparatus further comprises:
and the pushing module is used for generating a link for accessing the test result and pushing the link to the target environment.
In a third aspect, an embodiment of the present invention provides a computer device, where the computer device includes:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the method for automated testing of interfaces of any of the first aspects.
In a fourth aspect, embodiments of the present invention provide a computer-readable storage medium.
The computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method for automated testing of an interface according to any of the first aspects.
In the embodiment of the invention, a target business service interface request is created by configuring a target interface test case to a JMeter script, and the target business service interface request is associated with the configured JMeter script; configuring an Ant construction tool, and associating the configured JMeter script with the Ant construction tool; and establishing a test task by using a task plan program, calling an Ant construction file after the test task is triggered to execute interface test operation and generate a test result, thereby realizing the automatic interface test. An Ant construction tool can be called every minute by utilizing a task planning program, and the requirement of lightweight minute-level monitoring is met.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a flowchart of an interface automation test method according to an embodiment of the present invention;
FIG. 1A is a flowchart of an interface script design based on overseas game services according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an interface automation test apparatus according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a computer device according to a third embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
In the overseas game industry, more and more competitive mobile phone games are not limited to a single-machine environment without a network, but need to interact with a server to acquire server data and the like. After the game is formally released and online, the server may have risks such as functional failure and high pressure, and if the risks cannot be monitored and solved in time, the problems occur in the running process of the game, so that loss is brought.
An interface testing framework commonly used in the market at present is JMeter + Ant + Jenkins.
Apache JMeter is a pressure testing tool developed by Apache organization based on Java, and is used for performing pressure testing on software. JMeter was originally designed for Web application testing, but later extended to other areas of testing, available for testing static and dynamic resources such as static files, java servlets, CGI scripts, java objects, databases, FTP servers, and so forth. JMeter can simulate huge loads on servers, networks or objects, test their strengths and analyze overall performance under different stress categories. Additionally, JMeter can perform a function/regression test on the application to verify if the program returns the expected result by creating a script with an assertion. The JMeter is used as an interface testing tool, has a packaged built-in assembly, is simple to operate, is light and convenient to operate, and has good cross-platform performance.
Ant is a sub-project in the apache foundation, is a cross-platform project construction tool written in java language, and requires a construction file in xml format, and the default is build. And Ant is used as a construction tool, the test script is executed through the XML configuration file, the test result is output, and the test report is generated through the self-defined report template.
Jenkins serves as a continuous integration platform to drive Ant to operate, and therefore the function of automatic interface testing is formed. However, the Jenkins platform is not lightweight, and the requirement of minute-level monitoring is difficult to meet due to the slowness of construction each time.
In order to overcome the above problems or at least partially solve the above problems, an interface automation test method according to an embodiment of the present application can implement an interface automation test, and meet the requirement of minute-level monitoring. The following examples are given for the purpose of illustration.
Example one
Fig. 1 is a flowchart of an interface automated testing method according to an embodiment of the present invention, which may be executed by an interface automated testing apparatus, where the interface automated testing apparatus may be implemented by software and/or hardware, and may be configured in a computer device, such as a server, a personal computer, or the like. The automatic interface testing method specifically comprises the following steps:
In an embodiment, the target interface test case refers to a test case required by an interface implementing automated testing. The target interface test case data can be recorded in the CSV data file, and the CSV data file is used for data driving, so that the data file can be directly modified instead of using the script file when the data configuration changes subsequently.
The target service may be a overseas game, such as an overseas market cell phone network game. The interface request can be in http request, GET mode or POST mode. The GET mode is to send a request to a specific resource (to request for specifying page information and to return to an entity body), and the POST mode is to submit data to a specified resource to process a request (to submit a form and upload a file), which may result in the establishment of a new resource or the modification of an original resource.
And 102, configuring an Ant construction tool, and associating the configured JMeter script with the Ant construction tool.
Xml (xml files with other file names can also be taken), and a plurality of targets can be defined in the xml file to construct a project. When executing the JMeter script, the Ant construction tool configures the running configuration according to the content in the build.xml, so that a JMeter script path, a test result, a test report storage path, a test report template and the like need to be configured in the content in the build.xml.
When the Ant construction tool is called, the JMeter script is transferred and executed, the interface test is executed, the test result is generated, and the corresponding test report is generated according to the template pattern.
Specifically, a task planning program (task scheduler) in the Windows operating system is used for creating a test task, the test task can be set to be triggered once per a preset period, for example, once per minute, and after being triggered, an Ant build file (built.xml) is called, and the calling mode can be hidden and unaware. When the Ant construction tool is called, the JMeter script is transferred and executed, the interface test is executed, the test result is generated, and the corresponding test report can be generated according to the template pattern.
In one embodiment, before configuring the target interface test case to JMeter script in step 101, the method further includes:
configuring the running environment of the JMeter script, and creating a CSV data file for recording the target interface test case data.
Specifically, according to an operating system, such as a Windows x64 system, a JDK installation package is selected, a JDK is installed, JDK environment variables are configured, and whether the JDK is installed successfully is verified. And decompressing a JMeter installation package after the JDK is successfully installed, and configuring JMeter environment variables.
The CSV data file is used for recording the target interface test case data, so that data driving is facilitated, and the data file can be directly modified instead of a script file when the subsequent data configuration changes. For the case where the target service is overseas gaming, particularly overseas market mobile phone network gaming, the CSV data file may record the server request domain name, product ID information, user ID information, game scene name information.
In one embodiment, in step 101, the creating a target business service interface request includes:
creating a first service interface request, performing response assertion judgment on a first service interface return result, and extracting return data;
and creating a second service interface request, wherein the first service interface is a prepositive interface condition of the second service interface, and responding to a returned result of the second service interface and judging assertion.
In a specific application, the target service is an overseas game, specifically an overseas market mobile phone network game, fig. 1A is a flowchart for designing an interface script based on an overseas game service, and creating a target service interface request includes:
and creating a 'login' interface request, namely creating a first service interface request, then extracting return data, and storing variables for subsequent interface requests. Since the login interface is a pre-interface condition of all subsequent interfaces, the assertion judgment needs to be performed on the response result of the login interface, and when the returned result is not matched with the expected assertion result, N times of failure retry operations can be performed, for example, 3 times of failure retry operations are performed, thereby avoiding the failure condition of the whole scene caused by the failure of a single interface.
Second service interface requests such as a server configuration acquisition interface request, a game starting interface request, a game ending interface request, a game data uploading interface request and the like are sequentially created, and response assertion judgment is carried out on the returned results of the interfaces, so that the specific state of each interface request is known.
And judging the result states of all response assertions so as to know whether the whole testing link has failed request conditions.
In one embodiment, before configuring the Ant building tool in step 102, the method further includes:
and configuring the running environment of the Ant construction tool.
Specifically, an Ant installation package is selected according to an operating system, files are decompressed, ant environment variables are configured, and whether configuration is successful or not is verified.
In one embodiment, the method further comprises:
and 104, generating a link for accessing the test result, and pushing the link to the target environment.
Specifically, the interface automation test result is generated and linked, and the link is pushed to a working environment in a message pushing mode through the enterprise WeChat robot, so that the related workers can monitor and solve the problem in time. When the 'interface automation test result' is fed back to the fault, the push of related handlers can be increased, and the problem is promoted to be solved in time. Of course, the link may also be pushed to the target environment by mail pushing or other suitable means, which is not limited herein.
In the embodiment, a target business service interface request is created by configuring a target interface test case to a JMeter script, and the target business service interface request is associated with the configured JMeter script; configuring an Ant construction tool, and associating the configured JMeter script with the Ant construction tool; and creating a test task by using a task planning program, calling an Ant construction file after the test task is triggered to execute interface test operation, and generating a test result, thereby realizing the automatic test of the interface. An Ant construction tool can be called every minute by utilizing a task planning program, and the requirement of lightweight minute-level monitoring is met.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those of skill in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the embodiments of the invention.
Example two
Fig. 2 is a schematic structural diagram of an interface automation test apparatus according to a second embodiment of the present invention, where the interface automation test apparatus specifically includes the following modules:
the script configuration module 201 is used for configuring a target interface test case to a JMeter script, creating a target service interface request, and associating the target service interface request with the configured JMeter script;
a construction tool configuration module 202, configured to configure an Ant construction tool, and associate the configured JMeter script with the configured Ant construction tool;
the starting module 203 is configured to create a test task by using a task plan program, and call an Ant build file after the test task is triggered, so as to execute an interface test operation and generate a test result.
In an embodiment, the script configuration module 201 is further configured to configure a running environment of the JMeter script, and create a CSV data file recording target interface test case data.
In one embodiment, the script configuration module 201 includes:
the first establishing sub-module is used for establishing a first service interface request, performing response assertion judgment on a first service interface return result and extracting return data;
and the second creating submodule is used for creating a second service interface request, the first service interface is a preposed interface condition of the second service interface, and response assertion judgment is carried out on a result returned by the second service interface.
In one embodiment, the build tool configuration module 202 is further configured to configure the runtime environment of an Ant build tool.
In one embodiment, the test task is triggered once every preset period, and the call mode of the Ant build file is hidden and unaware.
In one embodiment, the apparatus further comprises:
and the pushing module 204 is configured to generate a link for accessing the test result, and push the link to the target environment.
The interface automatic testing device provided by the embodiment of the invention can execute the interface automatic testing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a computer device according to a third embodiment of the present invention. FIG. 3 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in FIG. 3 is only an example and should not impose any limitations on the functionality or scope of use of embodiments of the present invention.
As shown in FIG. 3, computer device 12 is in the form of a general purpose computing device. The components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. Computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 3 and commonly referred to as a "hard drive"). Although not shown in FIG. 3, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement the interface automation test method provided by the embodiment of the present invention.
Example four
A fourth embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the above-mentioned interface automation test method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
A computer readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. An automated interface testing method, comprising:
configuring a target interface test case to a JMeter script, creating a target service interface request, and associating the target service interface request with the configured JMeter script;
configuring an Ant construction tool, and associating the configured JMeter script with the Ant construction tool;
and establishing a test task by using a task plan program, and calling an Ant construction file after the test task is triggered so as to execute interface test operation and generate a test result.
2. The method of claim 1, wherein prior to configuring the target interface test case-to-JMeter script, further comprising:
configuring the running environment of the JMeter script, and creating a CSV data file for recording the target interface test case data.
3. The method of claim 1, wherein the creating a target business service interface request comprises:
creating a first service interface request, performing response assertion judgment on a first service interface return result, and extracting return data;
and creating a second service interface request, wherein the first service interface is a prepositive interface condition of the second service interface, and responding to a returned result of the second service interface and judging assertion.
4. The method of claim 1, wherein prior to configuring the Ant build tool, further comprising:
and configuring the running environment of the Ant construction tool.
5. The method of claim 1, wherein: the test task is triggered once every preset period, and the call mode of the Ant constructed file is hidden and unaware.
6. The method of claim 1, further comprising:
and generating a link for accessing the test result, and pushing the link to the target environment.
7. An automated interface testing device, comprising:
the script configuration module is used for configuring a target interface test case to the JMeter script, creating a target service interface request and associating the target service interface request with the configured JMeter script;
the construction tool configuration module is used for configuring an Ant construction tool and associating the configured JMeter script with the configured Ant construction tool;
and the starting module is used for creating a test task by using the task planning program, calling an Ant construction file after the test task is triggered so as to execute interface test operation and generate a test result.
8. The apparatus of claim 7, wherein the script configuration module is further configured to configure a runtime environment of the JMeter script and create a CSV data file that records target interface test case data.
9. A computer device, characterized in that the computer device comprises:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the interface automated testing method of any of claims 1-5.
10. A computer-readable storage medium characterized by: the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the interface automation testing method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211214287.9A CN115509925A (en) | 2022-09-30 | 2022-09-30 | Automatic interface testing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211214287.9A CN115509925A (en) | 2022-09-30 | 2022-09-30 | Automatic interface testing method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115509925A true CN115509925A (en) | 2022-12-23 |
Family
ID=84508008
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211214287.9A Pending CN115509925A (en) | 2022-09-30 | 2022-09-30 | Automatic interface testing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115509925A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117251382A (en) * | 2023-11-17 | 2023-12-19 | 北京安锐卓越信息技术股份有限公司 | Automatic performance pressure measurement period execution method and device |
-
2022
- 2022-09-30 CN CN202211214287.9A patent/CN115509925A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117251382A (en) * | 2023-11-17 | 2023-12-19 | 北京安锐卓越信息技术股份有限公司 | Automatic performance pressure measurement period execution method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109271325B (en) | Application testing method, system, electronic device and storage medium | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| US9465718B2 (en) | Filter generation for load testing managed environments | |
| US9491072B2 (en) | Cloud services load testing and analysis | |
| US20070061625A1 (en) | Automation structure for software verification testing | |
| KR20210049033A (en) | Method for fault injection, device, electronic equipment and storage medium | |
| WO2015006137A1 (en) | Cloud services load testing and analysis | |
| CN110955589A (en) | Method, system, device and medium for testing headless mode based on browser | |
| US10803166B1 (en) | Automated determination of application privileges | |
| CN115658529A (en) | Automatic testing method for user page and related equipment | |
| US7783927B2 (en) | Intelligent processing tools | |
| CN111414309A (en) | Automatic test method of application program, computer equipment and storage medium | |
| US20220350689A1 (en) | Instinctive Slither Application Assessment Engine | |
| CN115509925A (en) | Automatic interface testing method and related device | |
| CN111274130A (en) | Automatic testing method, device, equipment and storage medium | |
| CN114661594A (en) | Method, apparatus, medium, and program product for automated testing | |
| CN113918864A (en) | Website page testing method, testing system, testing device, electronic equipment and medium | |
| US20140057231A1 (en) | Break-fix simulator | |
| CN113392002A (en) | Test system construction method, device, equipment and storage medium | |
| US20210294735A1 (en) | Test case failure with root cause isolation | |
| CN113014445A (en) | Operation and maintenance method, device and platform for server and electronic equipment | |
| Cai et al. | Analysis for cloud testing of web application | |
| CN115454856A (en) | Multi-application security detection method, device, medium and electronic equipment | |
| CN113986263A (en) | Code automation test method, device, electronic equipment and storage medium | |
| RU2729210C1 (en) | Electronic devices software testing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |