CN114328189A - Fault recurrence method, device, terminal and computer readable storage medium - Google Patents
Fault recurrence method, device, terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN114328189A CN114328189A CN202111506353.5A CN202111506353A CN114328189A CN 114328189 A CN114328189 A CN 114328189A CN 202111506353 A CN202111506353 A CN 202111506353A CN 114328189 A CN114328189 A CN 114328189A
- Authority
- CN
- China
- Prior art keywords
- test
- fault
- log
- case
- test case
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application provides a fault recurrence method, a fault recurrence device, a terminal and a computer readable storage medium, relates to the field of fault detection, and the method is applied to the terminal. Firstly, the terminal generates a corresponding test case according to the operation steps, then runs the test case to generate a test log, displays the test log on the terminal so that a user can verify the correctness of the test log, adds a preset positioning identifier to the test case under the condition that the user verifies that the test log is correct, further obtains an identification case, runs the identification case on the terminal, and generates and sends a fault log when a fault occurs. The identification case is obtained by adding the positioning identifier in the test case, and the identification case is continuously operated to find out the accidental faults in the program, so that the accidental faults can be quickly reproduced, the difficulty in the accidental fault repairing process is reduced, and the time cost is effectively saved.
Description
Technical Field
The present application relates to the field of fault detection, and in particular, to a fault recurrence method, apparatus, terminal, and computer-readable storage medium.
Background
With the continuous development of information technology, more and more applications are installed in a terminal, and faults occur in the running and developing processes of the applications, most of the faults can be reproduced, but some faults occur occasionally or are difficult to reproduce, and the faults are called occasional faults. Even if the even fault occurs again, the problem is difficult to attach, and the even fault exists in the application program.
In order to find out the reason of the occurrence of the accidental fault, a tester only needs to continuously test to obtain corresponding test steps, and the accidental fault is difficult to quickly reproduce after the occurrence of the accidental fault, so that for the tester and research personnel, difficulty is increased in the process of reproducing and repairing the accidental fault, and a large amount of time is consumed. Therefore, how to reproduce the occasional failure of the application program becomes a technical problem to be solved urgently.
Disclosure of Invention
In order to overcome the above defects in the prior art, embodiments of the present application provide a fault recurrence method, apparatus, terminal, and computer-readable storage medium, which can achieve the purpose of recurrence of an even fault of an application program.
In order to achieve the above purpose, the embodiments of the present application employ the following technical solutions:
in a first aspect, an embodiment of the present application provides a fault recurrence method, which is applied to a terminal, and the method includes:
generating a corresponding test case according to operation steps, wherein the operation steps are determined in advance according to external feedback or functional test;
running the test case to generate a test log, and displaying the test log on a terminal so that a user can verify the correctness of the test log;
under the condition that the test log is correct, adding a preset positioning identifier into the test case to obtain an identification case;
and running the identification use case, and generating and sending a fault log when the identification use case fails.
Further, before generating the corresponding test case according to the operation steps, the method further includes:
acquiring system information input by a user;
and logging in a corresponding system to be tested according to the system information, wherein the system to be tested corresponds to the test case.
Further, the operation steps include an operation type, a positioning method and an operation mode, and the step of generating the corresponding test case according to the operation steps includes:
generating a test case script according to the operation type, the positioning method and the operation mode;
and running the test case script to obtain the test case.
Further, the method further comprises:
and sending the test log if the test log is wrong.
In a second aspect, an embodiment of the present application further provides a fault recurrence device, which is applied to a terminal, and the device includes:
the generating module is used for generating a corresponding test case according to operation steps, and the operation steps are determined in advance according to external feedback or functional test;
the operation module is used for operating the test case to generate a test log and displaying the test log on a terminal so that a user can verify the correctness of the test log;
the adding module is used for adding a preset positioning identifier to the test case to obtain an identification case under the condition that the test log is correct;
and the operation module is also used for operating the identification use case, and generating and sending a fault log when the identification use case fails.
Further, the apparatus further comprises:
the acquisition module is used for acquiring system information input by a user;
and the login module is used for logging in a corresponding system to be tested according to the system information, and the system to be tested corresponds to the test case.
Further, the operation steps include operation type, positioning method and operation mode, and the generation module includes:
the generating submodule is used for generating a test case script according to the operation type, the positioning method and the operation mode;
and the operation sub-module is used for operating the test case script to obtain the test case.
Further, the apparatus further comprises:
and the sending module is used for sending the test log under the condition that the test log is wrong.
In a third aspect, an embodiment of the present application further provides a terminal, including: a processor, a memory and a bus, the memory storing program instructions executable by the processor, the processor and the memory communicating via the bus when the client is running, the processor executing the program instructions to perform the fault recurrence method according to any one of the first aspect.
In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the fault recurrence method according to any one of the first aspects.
The application provides a fault recurrence method, a fault recurrence device, a terminal and a computer readable storage medium, which are applied to the terminal. Firstly, the terminal generates a corresponding test case according to the operation steps, then runs the test case to generate a test log, displays the test log on the terminal so that a user can verify the correctness of the test log, adds a preset positioning identifier to the test case under the condition that the user verifies that the test log is correct, further obtains an identification case, runs the identification case on the terminal, and generates and sends a fault log when a fault occurs. The identification case is obtained by adding the positioning identifier in the test case, and the identification case is continuously operated to find out the accidental faults in the program, so that the accidental faults can be quickly reproduced, the difficulty in the accidental fault repairing process is reduced, and the time cost is effectively saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 shows a flowchart of a fault recurrence method provided in an embodiment of the present application.
Fig. 2 shows another flow chart of the fault recurrence method provided in the embodiment of the present application.
Fig. 3 shows a schematic flowchart of step S130 in the fault recurrence method provided in the embodiment of the present application.
FIG. 4 shows a test case script generation diagram provided in an embodiment of the present application.
Fig. 5 shows a schematic structural diagram of a fault replication device provided in an embodiment of the present application.
Fig. 6 shows a schematic structural diagram of a terminal provided in an embodiment of the present application.
Icon: 100-fault recurrence device; 110-a generation module; 120-add module; 130-running module; 11-a processor; 12-a memory; 13-bus.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
In the process of running and developing the application program, because of the complicated running environment, some faults may occur during the running of the application program, and the faults are not caused by the application program itself and have certain contingencies, and the faults are called occasional faults. Even faults do not have any rule to be found, so that testers and developers can hardly find the problem, but even faults exist in the application program all the time.
In order to find out the reason of the occurrence of the accidental fault, only through continuous testing, since the accidental fault is difficult to reproduce quickly after the accidental fault occurs, for a tester and a research and development personnel, the difficulty is increased in the process of reproducing and repairing the accidental fault, and a large amount of time is consumed. Therefore, how to quickly reproduce the occasional faults in the application program becomes a technical problem to be solved urgently by technical personnel.
In view of the above technical problems, embodiments of the present application provide a fault recurrence method, which can rapidly recur an even fault when the even fault occurs, reduce difficulty in repairing the even fault, and improve efficiency of a tester in repairing the even fault, which is described in detail below.
First, the terminal applied to the fault recurrence method in the present application may be implemented in various forms, for example, it may be a fixed terminal such as a Digital TV, a desktop computer, etc., or it may also be a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palm top computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, etc.
Referring to fig. 1, fig. 1 shows a schematic flow chart of a fault recurrence method provided in an embodiment of the present application, where the fault recurrence method is applied in a terminal, and includes the following steps S130 to S160:
and S130, generating a corresponding test case according to the operation steps, wherein the operation steps are determined in advance according to external feedback or functional test.
The operation steps can be determined according to external feedback, for example, when the electronic equipment of the user generates the occasional faults when running the application program, the feedback information is sent to indicate that the occasional faults occur, and the operation steps can also be determined through functional testing, for example, when testing the application program, a tester writes and runs a functional test case so as to actively find the occasional faults.
It should be noted that the functional test is an important aspect in the software test, and is to verify each function of the software product and test whether the function of the software product meets the function required by the user item by item according to the functional test case. Functional test cases are a set of test inputs, execution conditions, and expected results tailored for a particular purpose in order to test whether a function meets requirements. Generally, the functional test case is a login functional test case for testing inside a single page, for example, after inputting a user name and a password into a login box in one page, clicking a login button to verify whether the login is successful.
The terminal generates a corresponding test case according to the operation steps, and the operation steps may include the functional test case. In a possible implementation manner, the terminal may store the test case in the database in advance, set the test case and the operation step as a corresponding relationship, and generate the test case when the terminal obtains the operation step.
And S140, running the test case to generate a test log, and displaying the test log on the terminal so that the user can verify the correctness of the test log.
After the test case is generated, the terminal runs the test case to generate a test log, and displays the test log to a user, so that the user can check whether the test log is correct, and can find an emerging defect only under the condition that the test log is correct, so that the correctness of the test log needs to be verified once, and the test log correctly executes the step S150.
S150, under the condition that the test log is correct, adding a preset positioning identifier to the test case to obtain an identification case.
And S160, running the identification use case, and generating and sending a fault log when the identification use case fails.
The location identifier is used to locate a field in which an occasional defect may occur, and the field may be a keyword, a sentence, or a text, which is not limited in this application. When the identification case with the positioning identifier is operated, only the field positioned by the judgment identifier is used, and all fields in the test case are not required to be judged, so that the workload of the terminal is reduced.
After the user verifies that the test log is correct, the terminal sets the positioning identifier in the test case to generate an identification case, then starts a cycle test to repeatedly run the identification case, when an even fault occurs in the cycle test process, the cycle test is immediately stopped and a corresponding fault log is generated, and the fault log can be sent to a designated mailbox through a mail to indicate that the even fault has been found out. The fault log provides effective help for the follow-up analysis of the cause of the emerging defect, and the time for discovering the emerging defect is shortened.
In a possible implementation manner, the manner of judging that the fault occurs in the operation process of the identification use case may be that a corresponding log is generated by operating the identification use case once, then a corresponding log is generated by operating the identification use case once, the previous log and the next log are compared, if the previous log and the next log are different, the fault occurs, and if the previous log and the next log are the same, the above steps are continuously circulated until the fault occurs.
According to the method and the device, the corresponding test case is generated according to the operation steps, then the test case is operated to generate the test log, the test log is displayed on the terminal, so that a user can verify the correctness of the test log, the preset positioning identifier is added to the test case under the condition that the user verifies that the test log is correct, then the identification case is obtained, the terminal operates the identification case, and when a fault occurs, the fault log is generated and sent. The identification case is obtained by adding the positioning identifier in the test case, and the identification case is continuously operated to find out the accidental faults in the program, so that the accidental faults can be quickly reproduced, the difficulty in the accidental fault repairing process is reduced, and the time cost is effectively saved.
In order to find a system under test for executing a test case, with reference to fig. 2 on the basis of fig. 1, fig. 2 shows another schematic flow chart of the fault recurrence method provided in the embodiment of the present application, as shown in the figure, before step S130, the method further includes:
and S110, acquiring system information input by a user.
And S120, logging in a corresponding system to be tested according to the system information, wherein the system to be tested corresponds to the test case.
The system information is a web access address of the system to be tested, and may be an ip address or a domain name address. After the user inputs the web access address at the terminal, the terminal logs in the corresponding system to be tested according to the access address, and the test case is operated in the system to be tested.
Furthermore, according to the corresponding relation between the system to be tested and the test case, the multiple systems can be tested simultaneously to reproduce the double faults, so that the time for reproducing the double faults is greatly shortened, and the working efficiency of testers is improved.
Next, step S130 is described in detail, with reference to fig. 3 on the basis of fig. 1, fig. 3 shows a schematic flow chart of step S130 in the fault recurrence method provided in the embodiment of the present application, and step S130 includes:
s131, generating a test case script according to the operation type, the positioning method and the operation mode.
And S132, running the test case script to obtain the test case.
The operation steps comprise operation types, positioning methods, operation modes and the like, wherein the operation types are types which need to be actually executed by a user and comprise positioning elements, executing js statements, opening or closing windows and the like, the positioning method is used for positioning view elements through attribute values of front end elements, the attributes of the front end elements can be class, id, name, xpath, css and the like, and the operation modes are operations which need to be executed by the user and comprise clicking, text clearing, element obtaining, text obtaining, right mouse clicking, left mouse clicking, double mouse clicking, space and the like.
The test case script is automatically generated through the operation steps of the operation type, the positioning method and the operation mode selected by the user, then the terminal runs the test case script to obtain the test case, and the test case can automatically generate the automatic running script according to the test key words selected by the user.
In one possible implementation, fig. 4 shows a test case script generation diagram provided in an embodiment of the present application, as shown in the figure.
The method comprises three operation steps, wherein the operation types in the three operation steps are all positioning elements, the selection of the positioning elements is xpath, the operation modes selected in the first operation step and the second operation step are all output texts, the selection of the third operation step is clicking, and at the moment, a user only needs to maintain each step, and the terminal can automatically generate a test case script.
Optionally, after step S140, the method further includes:
s170, sending the test log under the condition that the test log is wrong.
After the test log is displayed on the terminal, the user verifies the error of the test log, and the terminal sends the error test log to a designated mailbox according to the selection of the user to analyze the reason of the error of the test log.
Compared with the prior art, the embodiment of the application has the following beneficial effects:
firstly, the identification case is obtained by adding the positioning identifier in the test case, and the identification case is continuously operated to find out the accidental faults in the program, so that the accidental faults can be quickly reproduced, the difficulty in the accidental fault repairing process is reduced, and the time cost is effectively saved.
Secondly, according to the corresponding relation between the system to be tested and the test case, the multiple systems can be tested in parallel, so that the double faults can be reproduced, the time for reproducing the double faults is greatly shortened, and the working efficiency of testers is improved.
A possible implementation of the fault recurrence apparatus is given below, which is used to execute each execution step and corresponding technical effect of the fault recurrence method shown in the foregoing embodiments and possible implementations. Referring to fig. 5, fig. 5 is a schematic structural diagram of a fault recovery apparatus 100 according to an embodiment of the present application, which is applied to the terminal, where the fault recovery apparatus 100 includes:
the generating module 110 is configured to generate a corresponding test case according to an operation step, where the operation step is determined in advance according to external feedback or a functional test;
the running module 130 is used for running the test case to generate a test log and displaying the test log on the terminal so that a user can verify the correctness of the test log;
an adding module 120, configured to add a preset location identifier to the test case to obtain an identifier case when the test log is correct;
the running module 130 is further configured to run the identification use case, and generate and send a fault log when the identification use case fails.
The application provides a fault recurrence device 100, a generating module 110 generates a corresponding test case according to an operation step, an operating module 130 operates the test case to generate a test log, the test log is displayed on a terminal so that a user can verify the correctness of the test log, an adding module 120 adds a preset positioning identifier to the test case under the condition that the user verifies that the test log is correct, and then an identification case is obtained, and the operating module 130 operates the identification case, and generates and sends a fault log when a fault occurs. The method finds out the double fault in the program and can quickly reproduce the double fault.
Optionally, the fault replication device 100 further includes:
the acquisition module is used for acquiring system information input by a user;
and the login module is used for logging in a corresponding system to be tested according to the system information, and the system to be tested corresponds to the test case.
Optionally, the generating module 110 includes:
the generating submodule is used for generating a test case script according to the operation type, the positioning method and the operation mode;
and the operation sub-module is used for operating the test case script to obtain the test case.
Optionally, the fault replication device 100 further includes:
and the sending module is used for sending the test log under the condition that the test log is wrong.
Referring to fig. 6, fig. 6 is a schematic diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
The terminal includes basic devices such as a radio frequency unit, a WiFi module, an audio output unit, a video input unit, a sensor, a display, and the like, which are included in a normal terminal. The terminal provided by the embodiment of the application may further include a processor 11, a memory 12 and a bus 13, where the processor 11 is connected to the memory 12 through the bus 13. The memory 12 is used for storing a program, such as the fault recovery device 100 shown in fig. 4, the fault recovery device 100 includes at least one software functional module which can be stored in the memory 12 in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the terminal, and the processor 11 executes the program after receiving an execution instruction to implement the fault recovery method disclosed in the above embodiment.
The memory 12 may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 12 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charge Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 12 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 12 in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.
The processor 11 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above fault recurrence method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 11. The processor 11 may be a general-purpose processor, and includes a Central Processing Unit (CPU), a Micro Control Unit (MCU), a Complex Programmable Logic Device (CPLD), a Field Programmable Gate Array (FPGA), and an embedded ARM.
The embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by the processor 11, implements the fault recurrence method disclosed in the above embodiment.
In summary, the present application provides a fault recurrence method, apparatus, terminal and computer-readable storage medium, which are applied to a terminal. Firstly, the terminal generates a corresponding test case according to the operation steps, then runs the test case to generate a test log, displays the test log on the terminal so that a user can verify the correctness of the test log, adds a preset positioning identifier to the test case under the condition that the user verifies that the test log is correct, further obtains an identification case, runs the identification case on the terminal, and generates and sends a fault log when a fault occurs. The identification case is obtained by adding the positioning identifier in the test case, and the identification case is continuously operated to find out the accidental faults in the program, so that the accidental faults can be quickly reproduced, the difficulty in the accidental fault repairing process is reduced, and the time cost is effectively saved.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A fault recurrence method is applied to a terminal, and comprises the following steps:
generating a corresponding test case according to operation steps, wherein the operation steps are determined in advance according to external feedback or functional test;
running the test case to generate a test log, and displaying the test log on a terminal so that a user can verify the correctness of the test log;
under the condition that the test log is correct, adding a preset positioning identifier into the test case to obtain an identification case;
and running the identification use case, and generating and sending a fault log when the identification use case fails.
2. The method according to claim 1, further comprising, before generating the corresponding test case according to the operation step:
acquiring system information input by a user;
and logging in a corresponding system to be tested according to the system information, wherein the system to be tested corresponds to the test case.
3. The fault recurrence method of claim 1, wherein the operation steps include an operation type, a positioning method, and an operation manner, and the step of generating the corresponding test case according to the operation steps includes:
generating a test case script according to the operation type, the positioning method and the operation mode;
and running the test case script to obtain the test case.
4. The fault recurrence method of claim 1, further comprising:
and sending the test log if the test log is wrong.
5. A fault recurrence apparatus, applied to a terminal, the apparatus comprising:
the generating module is used for generating a corresponding test case according to operation steps, and the operation steps are determined in advance according to external feedback or functional test;
the operation module is used for operating the test case to generate a test log and displaying the test log on a terminal so that a user can verify the correctness of the test log;
the adding module is used for adding a preset positioning identifier to the test case to obtain an identification case under the condition that the test log is correct;
and the operation module is also used for operating the identification use case, and generating and sending a fault log when the identification use case fails.
6. The fault recurrence device of claim 5, wherein the device further comprises:
the acquisition module is used for acquiring system information input by a user;
and the login module is used for logging in a corresponding system to be tested according to the system information, and the system to be tested corresponds to the test case.
7. The apparatus according to claim 5, wherein the operation steps include operation type, location method and operation mode, and the generating module includes:
the generating submodule is used for generating a test case script according to the operation type, the positioning method and the operation mode;
and the operation sub-module is used for operating the test case script to obtain the test case.
8. The fault recurrence device of claim 5, wherein the device further comprises:
and the sending module is used for sending the test log under the condition that the test log is wrong.
9. A terminal, comprising: a processor, a memory and a bus, the memory storing program instructions executable by the processor, the processor and the memory communicating via the bus when the client is running, the processor executing the program instructions to perform the fault recurrence method according to any one of claims 1 to 4 when executed.
10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, performs the fault-recurrence method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111506353.5A CN114328189A (en) | 2021-12-10 | 2021-12-10 | Fault recurrence method, device, terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111506353.5A CN114328189A (en) | 2021-12-10 | 2021-12-10 | Fault recurrence method, device, terminal and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114328189A true CN114328189A (en) | 2022-04-12 |
Family
ID=81050329
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111506353.5A Pending CN114328189A (en) | 2021-12-10 | 2021-12-10 | Fault recurrence method, device, terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114328189A (en) |
-
2021
- 2021-12-10 CN CN202111506353.5A patent/CN114328189A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI533123B (en) | Method and system for automated test and result comparison | |
| US20140095933A1 (en) | Testing mobile applications | |
| US20150081875A1 (en) | Method and system for operating system (os) verification | |
| CN110959153A (en) | Application analysis using flexible post-processing | |
| US7783927B2 (en) | Intelligent processing tools | |
| CN110688173B (en) | Positioning method and device of components in cross-platform interface framework and electronic equipment | |
| CN115686961A (en) | Processor testing method and device and electronic equipment | |
| US20180365132A1 (en) | Adaptive software testing | |
| CN113535577B (en) | Application testing method and device based on knowledge graph, electronic equipment and medium | |
| US10025697B2 (en) | Generation of automated unit tests for a controller layer system and method | |
| US9501390B1 (en) | Enhancing automated mobile application testing | |
| CN113918864A (en) | Website page testing method, testing system, testing device, electronic equipment and medium | |
| CN117707982A (en) | Test method, apparatus, device, medium and program product | |
| US20130275939A1 (en) | Efficient file system object-based deduplication | |
| CN112988578A (en) | Automatic testing method and device | |
| CN114328189A (en) | Fault recurrence method, device, terminal and computer readable storage medium | |
| CN115481025A (en) | Script recording method and device for automatic test, computer equipment and medium | |
| CN116048962A (en) | Test report generation method, device, computer equipment and storage medium | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN112560041B (en) | Method, apparatus and computer storage medium for automated quality verification detection | |
| CN107885648B (en) | Method and device for generating test report | |
| CN114969759A (en) | Asset safety assessment method, device, terminal and medium for industrial robot system | |
| CN116662143A (en) | Test method, apparatus, device, storage medium and computer program product | |
| CN112328473A (en) | Code automation integration test method and device and electronic equipment | |
| CN112631905A (en) | Execution process data management method and device, computer equipment and storage medium |
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 |