CN111666168B - Method and terminal for automatically recording test exception - Google Patents
Method and terminal for automatically recording test exception Download PDFInfo
- Publication number
- CN111666168B CN111666168B CN201910168368.1A CN201910168368A CN111666168B CN 111666168 B CN111666168 B CN 111666168B CN 201910168368 A CN201910168368 A CN 201910168368A CN 111666168 B CN111666168 B CN 111666168B
- Authority
- CN
- China
- Prior art keywords
- application
- tested
- test
- automatically
- exception
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a terminal for automatically recording test abnormity, which take over an abnormity processing method of an application to be tested in a Hook mode, automatically record page information in the test process of the application to be tested, automatically receive corresponding abnormal logs if abnormity is captured in the test process of the application to be tested, automatically store the recorded page information and the abnormal logs, can timely acquire the abnormity in the test and the related abnormal logs, reduce an operation flow, help to analyze abnormity causes, reduce manual operation, reduce test pressure, improve the efficiency of acquiring test abnormity, can be used for various programs, and has wide applicability and strong reusability.
Description
Technical Field
The invention relates to the technical field of testing, in particular to a method and a terminal for automatically recording testing abnormity.
Background
Various abnormalities or errors are often encountered in the usual test process, some abnormalities are often missed due to the heavy test task and the like, or the occurrence steps are not recorded in time when the abnormalities occur, so that developers cannot find the reasons in time and cannot repair the abnormalities in time, particularly some abnormalities caused by a specific operation flow are difficult to reproduce if the operations are not performed according to the specific flow.
When an abnormal log occurs in the test process, in order to reproduce the accidental bug, usually a tester needs to actively connect a computer to execute a command or acquire the abnormal log through an IDE (integrated development environment), finding the abnormal log is complicated under the condition of more logs, the requirement on the tester is higher, even the tester with rich experience cannot avoid missing the abnormal log or missing some steps in the test process, and sometimes the abnormal log cannot be timely acquired, so that the abnormal log is brushed away by the following information or emptied after the cache time is exceeded, and great inconvenience is brought to the test process.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the method and the terminal for automatically recording the test exception can improve the efficiency of acquiring the test exception.
In order to solve the technical problem, the invention adopts a technical scheme that:
a method of automatically recording test anomalies, comprising the steps of:
taking over an exception handling method of the application to be tested in a Hook mode;
automatically recording page information in the test process of the application to be tested;
and judging whether the abnormality is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding abnormality log, and automatically storing the recorded page information and the abnormality log.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a terminal for automatically recording test exceptions, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
taking over an exception handling method of the application to be tested in a Hook mode;
automatically recording page information in the test process of the application to be tested;
and judging whether the abnormality is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding abnormality log, and automatically storing the recorded page information and the abnormality log.
The invention has the beneficial effects that: the method comprises the steps of taking over an exception handling method of an application to be tested in a Hook mode, automatically recording page information in the testing process of the application to be tested, automatically receiving a corresponding exception log if an exception is captured in the testing process of the application to be tested, automatically storing the recorded page information and the exception log, timely acquiring the exception and the related exception log in the test, restoring an operation flow, helping to analyze the reason of the exception, reducing manual operation, reducing testing pressure, improving the efficiency of acquiring the exception of the test, being applicable to various programs, and having wide applicability and strong reusability.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for automatically recording test exceptions in accordance with one embodiment of the present invention;
fig. 2 is a schematic structural diagram of a terminal for automatically recording a test exception according to an embodiment of the present invention;
FIG. 3 is a Hook functional schematic of an embodiment of the present invention;
FIG. 4 is a flowchart illustrating steps of a method for automatically recording test exceptions, in accordance with an embodiment of the present invention;
FIG. 5 is a flowchart illustrating steps of a method for automatically recording test exceptions, in accordance with an embodiment of the present invention;
description of reference numerals:
1. a terminal for automatically recording test anomalies; 2. a memory; 3. a processor.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
The noun interpretation:
hook: in an Android operating system, the system maintains a set of event distribution mechanism of the system, application trigger events and background logic processing in an application program are executed step by step according to an event flow, and Hook can intercept and monitor transmission of events before the events are transmitted to a terminal point, as shown in fig. 3, the method is similar to hooking events and can process specific events while hooking the events.
The most key concept of the invention is that an exception handling method of the application to be tested is taken over in a Hook mode, page information in the test process of the application to be tested is automatically recorded, and the recorded page information and the exception log are automatically stored when an exception is captured in the test process.
Referring to fig. 1, a method for automatically recording test anomalies includes the steps of:
taking over an exception handling method of the application to be tested in a Hook mode;
automatically recording page information in the test process of the application to be tested;
and judging whether the abnormality is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding abnormality log, and automatically storing the recorded page information and the abnormality log.
From the above description, the beneficial effects of the present invention are: the method comprises the steps of taking over an exception handling method of an application to be tested in a Hook mode, automatically recording page information in the testing process of the application to be tested, automatically receiving a corresponding exception log if an exception is captured in the testing process of the application to be tested, automatically storing the recorded page information and the exception log, timely acquiring the exception and the related exception log in the test, restoring an operation flow, helping to analyze the reason of the exception, reducing manual operation, reducing testing pressure, improving the efficiency of acquiring the exception of the test, being applicable to various programs, and having wide applicability and strong reusability.
Further, the exception handling method for taking over the application to be tested in a Hook manner includes:
installing an application to be tested, and acquiring a first package name of the application to be tested;
the exception handling method for taking over the application to be tested in the Hook mode and the step of automatically recording the page information in the test process of the application to be tested comprise the following steps:
monitoring the application to be tested, judging whether the application to be tested is started, if so, acquiring current page information, and acquiring a second package name of the application to be tested according to the current page information;
and judging whether the second package name is the same as the first package name, if not, ending the test, and if so, automatically recording page information in the test process of the application to be tested.
According to the description, the first package name and the second package name are compared, the currently started application is ensured to be the application to be tested, the accuracy and the reliability are improved, the condition that the currently started application is not the application to be tested is avoided, and the subsequent test operation is only carried out when the second package name is the same as the first package name.
Further, the page information includes Activity information;
the automatically recording the page information in the test process of the application to be tested comprises the following steps:
s1, acquiring Activity information of the current page, and storing the Activity information of the current page into a stack;
and S2, executing corresponding operation on the application to be tested according to the test case, judging whether to switch to a new page or not in the operation process, and if so, returning to execute the step S1.
According to the description, the Activity information of the current page is recorded, and the Activity information of the page is recorded when the current page is switched to a new page, so that the page information of the application to be tested during the execution of the test case can be automatically recorded, the operation process is restored, the test efficiency is improved, and the manual test pressure is reduced.
Further, the exception log includes a third package name;
judging whether the capture abnormality occurs, if so, automatically receiving a corresponding abnormality log, specifically:
and judging whether the abnormality processing method captures abnormality or not, if so, acquiring an abnormality log with a third packet name identical to the first packet name of the application to be detected from the abnormality log.
According to the description, when the abnormality is captured in the test process, the abnormal log corresponding to the application to be tested in the abnormal log is automatically obtained according to the packet name, the corresponding abnormal log is obtained in time, omission is avoided, the problem that the abnormal information is not obtained in time or the abnormal information is omitted in the current test process is solved, and convenience is improved.
Further, the automatically saving the recorded page information and the exception log comprises:
creating a corresponding folder according to the second packet name, and creating a text file under the folder according to a timestamp of the current time;
writing the Activity information and the exception log in the stack into the text file;
emptying the stack.
According to the description, the folder and the text file are automatically created to store the recorded page information and the abnormal log, so that the condition that the abnormal related information is emptied after the cache time is exceeded can be avoided, and the analysis of the abnormal reason is facilitated; after the related information of the abnormality is stored, the stack is emptied, the test is continued, the related information of the abnormality in each test can be automatically recorded, and the efficiency is improved.
Referring to fig. 2, a terminal for automatically recording a test exception includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the following steps:
taking over an exception handling method of the application to be tested in a Hook mode;
automatically recording page information in the test process of the application to be tested;
and judging whether the abnormality is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding abnormality log, and automatically storing the recorded page information and the abnormality log.
From the above description, the beneficial effects of the present invention are: the method comprises the steps of taking over an exception handling method of an application to be tested in a Hook mode, automatically recording page information in the testing process of the application to be tested, automatically receiving a corresponding exception log if an exception is captured in the testing process of the application to be tested, automatically storing the recorded page information and the exception log, timely acquiring the exception and the related exception log in the test, restoring an operation flow, helping to analyze the reason of the exception, reducing manual operation, reducing testing pressure, improving the efficiency of acquiring the exception of the test, being applicable to various programs, and having wide applicability and strong reusability.
Further, the exception handling method for taking over the application to be tested in a Hook manner includes:
installing an application to be tested, and acquiring a first package name of the application to be tested;
the exception handling method for taking over the application to be tested in the Hook mode and the step of automatically recording the page information in the test process of the application to be tested comprise the following steps:
monitoring the application to be tested, judging whether the application to be tested is started, if so, acquiring current page information, and acquiring a second package name of the application to be tested according to the current page information;
and judging whether the second package name is the same as the first package name, if not, ending the test, and if so, automatically recording page information in the test process of the application to be tested.
According to the description, the first package name and the second package name are compared, the currently started application is ensured to be the application to be tested, the accuracy and the reliability are improved, the condition that the currently started application is not the application to be tested is avoided, and the subsequent test operation is carried out only when the second package name is the same as the first package name.
Further, the page information includes Activity information;
the automatically recording the page information in the test process of the application to be tested comprises the following steps:
s1, acquiring Activity information of the current page, and storing the Activity information of the current page into a stack;
and S2, executing corresponding operation on the application to be tested according to the test case, judging whether to switch to a new page or not in the operation process, and if so, returning to execute the step S1.
According to the description, the page information of the application to be tested can be automatically recorded when the test case is executed by recording the Activity information of the current page and recording the Activity information of the page when the current page is switched to a new page every time, so that the operation flow is restored, the test efficiency is improved, and the manual test pressure is reduced.
Further, the exception log includes a third packet name;
judging whether the abnormity is captured, if so, automatically receiving the corresponding abnormity log specifically comprises the following steps:
and judging whether the abnormality processing method captures abnormality or not, if so, acquiring an abnormality log with a third packet name identical to the first packet name of the application to be detected from the abnormality log.
According to the description, when the abnormal log is captured in the test process, the abnormal log corresponding to the application to be tested in the abnormal log is automatically obtained according to the packet name, the corresponding abnormal log is obtained in time, omission is avoided, the problem that the abnormal information is not obtained in time or the abnormal information is omitted in the current test process is solved, and convenience is improved.
Further, the automatically saving the recorded page information and the exception log comprises:
creating a corresponding folder according to the second packet name, and creating a text file under the folder according to a timestamp of the current time;
writing the Activity information and the exception log in the stack into the text file;
emptying the stack.
According to the description, the folder and the text file are automatically created to store the recorded page information and the abnormal log, so that the condition that the abnormal related information is emptied after the cache time is exceeded can be avoided, and the analysis of the abnormal reason is facilitated; after the related information of the abnormality is stored, the stack is emptied, the test is continued, the related information of the abnormality in each test can be automatically recorded, and the efficiency is improved.
Example one
Referring to fig. 1 and 4, a method for automatically recording test anomalies includes the steps of:
selecting equipment to be tested, namely the tested equipment, and configuring a required environment on the equipment to be tested;
before testing is started, verifying whether a self-research tool with a Hook function is installed on the equipment to be tested, and if not, installing the self-research tool with the Hook function;
the self-research tool is similar to an Xpos frame, a service frame which can influence program operation under the condition of not modifying APP can achieve the Hook function through the take-over of bottom layer service, the self-research tool has low immersion on the application to be tested, and the operation of the application to be tested cannot be influenced;
installing an application to be tested, namely the APP to be tested needing to be monitored, selecting whether to perform automatic testing or not, and if not, performing testing according to a manual testing mode; if yes, testing according to an automatic testing process;
acquiring a first package name of the application to be detected;
starting the self-research tool, inputting a first package name of the application to be tested, namely the name of the package, and monitoring the application to be tested through the self-research tool;
taking over an exception handling method of the application to be tested in a Hook mode;
specifically, taking over an exception handling method UncaughtExceptionHandler of the application to be tested through a Hook function of the self-research tool, monitoring UncaughtException by the self-research tool through an observer mode, and capturing the application to be tested by the self-research tool when the UncaughtException is generated;
monitoring the application to be tested, judging whether the application to be tested is started, if so, acquiring page information of a home page after the application to be tested is started, and acquiring a second package name of the application to be tested according to the current page information;
specifically, when the application to be tested is started, the Activity Manager Service sends a Launcher _ Activity message to the Activity to start the Activity of the application to be tested, and the self-research tool monitors the Activity Manager Service through the Hook function, so that monitoring on whether the application to be tested is started is realized;
once the self-research tool receives a Launcher _ Activity message sent by an Activity Manager Service to an Activity, the application to be tested is judged to be started, at this time, an adb shell duty Activity | grep-i run command is executed to obtain Activity information of a current page of the application to be tested, and the name of a package of the current Activity is obtained from the Activity information and is used as a second package name of the application to be tested;
judging whether the second package name is the same as the first package name, if not, indicating that the started application is not the application to be tested, ending the test, if so, executing a test case, and automatically recording page information in the test process of the application to be tested;
wherein the page information comprises Activity information;
specifically, S1, acquiring Activity information of a current page, and storing the Activity information of the current page into a stack;
the self-research tool executes an adb shell dumpsys Activity | grep-i run command to acquire Activity information of a current page, and stores the acquired Activity information into a Stack for recording;
the Activity information includes a name of an Activity, such as nd.com.xx.mainactivity;
s2, executing corresponding operation on the application to be tested according to the test case, judging whether to switch to a new page to execute the test operation in the operation process, and if so, returning to the step S1;
in the process of executing the test case, every page is operated, the Activity information of the page is stored into a stack, and the operation process can be restored by recording the page information in the test process;
and judging whether the abnormality is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding abnormality log, automatically storing the recorded page information and the abnormality log, and if not, continuously executing the test operation.
Whether the test is an automatic test or a manual test, when an abnormity occurs, the corresponding abnormal log can be automatically acquired, and the recorded page information and the abnormal log are stored locally;
the exception log comprises a package, and the name of the package is used as a third package name;
specifically, whether the UncaudexException handler captures the abnormity or not is judged through a self-research tool, namely whether UncaudexException is generated or not, if not, the current to-be-tested application is normal in operation, if yes, bug is generated, and at the moment, the self-research tool captures Uncaudexeption and automatically receives an abnormal log sent by a to-be-tested equipment system;
the method includes the steps that abnormal log information is sent by a device system to be tested and other applications on the device to be tested, so that abnormal logs corresponding to the applications to be tested need to be screened from received abnormal logs, specifically, the abnormal logs with the third packet name identical to the first packet name of the applications to be tested are obtained from the abnormal logs, and the Activity information recorded in the stack is added to the corresponding abnormal logs.
Example two
Referring to fig. 5, a difference between the present embodiment and the first embodiment is that the present embodiment further includes, after the automatically saving the recorded page information and the exception log:
creating a corresponding folder on a storage structure according to the second packet name, and creating a text file under the folder according to the timestamp of the current time;
preferably, the storage structure is a component capable of storing data, such as an SD card;
writing the information of the abnormal log with the Activity information in the stack, which corresponds to the application to be tested, into the text file;
the stack is automatically emptied through the self-research tool, so that other test cases can be conveniently and subsequently executed;
repeating the steps until all the test cases are completely executed, and ending the test;
in addition, before executing a new test case, the information saved during the previous test execution is actively cleared, so that the immersion of the self-research tool to the application to be tested is reduced to the minimum and is almost zero, and the running of the application to be tested is not influenced.
EXAMPLE III
Referring to fig. 2, a terminal 1 for automatically recording a test exception includes a memory 2, a processor 3, and a computer program stored in the memory 2 and executable on the processor 3, where the processor 3 implements the steps of the first embodiment when executing the computer program.
Example four
Referring to fig. 2, a terminal 1 for automatically recording a test exception includes a memory 2, a processor 3, and a computer program stored in the memory 2 and capable of running on the processor 3, where the processor 3 implements the steps of the second embodiment when executing the computer program.
In summary, the method and terminal for automatically recording test exception provided by the present invention install an application to be tested, and obtain a first package name of the application to be tested, take over an exception handling method of the application to be tested in a Hook manner, when it is monitored that the application to be tested is started, obtain a second package name of the application to be tested according to current page information, compare the second package name with the first package name, continue to execute a test case only when the second package name is the same as the first package name, automatically record page information in a test process of the application to be tested, if an exception is captured in the test process of the application to be tested, automatically receive a corresponding exception log, create a text file according to a timestamp of the current time, automatically store the recorded page information and the exception log into the text file, and can ensure that the currently started application is the application to be tested, the method has the advantages of improving accuracy, timely obtaining abnormity and related abnormal logs in the test, restoring the operation process, helping to analyze abnormal reasons, avoiding the condition that abnormal related information exceeds the cache time and is emptied, reducing manual operation, reducing test pressure, improving efficiency of obtaining abnormal test, being applicable to various programs, being wide in applicability and strong in reusability.
The above description is only an embodiment of the present invention, and is not intended to limit the scope of the present invention, and all equivalent modifications made by the present invention and the contents of the accompanying drawings, which are directly or indirectly applied to the related technical fields, are included in the scope of the present invention.
Claims (6)
1. A method for automatically recording test anomalies, comprising the steps of:
taking over an exception handling method of the application to be tested in a Hook mode;
automatically recording page information in the test process of the application to be tested;
judging whether an exception is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding exception log, and automatically storing the recorded page information and the exception log; the exception handling method for taking over the application to be tested in a Hook mode comprises the following steps:
installing an application to be tested, and acquiring a first package name of the application to be tested;
the exception handling method for taking over the application to be tested in the Hook mode and the step of automatically recording the page information in the test process of the application to be tested comprise the following steps:
monitoring the application to be tested, judging whether the application to be tested is started, if so, acquiring current page information, and acquiring a second package name of the application to be tested according to the current page information;
judging whether the second package name is the same as the first package name or not, if not, finishing the test, and if so, automatically recording page information in the test process of the application to be tested;
the exception log includes a third packet name;
judging whether the capture abnormality occurs, if so, automatically receiving a corresponding abnormality log, specifically:
and judging whether the abnormality processing method captures abnormality or not, if so, acquiring an abnormality log with a third packet name identical to the first packet name of the application to be detected from the abnormality log.
2. The method of claim 1, wherein the page information comprises Activity information;
the automatically recording the page information in the test process of the application to be tested comprises the following steps:
s1, acquiring Activity information of the current page, and storing the Activity information of the current page into a stack;
and S2, executing corresponding operation on the application to be tested according to the test case, judging whether to switch to a new page or not in the operation process, and if so, returning to execute the step S1.
3. The method of claim 2, wherein automatically saving the recorded page information and the exception log comprises:
creating a corresponding folder according to the second packet name, and creating a text file under the folder according to the timestamp of the current time;
writing the Activity information and the exception log in the stack into the text file;
emptying the stack.
4. A terminal for automatically recording test exceptions, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to perform the steps of:
taking over an exception handling method of the application to be tested in a Hook mode;
automatically recording page information in the test process of the application to be tested;
judging whether an abnormality is captured or not in the test process of the application to be tested, if so, automatically receiving a corresponding abnormality log, and automatically storing recorded page information and the abnormality log; the exception handling method for taking over the application to be tested in a Hook mode comprises the following steps:
installing an application to be tested, and acquiring a first package name of the application to be tested;
the exception handling method for taking over the application to be tested in the Hook mode and the step of automatically recording the page information in the test process of the application to be tested comprise the following steps:
monitoring the application to be tested, judging whether the application to be tested is started, if so, acquiring current page information, and acquiring a second package name of the application to be tested according to the current page information;
judging whether the second package name is the same as the first package name or not, if not, finishing the test, and if so, automatically recording page information in the test process of the application to be tested;
the exception log includes a third packet name;
judging whether the abnormity is captured, if so, automatically receiving the corresponding abnormity log specifically comprises the following steps:
and judging whether the abnormality processing method captures abnormality or not, if so, acquiring an abnormality log with a third packet name identical to the first packet name of the application to be detected from the abnormality log.
5. The terminal for automatically recording the test exception according to claim 4, wherein the page information comprises Activity information;
the automatically recording the page information in the test process of the application to be tested comprises the following steps:
s1, acquiring Activity information of the current page, and storing the Activity information of the current page into a stack;
and S2, executing corresponding operation on the application to be tested according to the test case, judging whether to switch to a new page or not in the operation process, and if so, returning to execute the step S1.
6. The terminal for automatically recording the test exception according to claim 5, wherein the automatically saving the recorded page information and the exception log comprises:
creating a corresponding folder according to the second packet name, and creating a text file under the folder according to a timestamp of the current time;
writing the Activity information and the exception log in the stack into the text file;
emptying the stack.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910168368.1A CN111666168B (en) | 2019-03-06 | 2019-03-06 | Method and terminal for automatically recording test exception |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910168368.1A CN111666168B (en) | 2019-03-06 | 2019-03-06 | Method and terminal for automatically recording test exception |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111666168A CN111666168A (en) | 2020-09-15 |
| CN111666168B true CN111666168B (en) | 2022-08-30 |
Family
ID=72381298
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910168368.1A Active CN111666168B (en) | 2019-03-06 | 2019-03-06 | Method and terminal for automatically recording test exception |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111666168B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101930399A (en) * | 2010-08-16 | 2010-12-29 | 于秀山 | Method for recording software test |
| CN105574416A (en) * | 2015-12-16 | 2016-05-11 | 北京神州绿盟信息安全科技股份有限公司 | Detection method and device of browser bug |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104424094B (en) * | 2013-08-26 | 2019-04-23 | 腾讯科技（深圳）有限公司 | A kind of exception information acquisition methods, device and intelligent terminal |
-
2019
- 2019-03-06 CN CN201910168368.1A patent/CN111666168B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101930399A (en) * | 2010-08-16 | 2010-12-29 | 于秀山 | Method for recording software test |
| CN105574416A (en) * | 2015-12-16 | 2016-05-11 | 北京神州绿盟信息安全科技股份有限公司 | Detection method and device of browser bug |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111666168A (en) | 2020-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7149928B2 (en) | User transparent software malfunction detection and reporting | |
| US10545807B2 (en) | Method and system for acquiring parameter sets at a preset time interval and matching parameters to obtain a fault scenario type | |
| US7908521B2 (en) | Process reflection | |
| US20070220370A1 (en) | Mechanism to generate functional test cases for service oriented architecture (SOA) applications from errors encountered in development and runtime | |
| CN109408338B (en) | Method, device, equipment and system for grabbing trace of NVME (network video management entity) hard disk | |
| KR20160044484A (en) | Cloud deployment infrastructure validation engine | |
| CN107577597B (en) | Installation package automatic testing method, device, equipment and storage medium | |
| US7913233B2 (en) | Performance analyzer | |
| EP3591485B1 (en) | Method and device for monitoring for equipment failure | |
| US11422920B2 (en) | Debugging multiple instances of code using thread patterns | |
| CN113064762B (en) | Service self-recovery method based on various detection | |
| CN101706752B (en) | Method and device for in-situ software error positioning | |
| CN111666168B (en) | Method and terminal for automatically recording test exception | |
| CN110928787B (en) | Automatic test script recording and playback method, device, equipment and storage medium | |
| CN115599645B (en) | Method and device for testing stability of linux driving module | |
| CN107844395B (en) | Reboot test control method and system | |
| JP2001243089A (en) | Device and method for verifying software | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN113986622A (en) | SDK abnormity self-checking method, device, medium and computing equipment | |
| JP5592828B2 (en) | Patch impact analysis apparatus, method and program | |
| WO2010018619A1 (en) | Information processor and hang-up cause investigation information acquiring method | |
| CN107766251B (en) | Detection method, system and device for loading image and readable storage medium | |
| CN114257534A (en) | Test result processing method, device and system and storage medium | |
| CN109376030B (en) | System for capturing embedded operating system exceptions | |
| CN115756914A (en) | Test method, test system, test platform and test machine |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |