CN115658545B - Software error reporting method and system - Google Patents
Software error reporting method and system Download PDFInfo
- Publication number
- CN115658545B CN115658545B CN202211421024.5A CN202211421024A CN115658545B CN 115658545 B CN115658545 B CN 115658545B CN 202211421024 A CN202211421024 A CN 202211421024A CN 115658545 B CN115658545 B CN 115658545B
- Authority
- CN
- China
- Prior art keywords
- log
- screenshot
- application program
- interval
- information
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a software error reporting method and a system, wherein the method comprises the following steps: starting a log monitoring program independent of the monitored application program, wherein the log monitoring program is used for monitoring log files of at least one application program, and reporting the error reporting information and logs generated within a preset time before the error reporting information is generated to a server when the error reporting information is monitored in the log files; when an application program in the foreground generates error reporting information, intercepting an application program interface to obtain a screenshot; when the log is reported to the server, reporting the error reporting information and the screenshot to the server; the log monitoring program scans the log files according to a first interval for the application program in the foreground and scans the log files according to a second interval for the application program in the background, wherein the first interval is smaller than the second interval. The method and the device can provide effective screen capturing information for testers.
Description
Technical Field
The application relates to a software testing technology, in particular to a software error reporting method and a system.
Background
The software tests include application tests before shipment and also subsequent analytical tests for user submission of the BUG. How to learn about the questions submitted by the user is generally performed by means of log reporting. The tester can analyze the BUG of the application through the log information.
When providing an application BUG, it is typically submitted after a software crash. Such an approach is generally only able to provide log information.
Disclosure of Invention
The present invention aims to solve at least one of the technical problems existing in the prior art. Therefore, the invention provides a software error reporting method and a system for providing more test information for application program developers.
In one aspect, an embodiment of the present application provides a method for reporting a software error, including:
starting a log monitoring program independent of the monitored application program, wherein the log monitoring program is used for monitoring log files of at least one application program, and reporting the error reporting information and logs generated within a preset time before the error reporting information is generated to a server when the error reporting information is monitored in the log files;
when an application program in the foreground generates error reporting information, intercepting an application program interface to obtain a screenshot;
when the log is reported to the server, reporting the error reporting information and the screenshot to the server;
the log monitoring program scans the log files according to a first interval for the application program in the foreground and scans the log files according to a second interval for the application program in the background, wherein the first interval is smaller than the second interval.
In some embodiments, the first interval is determined by:
when the log monitoring program is started, checking screen capturing permission and storage access permission;
under the condition of the taken screen capturing authority and the storage access authority, a plurality of screen capturing instructions are sent to a system;
determining average screenshot time according to each screenshot instruction and the time generated by the corresponding screenshot;
counting average processing time of the log;
and determining a first interval according to the average screenshot time, the log average processing time and a set detection time threshold.
In some embodiments, the statistical log average processing time is specifically:
acquiring the average generation quantity of the logs in the unit time of the application program;
and calculating the time required for processing the average generated number of logs to obtain the average log processing time.
In some embodiments, the determining the first interval according to the average screenshot time, the log average processing time and the set detection time threshold value specifically includes:
the detection time threshold is more than or equal to the average processing time of the log, the scanning interval of the first log file and the average screenshot time.
In some embodiments, the screenshot is uploaded to a server for privacy processing and then sent to the application developer's server.
In some embodiments, the privacy process is specifically:
checking the page number of the current application program through the reported log;
determining whether the current page contains privacy information according to the page number;
if the privacy information exists, a privacy processing template corresponding to the page number is acquired to process the privacy information.
In some embodiments, the privacy information is processed by acquiring a privacy processing template corresponding to the page number, specifically:
stretching the privacy processing template to the same size as the screenshot;
detecting the position of a character string or a picture in the screenshot, judging whether the character string or the picture meets the preset coincidence degree with a privacy area in a template, if so, judging that the character string or the picture is privacy information, and performing desensitization treatment on the character string or the picture.
In some embodiments, the method further comprises the steps of:
the status bar in the screenshot is cropped.
In another aspect, an embodiment of the present application provides a software error reporting system, including:
the system comprises a starting unit, a server and a log monitoring unit, wherein the starting unit is used for starting a log monitoring program independent of a monitored application program, the log monitoring program is used for monitoring log files of at least one application program, and when error reporting information is monitored in the log files, the error reporting information and a log generated in a preset time before the error reporting information is generated are reported to the server;
the screenshot unit is used for intercepting an application program interface to obtain a screenshot when the application program in the foreground generates error reporting information;
the report unit is used for reporting the error report information and the screenshot to the server when reporting the log to the server;
the log monitoring program scans the log files according to a first interval for the application program in the foreground and scans the log files according to a second interval for the application program in the background, wherein the first interval is smaller than the second interval.
In another aspect, an embodiment of the present application provides a software error reporting system, including:
a memory for storing a program;
and the processor is used for loading the method of the program.
According to the embodiment of the application program monitoring method, the log monitoring program independent of the monitored application program is started to monitor the log file of at least one application program, whether the program generates an error report log or not can be monitored in such a mode, meanwhile, the foreground program can be subjected to screenshot in time when the application program reports errors so as to provide more test information, meanwhile, different log scanning intervals are given according to the states of the application program in the foreground and the background, the effectiveness of screenshot is guaranteed by sequentially guaranteeing shorter scanning intervals of the program needing screenshot in the foreground, and meanwhile, the background program is given with longer scanning intervals, so that occupation of system resources by scanning is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are required to be used in the description of the embodiments will be briefly described.
FIG. 1 is a flowchart of a software error reporting method according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram of a software error reporting system according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present application more clear, the technical solutions of the present application will be clearly and completely described by implementation with reference to the accompanying drawings in the examples of the present application, and it is apparent that the described examples are some, but not all, examples of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Referring to fig. 1 and fig. 2, an embodiment of the present application discloses a software error reporting method, it may be understood that the present solution may be used as a system plug-in to provide services for an application program, where the application program is registered in advance, the information provided during registration includes basic information (such as an application name, a version number, a downloading channel, etc.) of the application program, where a log file is located, etc., and a log monitoring program monitors a log of the registered application program, processes data by means of a reporting server, and returns the processed data to a server of an application program developer, so as to provide value-added services such as data analysis, data statistics, etc. for the application program developer, where the method of the present embodiment includes:
s1, starting a log monitoring program independent of the monitored application program, wherein the log monitoring program is used for monitoring log files of at least one application program, and when error reporting information is monitored in the log files, reporting the error reporting information and logs generated within a preset time before the error reporting information is generated to a server. Typically, the error information is related to log information for a period of time before. In some scenes, all log information generated during the running of the application program can be reported, and log information generated 5 minutes before the reporting can also be reported. It should be appreciated that log monitoring programs that are independent of the application being monitored are not affected by program crashes, but because they are not embedded in the code of the application, scanning log files can have some hysteresis.
S2, when the application program in the foreground generates error reporting information, an application program interface is intercepted to obtain a screenshot. For applications in the foreground, the application screenshot is helpful to the tester in analyzing and locating program failures. Thus, for an application in the foreground, this step will take a screenshot of the application interface when it generates the error message.
And S3, reporting the error reporting information and the screenshot to a server when reporting the log to the server.
In this step, the log and the screenshot corresponding to the log are reported to the server. The server referred to in this step is a server of the log monitoring program, and the server gathers the error reporting information of each application program, provides analysis and statistics services, and finally sends the data summary to the server of the corresponding application program developer. Thus, it is understood that the server of the present application refers to a server of a service provider that provides log monitoring services.
It should be understood that the closer the time between the screenshot and the error report log is to the reference value, the greater the reference value, so if the error report information can be monitored in real time, the timeliness of the screenshot can be ensured, but in actual cases, if the real-time monitoring is required, the monitoring program will need to scan the log file frequently, which will waste the system resources. Therefore, the application solves the problem of resource allocation by configuring a higher scanning frequency for the application program in the foreground and a lower scanning frequency for the application program in the background. First, there is a need for a screenshot for the foreground program, while there is no need for a screenshot for the background program, and the screenshot has a certain urgency. Therefore, by shortening the scanning interval of the log file of the foreground application program to increase the scanning frequency, the foreground application program can be ensured to discover the error log at a faster speed, and timely implement screenshot.
Therefore, in this embodiment, the log monitor scans the log files at a first interval for the application program in the foreground and scans the log files at a second interval for the application program in the background, where the first interval is smaller than the second interval.
Specifically, the first interval is determined by:
s21, when the log monitoring program is started, the screen capturing authority and the storage access authority are checked. Firstly, the permission is required to be obtained, the permission cannot be checked until an error report log is generated, and otherwise, the program cannot perform screenshot in time. The program can remind the user to authorize when the permission is not obtained.
S22, sending a plurality of screenshot instructions to a system under the condition of the obtained screenshot authority and the storage access authority.
In this step, several screenshot instructions are sent to test the screenshot delay in the local machine. The screenshot delay is a relatively important factor affecting the screenshot time.
S23, determining average screenshot time according to each screenshot instruction and the time generated by the corresponding screenshot.
In this step, the average screenshot time may be determined by comparing the screenshot instruction with the screenshot generation time, where the average screenshot time is actually an average of several screenshot delays. Typically this value varies from tens to hundreds of milliseconds.
S24, counting log average processing time. The average time of the log is counted in order to analyze the time required to process a batch of logs in the machine, which is actually the maximum time required to estimate the log from scanning to finding the error.
Specifically, the average processing time is obtained by:
and obtaining the average generation quantity of the logs in the unit time of the application program. This value can be obtained from statistics in the server and typically determines the average log that the application produces per unit time during runtime.
And calculating the time required for processing the average generated number of logs to obtain the average log processing time. The time required to scan the average generated number of logs is then determined by locally scanning the number of logs.
S25, determining a first interval according to the average screenshot time, the log average processing time and the set detection time threshold.
Generally, the detection time threshold is greater than or equal to the average processing time of the log, the scanning interval of the first log file and the average screenshot time.
By the above formula, the first log file scanning interval can be determined, and the detection time threshold is empirically determined as a set constant, as long as it is ensured that the sum of the above three times is smaller than the value. In this way, it is ensured that the delay between log generation and screenshot is less than a certain value.
In some embodiments, the application developer is provided with a desensitization service to ensure privacy security of the user, and through the desensitization process, a tester of the application developer does not contact sensitive information possibly carried in the user screenshot. Of course, in some embodiments, services such as error reporting statistics and error reporting analysis are also provided.
Therefore, in this embodiment, the screenshot is uploaded to a server for privacy processing and then sent to the application developer's server.
In some embodiments, the privacy process is specifically:
and checking the page number of the current application program through the reported log. It will be appreciated that for most applications, the privacy-related pages are in fact a small number, and that it is possible to determine whether the privacy information is contained in the page of the current screenshot by registering the number of these pages.
And then determining whether the current page contains privacy information according to the page number in the log. By looking at the log, a log with the page number is generated when the page jumps. In this way, it can be relatively easy to determine whether a page contains private information.
If the privacy information exists, a privacy processing template corresponding to the page number is acquired to process the privacy information. The application developer can set a privacy processing template to process the privacy information as required. In practical situations, for example, a picture, through a neural network model, whether the content uploaded by a user cannot be distinguished, that is, whether the privacy information of the picture cannot be distinguished. However, the application developer may be aware that those pages have private information of the user. And the area where the privacy information is located is given by setting a page template. The processing of the privacy information is more accurate and simpler.
In some embodiments, the privacy information is processed by acquiring a privacy processing template corresponding to the page number, specifically:
the privacy handling template is stretched to the same dimensions as the screenshot. It will be appreciated that a typical application developer provides only one set of templates, but in practice the display size of the application on different handsets is not the same. Thus, by means of stretching, the above-mentioned problems can be overcome. Of course, another problem occurs when stretching, namely, the position of the privacy zone is deformed.
Therefore, the position of the character string or the picture in the screenshot needs to be detected, whether the character string or the picture meets the preset coincidence degree with the privacy area in the template or not is judged, if so, the character string or the picture is judged to be privacy information, and desensitization treatment is carried out on the character string or the picture. The overlap ratio may be calculated by dividing the overlap area of two regions by the area of one of the regions (e.g., the larger region). Although the screen distortion causes the area distortion, the corresponding positions are approximately the same, and the characters and pictures in the picture can be relatively easily confirmed to belong to private information by comparing the overlapping degree, and the information can be subjected to desensitization treatment (such as mosaic, color coating, pixel replacement and the like) by the method.
Of course, the status bar in the screenshot may also be cropped. The status bar may be given to remove the carrier information and the like, which also belongs to the privacy information.
The embodiment of the application provides a software error reporting system, which comprises the following components:
the system comprises a starting unit, a server and a log monitoring unit, wherein the starting unit is used for starting a log monitoring program independent of a monitored application program, the log monitoring program is used for monitoring log files of at least one application program, and when error reporting information is monitored in the log files, the error reporting information and a log generated in a preset time before the error reporting information is generated are reported to the server;
the screenshot unit is used for intercepting an application program interface to obtain a screenshot when the application program in the foreground generates error reporting information;
the report unit is used for reporting the error report information and the screenshot to the server when reporting the log to the server;
the log monitoring program scans the log files according to a first interval for the application program in the foreground and scans the log files according to a second interval for the application program in the background, wherein the first interval is smaller than the second interval.
The embodiment of the application provides a software error reporting system, which comprises:
a memory for storing a program;
and the processor is used for loading the method of the program.
According to the embodiment of the application program monitoring method, the log monitoring program independent of the monitored application program is started to monitor the log file of at least one application program, whether the program generates an error report log or not can be monitored in such a mode, meanwhile, the foreground program can be subjected to screenshot in time when the application program reports errors so as to provide more test information, meanwhile, different log scanning intervals are given according to the states of the application program in the foreground and the background, the effectiveness of screenshot is guaranteed by sequentially guaranteeing shorter scanning intervals of the program needing screenshot in the foreground, and meanwhile, the background program is given with longer scanning intervals, so that occupation of system resources by scanning is reduced.
Note that the above is only a preferred embodiment of the present application and the technical principle applied. Those skilled in the art will appreciate that the present application is not limited to the particular embodiments described herein, but is capable of numerous obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the present application. Therefore, while the present application has been described in connection with the above embodiments, the present application is not limited to the above embodiments, but may include many other equivalent embodiments without departing from the spirit of the present application, the scope of which is defined by the scope of the appended claims.
Claims (10)
1. A method for reporting software errors, comprising:
starting a log monitoring program independent of the monitored application program, wherein the log monitoring program is used for monitoring log files of at least one application program, and reporting the error reporting information and logs generated within a preset time before the error reporting information is generated to a server when the error reporting information is monitored in the log files;
when an application program in the foreground generates error reporting information, intercepting an application program interface to obtain a screenshot;
when the log is reported to the server, reporting the error reporting information and the screenshot to the server;
the log monitoring program scans the log files of the application program in the foreground according to a first interval, and scans the log files of the application program in the background according to a second interval, wherein the first interval is smaller than the second interval, and the first interval and the second interval refer to time intervals.
2. The software bug reporting method of claim 1, wherein the first interval is determined by:
when the log monitoring program is started, checking screen capturing permission and storage access permission;
under the condition of the taken screen capturing authority and the storage access authority, a plurality of screen capturing instructions are sent to a system;
determining average screenshot time according to each screenshot instruction and the time generated by the corresponding screenshot;
counting average processing time of the log;
and determining a first interval according to the average screenshot time, the log average processing time and a set detection time threshold.
3. The software error reporting method of claim 2, wherein the statistical log average processing time is specifically:
acquiring the average generation quantity of the logs in the unit time of the application program;
and calculating the time required for processing the average generated number of logs to obtain the average log processing time.
4. The software error reporting method according to claim 3, wherein the determining the first interval according to the average screenshot time, the log average processing time and the set detection time threshold value specifically includes:
the detection time threshold is more than or equal to the average processing time of the log, the scanning interval of the first log file and the average screenshot time.
5. The software bug reporting method of claim 1, wherein the screenshot is uploaded to a server for privacy processing and then sent to a server of an application developer.
6. The software error reporting method of claim 5, wherein the privacy processing specifically comprises:
checking the page number of the current application program through the reported log;
determining whether the current page contains privacy information according to the page number;
if the privacy information exists, a privacy processing template corresponding to the page number is acquired to process the privacy information.
7. The method for reporting a software error as in claim 6, wherein the step of obtaining the privacy processing template corresponding to the page number to process the privacy information specifically comprises:
stretching the privacy processing template to the same size as the screenshot;
detecting the position of a character string or a picture in the screenshot, judging whether the character string or the picture meets the preset coincidence degree with a privacy area in a template, if so, judging that the character string or the picture is privacy information, and performing desensitization treatment on the character string or the picture.
8. The software bug reporting method of claim 7, further comprising the steps of:
the status bar in the screenshot is cropped.
9. A software bug reporting system, comprising:
the system comprises a starting unit, a server and a log monitoring unit, wherein the starting unit is used for starting a log monitoring program independent of a monitored application program, the log monitoring program is used for monitoring log files of at least one application program, and when error reporting information is monitored in the log files, the error reporting information and a log generated in a preset time before the error reporting information is generated are reported to the server;
the screenshot unit is used for intercepting an application program interface to obtain a screenshot when the application program in the foreground generates error reporting information;
the report unit is used for reporting the error report information and the screenshot to the server when reporting the log to the server;
the log monitoring program scans the log files of the application program in the foreground according to a first interval, and scans the log files of the application program in the background according to a second interval, wherein the first interval is smaller than the second interval, and the first interval and the second interval refer to time intervals.
10. A software bug reporting system, comprising:
a memory for storing a program;
a processor for loading the program to perform the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211421024.5A CN115658545B (en) | 2022-11-14 | 2022-11-14 | Software error reporting method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211421024.5A CN115658545B (en) | 2022-11-14 | 2022-11-14 | Software error reporting method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115658545A CN115658545A (en) | 2023-01-31 |
| CN115658545B true CN115658545B (en) | 2023-05-05 |
Family
ID=85021890
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211421024.5A Active CN115658545B (en) | 2022-11-14 | 2022-11-14 | Software error reporting method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115658545B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102360328A (en) * | 2011-09-29 | 2012-02-22 | 用友软件股份有限公司 | Programmed monitoring device and programmed monitoring method |
| CN106776093A (en) * | 2016-12-12 | 2017-05-31 | Tcl集团股份有限公司 | A kind of application exception log processing method and system |
| WO2018120720A1 (en) * | 2016-12-30 | 2018-07-05 | 上海壹账通金融科技有限公司 | Method for locating test error of client program, electronic device, and storage medium |
| CN110347548A (en) * | 2019-05-28 | 2019-10-18 | 平安科技（深圳）有限公司 | A kind of method for detecting abnormality and device, storage medium, electronic equipment |
| CN111240952A (en) * | 2020-02-28 | 2020-06-05 | 北京百度网讯科技有限公司 | Log collection method and device |
| CN112749059A (en) * | 2021-01-13 | 2021-05-04 | 叮当快药科技集团有限公司 | Front-end abnormity monitoring method, device and system |
| CN113419940A (en) * | 2021-07-07 | 2021-09-21 | 广州方硅信息技术有限公司 | Program log collecting and returning method and corresponding device, equipment and medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP7281045B2 (en) * | 2019-03-27 | 2023-05-25 | 京セラドキュメントソリューションズ株式会社 | Error resolution information providing system, error resolution information providing device and electronic device |
-
2022
- 2022-11-14 CN CN202211421024.5A patent/CN115658545B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102360328A (en) * | 2011-09-29 | 2012-02-22 | 用友软件股份有限公司 | Programmed monitoring device and programmed monitoring method |
| CN106776093A (en) * | 2016-12-12 | 2017-05-31 | Tcl集团股份有限公司 | A kind of application exception log processing method and system |
| WO2018120720A1 (en) * | 2016-12-30 | 2018-07-05 | 上海壹账通金融科技有限公司 | Method for locating test error of client program, electronic device, and storage medium |
| CN110347548A (en) * | 2019-05-28 | 2019-10-18 | 平安科技（深圳）有限公司 | A kind of method for detecting abnormality and device, storage medium, electronic equipment |
| CN111240952A (en) * | 2020-02-28 | 2020-06-05 | 北京百度网讯科技有限公司 | Log collection method and device |
| CN112749059A (en) * | 2021-01-13 | 2021-05-04 | 叮当快药科技集团有限公司 | Front-end abnormity monitoring method, device and system |
| CN113419940A (en) * | 2021-07-07 | 2021-09-21 | 广州方硅信息技术有限公司 | Program log collecting and returning method and corresponding device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115658545A (en) | 2023-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105354126B (en) | Monitor method and apparatus abnormal in page script file | |
| CN112650685B (en) | Automatic test method, device, electronic equipment and computer storage medium | |
| CN110704306B (en) | Assertion processing method, device, equipment and storage medium in test | |
| KR101763804B1 (en) | Method for verifying mobile application and terminal using the same | |
| CN109344066B (en) | Method, system and terminal for testing browser page | |
| CN111611140A (en) | Reporting verification method and device of buried point data, electronic equipment and storage medium | |
| CN110879781A (en) | Program debugging method and device, electronic equipment and computer readable storage medium | |
| CN111163067A (en) | Safety testing method and device and electronic equipment | |
| CN112286825A (en) | Screen testing method and device for intelligent cabin and electronic equipment | |
| CN110618853B (en) | Detection method, device and equipment for zombie container | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN115658545B (en) | Software error reporting method and system | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN110691090B (en) | Website detection method, device, equipment and storage medium | |
| CN116738091A (en) | Page monitoring method and device, electronic equipment and storage medium | |
| CN110990289A (en) | Method and device for automatically submitting bug, electronic equipment and storage medium | |
| CN115454856A (en) | Multi-application security detection method, device, medium and electronic equipment | |
| CN115203178A (en) | Data quality inspection method and device, electronic equipment and storage medium | |
| KR20160118190A (en) | Method for verifying mobile application and terminal using the same | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal | |
| CN113872919A (en) | Vulnerability scanning method and device | |
| CN111212029A (en) | Sensitive data monitoring and tracking method | |
| CN115994098B (en) | Analysis method and system for software operation abnormality based on artificial intelligence | |
| CN116909800B (en) | Method and device for locating crash information and storage medium | |
| CN115242491B (en) | APP cloud detection method and system based on web crawlers |
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 |