CN112231202A - Automatic Bug lifting method based on log monitoring and monitored module monitoring - Google Patents
Automatic Bug lifting method based on log monitoring and monitored module monitoring Download PDFInfo
- Publication number
- CN112231202A CN112231202A CN202011005785.3A CN202011005785A CN112231202A CN 112231202 A CN112231202 A CN 112231202A CN 202011005785 A CN202011005785 A CN 202011005785A CN 112231202 A CN112231202 A CN 112231202A
- Authority
- CN
- China
- Prior art keywords
- test
- bug
- log
- monitoring
- recording
- 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.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an automatic Bug lifting method based on log monitoring and monitored module monitoring, and relates to the technical field of computer research and development; the problem that when a plurality of component logs are monitored simultaneously, function return is easy to have abnormity is solved; the method specifically comprises the following steps: testing and finding problems and recording; automatic Bug submission and assignment; the test finds the problem and records the problem, particularly, the test is carried out on the service automation script test in the test environment, and the test is combined with the function test of the tester to record the IP address of the equipment for carrying out the automation script test, the function test and the like; and abnormal conditions occur in the automatic script test or the functional test. According to the invention, through the measures of layered monitoring of the test environment, monitoring of each component, log analysis and the like, the abnormal request and the related logs are stored in the Bug system, so that the time for analyzing the logs of the servers one by a tester is saved, and the Bug efficiency of recording abnormal returns is greatly improved.
Description
Technical Field
The invention relates to the technical field of computer research and development, in particular to an automatic Bug lifting method based on log monitoring and module-under-test monitoring.
Background
As business grows, software systems are continually adding new modules and components. Developers often encounter flashed bugs that take a great deal of effort to reproduce. In the process of recording the Bug, the Bug which is difficult to reproduce is reproduced, useful log information is screened out and reported to a Bug management tool, and the Bug is a time-consuming and labor-consuming task, and sometimes the project progress is seriously influenced by the generation of backtracking Bug. When a test engineer finds that the return is abnormal during testing, the test engineer needs to start from the current error reporting module, gradually analyze and call logs of other dependent modules or components on a calling chain, finally locate problems, sometimes need development assistance, and is long in time consumption and high in labor cost.
Through retrieval, the chinese patent application No. CN201510960168.1 discloses a method for quickly acquiring and submitting BUG information, which is to embed a software in a SHELL commonly used by research and development and testing personnel in a plug-in manner, open the software in the process of development and debugging, prepare to capture output information and error log in system key location at any time, record BUG that may or may not be expected at any time, and store the BUG in a local storage medium or automatically upload the BUG to a designated BUG management software using a script according to the will of an operator and issue the BUG. The method for rapidly acquiring and submitting BUG information in the patent has the following defects: when the number of software functions depends on a plurality of module components, a plurality of component logs need to be monitored simultaneously, sometimes the functions return to normal, but the logs still have abnormal problems and need to draw attention of developers.
Disclosure of Invention
The invention aims to solve the defects in the prior art, and provides an automatic Bug lifting method based on log monitoring and module-under-test monitoring.
In order to achieve the purpose, the invention adopts the following technical scheme:
an automatic Bug lifting method based on log monitoring and module-under-test monitoring comprises the following steps:
s1: testing and finding problems and recording;
s2: automatic Bug submission and assignment;
the test finds the problem and records the problem, particularly, the test is carried out on the service automation script in the test environment, and the test is combined with the function test of the tester to record the IP address of the equipment for carrying out the automation script test and the function test;
and when the automatic script test or the function test is abnormal, judging the type of test execution failure, and performing the following operations corresponding to the type:
s21: reproducing the step record;
s22: and layering and gradually searching and recording related component logs according to the call chain.
Preferably: the step of reproducing record comprises judging the execution failure of the automatic test, centralizing the test steps of the cases corresponding to the automatic execution cases, and recording the preposed post-condition information.
Preferably: the recording of the reproducing step further includes judging that the function test is failed to execute, recording an IP address returning an error request, and recording N requests of the IP address before the time node as a pre-step for reproducing the error request.
Preferably: and recording N requests of the IP address in front of the time node, and inquiring through a load balancing log.
Preferably: the layering and step-by-step searching and recording related component logs according to the call chain comprise the following steps:
s31: starting from the load balancing log, inquiring a request of an IP address, and checking the related java module logs layer by layer;
s32: when finding that the dependent module or the component log needs to be checked from the keywords in the abnormal log of the java module, inquiring the related dependent module or the component log through an applied call chain;
s33: searching the part with the close time correlation of the dependent module log;
s34: then acquiring abnormal log information with the latest time correlation from the search engine, the message queue, the cache and the database monitoring log in sequence;
s35: and classifying the relevant logs for recording.
Preferably: and the automatic Bug is submitted and assigned as a developer corresponding to the abnormal interface according to the record, and the Bug is recorded and assigned.
Preferably: the automatic Bug submission and assignment specifically comprises the following steps:
s41: issuing the collected failure request and the related log information to a Bug system;
s42: searching keywords before submitting the Bug to ensure no repeated Bug;
s43: inquiring developers in charge of the module through searching the interface documents;
s44: bug is assigned to the developer and the test team is notified by mail.
Preferably: if the Bug is found to exist, corresponding operation is required according to the Bug state in the S41; if the bus is closed, activating the Bug; activating the Bug if the Bug is solved; if the Bug status is new, no repeated recording is performed.
The invention has the beneficial effects that:
1. according to the invention, through the measures of layered monitoring of the test environment, monitoring of each component, log analysis and the like, the abnormal request and the related logs are stored in the Bug system, so that the time for analyzing the logs of the servers one by a tester is saved, and the Bug efficiency of recording abnormal returns is greatly improved.
2. The invention not only searches from the error log, but also analyzes and positions other modules and components of the call chain, records the related log information of each module and component in the Bug management system, and enters the Bug life cycle management.
3. The invention reduces the time for the testers to submit the Bug, reduces the time for the research personnel to solve the Bug, improves the communication efficiency of the test and the development and achieves the aim of reducing the project cost.
Drawings
Fig. 1 is a schematic flow chart of an automatic Bug lifting method based on log monitoring and module-under-test monitoring according to the present invention;
FIG. 2 is a schematic flow chart of a system for layering an automatic Bug lifting method based on log monitoring and module-under-test monitoring, gradually searching and recording related component logs according to a call chain, according to the invention;
FIG. 3 is a detailed flow diagram of a method for layering a log monitoring and module-under-test monitoring based automatic Bug lifting method, gradually searching and recording related component logs according to a call chain, according to the invention;
fig. 4 is a schematic diagram of an automatic Bug submission and assignment process of an automatic Bug submission method based on log monitoring and module-under-test monitoring according to the present invention.
Detailed Description
The technical solution of the present patent will be described in further detail with reference to the following embodiments.
Reference will now be made in detail to embodiments of the present patent, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present patent and are not to be construed as limiting the present patent.
In the description of this patent, it is to be understood that the terms "center," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like are used in the orientations and positional relationships indicated in the drawings for the convenience of describing the patent and for the simplicity of description, and are not intended to indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and are not to be considered limiting of the patent.
In the description of this patent, it is noted that unless otherwise specifically stated or limited, the terms "mounted," "connected," and "disposed" are to be construed broadly and can include, for example, fixedly connected, disposed, detachably connected, disposed, or integrally connected and disposed. The specific meaning of the above terms in this patent may be understood by those of ordinary skill in the art as appropriate.
Example 1:
an automatic Bug lifting method based on log monitoring and module-under-test monitoring is shown in fig. 1-4, and comprises the following steps:
s1: testing and finding problems and recording;
s2: automatic Bug submissions and assignments.
The test finds the problem and records the problem, particularly, the test is carried out on the service automation script test in the test environment, and the test is combined with the function test of the tester to record the IP address of the equipment for carrying out the automation script test, the function test and the like.
Further, the automatic script test or the functional test has an abnormal condition, the type of the test execution failure is judged, and the following operations are performed corresponding to the type:
s21: reproducing the step record;
s22: and layering and gradually searching and recording related component logs according to the call chain.
The record of the reproducing step comprises the steps of judging the execution failure of the automatic test, centralizing the test steps of the use cases corresponding to the automatic execution use cases, and recording information such as preset conditions and the like.
The recording of the reproducing step further includes judging that the function test is failed to execute, recording an IP address returning an error request, and recording N requests of the IP address before the time node as a pre-step for reproducing the error request.
Further, the N requests of the IP address before the time node are recorded and inquired through a load balancing log.
The layering and step-by-step searching and recording related component logs according to the call chain comprise the following steps:
s31: starting from the load balancing log, inquiring a request of an IP address, and checking the related java module logs layer by layer;
s32: when finding that the dependent module or the component log needs to be checked from the keywords in the abnormal log of the java module, inquiring the related dependent module or the component log through an applied call chain;
s33: searching the part with the close time correlation of the dependent module log;
s34: then acquiring abnormal log information with the latest time correlation from monitoring logs such as a search engine, a message queue, a cache and a database in sequence;
s35: and classifying the relevant logs for recording.
And the automatic Bug is submitted and assigned as a developer corresponding to the abnormal interface according to the record, and the Bug is recorded and assigned.
The automatic Bug submission and assignment specifically comprises the following steps:
s41: issuing the collected information such as the failure request, the related log and the like to a Bug system;
s42: searching keywords before submitting the Bug to ensure no repeated Bug;
s43: inquiring developers in charge of the module through searching the interface documents;
s44: bug is assigned to the developer and the test team is notified by mail.
If the Bug is found to exist, corresponding operation is required according to the Bug state in the S41; if the bus is closed, activating the Bug; activating the Bug if the Bug is solved; if the Bug status is new, no repeated recording is performed.
When the method is used, the method not only searches from the error log, but also analyzes and positions other modules and components of the call chain, records the log information related to each module and component in the Bug management system, and enters the Bug life cycle management; through the measures of layered monitoring of the test environment, monitoring of each component, log analysis and the like, the abnormal requests and related logs are stored in the Bug system, the time for analyzing the logs of the server one by a tester is saved, and the Bug efficiency of recording abnormal returns is greatly improved.
Example 2:
an automatic Bug lifting method based on log monitoring and module-under-test monitoring is shown in fig. 1-4, and comprises the following steps:
s1: testing and finding problems and recording;
s2: automatic Bug submissions and assignments.
The test finds the problem and records the problem, particularly, the test is carried out on the service automation script test in the test environment, and the test is combined with the function test of the tester to record the IP address of the equipment for carrying out the automation script test, the function test and the like.
Further, the automatic script test or the functional test has an abnormal condition, the type of the test execution failure is judged, and the following operations are performed corresponding to the type:
s21: reproducing the step record;
s22: and layering and gradually searching and recording related component logs according to the call chain.
The record of the reproducing step comprises the steps of judging the execution failure of the automatic test, centralizing the test steps of the use cases corresponding to the automatic execution use cases, and recording information such as preset conditions and the like.
The recording of the reproducing step further includes judging that the function test is failed to execute, recording an IP address returning an error request, and recording N requests of the IP address before the time node as a pre-step for reproducing the error request.
The layering and step-by-step searching and recording related component logs according to the call chain comprise the following steps:
s31: starting from the load balancing log, inquiring a request of an IP address, and checking the related java module logs layer by layer;
s32: when finding that the dependent module or the component log needs to be checked from the keywords in the abnormal log of the java module, inquiring the related dependent module or the component log through an applied call chain;
s33: searching the part with the close time correlation of the dependent module log;
s34: then acquiring abnormal log information with the latest time correlation from monitoring logs such as a search engine, a message queue, a cache and a database in sequence;
s35: and classifying the relevant logs for recording.
And the automatic Bug is submitted and assigned as a developer corresponding to the abnormal interface according to the record, and the Bug is recorded and assigned.
The automatic Bug submission and assignment specifically comprises the following steps:
s41: issuing the collected information such as the failure request, the related log and the like to a Bug system;
s42: searching keywords before submitting the Bug to ensure no repeated Bug;
s43: inquiring developers in charge of the module through searching the interface documents;
s44: bug is assigned to the developer and the test team is notified by mail.
If the Bug is found to exist, corresponding operation is required according to the Bug state in the S41; if the bus is closed, activating the Bug; activating the Bug if the Bug is solved; if the Bug status is new, no repeated recording is performed.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art should be considered to be within the technical scope of the present invention, and the technical solutions and the inventive concepts thereof according to the present invention should be equivalent or changed within the scope of the present invention.
Claims (8)
1. An automatic Bug lifting method based on log monitoring and module-under-test monitoring is characterized by comprising the following steps:
s1: testing and finding problems and recording;
s2: automatic Bug submission and assignment;
the test finds the problem and records the problem, particularly, the test is carried out on the service automation script in the test environment, and the test is combined with the function test of the tester to record the IP address of the equipment for carrying out the automation script test and the function test;
and when the automatic script test or the function test is abnormal, judging the type of test execution failure, and performing the following operations corresponding to the type:
s21: reproducing the step record;
s22: and layering and gradually searching and recording related component logs according to the call chain.
2. The method according to claim 1, wherein the reproducing step records include judging the execution failure of the automated test, recording the test steps in a case set corresponding to the automated execution cases, and recording the pre-set condition information.
3. The method as claimed in claim 2, wherein the step of replaying records further includes determining that the function test fails to be performed, recording an IP address of the return error request, and recording N requests of the IP address before the time node as a pre-step of replaying the error request.
4. The automatic Bug lifting method based on log monitoring and module-under-test monitoring as claimed in claim 3, wherein the N requests of the IP address before the time node are recorded and queried through a load balancing log.
5. The automatic Bug lifting method based on log monitoring and module-under-test monitoring as claimed in claim 4, wherein the layering and step-by-step searching and recording related component logs according to the call chain comprises the following steps:
s31: starting from the load balancing log, inquiring a request of an IP address, and checking the related java module logs layer by layer;
s32: when finding that the dependent module or the component log needs to be checked from the keywords in the abnormal log of the java module, inquiring the related dependent module or the component log through an applied call chain;
s33: searching the part with the close time correlation of the dependent module log;
s34: then acquiring abnormal log information with the latest time correlation from the search engine, the message queue, the cache and the database monitoring log in sequence;
s35: and classifying the relevant logs for recording.
6. The automatic Bug lifting method based on log monitoring and module-under-test monitoring as claimed in claim 1, wherein the automatic Bug is submitted and assigned as a developer corresponding to the interface for recording exception, and the Bug is recorded and assigned.
7. The automatic Bug lifting method based on log monitoring and module-under-test monitoring as claimed in claim 6, wherein the automatic Bug lifting and assigning specifically comprises the steps of:
s41: issuing the collected failure request and the related log information to a Bug system;
s42: searching keywords before submitting the Bug to ensure no repeated Bug;
s43: inquiring developers in charge of the module through searching the interface documents;
s44: bug is assigned to the developer and the test team is notified by mail.
8. The method of claim 7, wherein the step S41 further comprises performing corresponding operations according to the Bug status if a Bug is found to exist; if the bus is closed, activating the Bug; activating the Bug if the Bug is solved; if the Bug status is new, no repeated recording is performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011005785.3A CN112231202A (en) | 2020-09-22 | 2020-09-22 | Automatic Bug lifting method based on log monitoring and monitored module monitoring |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011005785.3A CN112231202A (en) | 2020-09-22 | 2020-09-22 | Automatic Bug lifting method based on log monitoring and monitored module monitoring |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112231202A true CN112231202A (en) | 2021-01-15 |
Family
ID=74107541
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011005785.3A Withdrawn CN112231202A (en) | 2020-09-22 | 2020-09-22 | Automatic Bug lifting method based on log monitoring and monitored module monitoring |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231202A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282516A (en) * | 2021-07-05 | 2021-08-20 | 厦门亿联网络技术股份有限公司 | Method and device for processing test case result |
-
2020
- 2020-09-22 CN CN202011005785.3A patent/CN112231202A/en not_active Withdrawn
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113282516A (en) * | 2021-07-05 | 2021-08-20 | 厦门亿联网络技术股份有限公司 | Method and device for processing test case result |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10102113B2 (en) | Software test automation systems and methods | |
| CN111400198B (en) | Self-adaptive software testing system | |
| CN110088744B (en) | Database maintenance method and system | |
| CN102053906A (en) | System and method for collecting program runtime information | |
| CN113946499A (en) | Micro-service link tracking and performance analysis method, system, equipment and application | |
| WO2007147327A1 (en) | Method, system and apparatus of fault location for communicaion apparatus | |
| CN115080398A (en) | Automatic interface test system and method | |
| CN112306877A (en) | Power system fault operation and maintenance method and system | |
| US8327189B1 (en) | Diagnosing an incident on a computer system using a diagnostics analyzer database | |
| CN113986669A (en) | Call chain tracking and business analysis method based on AOP annotation | |
| CN115952081A (en) | Software testing method, device, storage medium and equipment | |
| CN112231202A (en) | Automatic Bug lifting method based on log monitoring and monitored module monitoring | |
| CN115080389A (en) | Test system, method, equipment and storage medium for improving index statistical efficiency | |
| CN110147313B (en) | Log output method and device | |
| CN116405412B (en) | Method and system for verifying cluster effectiveness of simulation server based on chaotic engineering faults | |
| CN116230067A (en) | Automatic testing method, system, equipment and medium for solid state disk | |
| CN111708654A (en) | Method and equipment for repairing virtual machine fault | |
| CN116107794A (en) | Ship software fault automatic diagnosis method, system and storage medium | |
| CN115686921A (en) | Multipath anomaly detection and repair method, device, equipment and medium | |
| CN113485919B (en) | Test method, test device, and computer-readable storage medium | |
| CN113626288B (en) | Fault processing method, system, device, storage medium and electronic equipment | |
| CN115658470A (en) | Distributed system-oriented automatic testing method and device for failure recovery mechanism | |
| CN113342675B (en) | Mapping method and device of tested module, and testing method and system | |
| CN109254919B (en) | Embedded software diagnosis system and method | |
| CN113037550B (en) | Service fault monitoring method, system and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210301 Address after: Room 109, building 2, no.787, manufacturing Bureau Road, Huangpu District, Shanghai 200011 Applicant after: Shanghai Qiyun Technology Co.,Ltd. Address before: Room 109, 655 Yinxiang Road, Jiading District, Shanghai, 201802 Applicant before: SHANGHAI RONGYIWANG ELECTRONIC COMMERCE Co.,Ltd. |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210115 |