Advice on handling minor bugs

The project encountered a bug where the reproduction rate was extremely low.
Developers are often responsible for investigating bugs.
The reason is quite boring. Bug
It cannot be reproduced, that is, it is difficult to find a bug.
And there is no countermeasure. Below are my very low probability of reproduction bugs
Some Ideas about processing. (
I personally think the recurrence rate is 5%.
The following bugs
That is, the bug of extremely low recurrence rate)

 

Extremely low probability of reproduction bug
Features:

-> Bug
Random appearance-
It often happens by accident.

->
Complex test environment

->
There is no regularity in reproducibility-
Bug-based development
Difficult to find rules when the investigation is reproduced

->
Some bugs
Once, it cannot be reproduced again

 

What Should testers do:

1.


When a bug occurs
Especially unexpected bugs
Always make bugs
Record. Bug
The record must contain the following content.

(1)


Bug
Test case when a test occurs
, The content to be verified.

(2)


Versions of tested software and products

(3)


Test environment, especially hardware requirements, software environment, and constraints.

(4)


A detailed record is required for testing the handline and input conditions, that is, the operation steps.

(5)


What is the expected normal result.

(6)


Bug
Symptom. Detailed records are required. It is best to take a photo or so on.

(7)


Record the recovery steps and conditions.

(8)


Bug
The probability of occurrence.

In short, when a bug occurs
Must be recorded as soon as possible, and as detailed as possible.

2.


Save bug
Log at occurrence
And data (
Various variables, memory, memory, and other data content when an error occurs)
.

3.


When a tester finds an accidental bug
Or bugs that are hard to reproduce
You need to carefully check the testing environment at that time, for example, whether there is any special software installed on the testing machine, and no viruses, and detailed records. If necessary, the test environment must be protected. For developers to confirm and reproduce.

4.


Test as many bugs as possible
The test items that appear are tested repeatedly to find out the rule.

5.


Bugs that cannot be reproduced
Report to test Manager and project manager.

6.


Assists developers in recreating bugs
.

 

What Should developers do:

1.


Ensure that the Code submitted to the tester is not warning
. Waring
It may cause potential problems.

2.


Measure the test taker's knowledge about bugs.
When the environment appears, repeat the bug with the help of testers
.

3.


You must use the same environment as the test environment to reproduce bugs.
. It is best to make a bug in the environment used for testing.
. Due to the non-reproducibility bug
The reason is complex and may have an impact on the external environment. The Reproduction on the test machine can ensure the consistency of the test conditions.

4.


External factors, such as compatibility issues, should be excluded.

5.


Based on bug
Found phenomenon, log
And other data to analyze bugs
Record the possible causes. You can start from the dashboard for processing. Narrow down bugs
The scope of the investigation.

6.


Conducts comprehensive manual queries on suspicious code and checks using comparison tools. It is necessary to hold a code review and review meeting.

7.


For bugs that have not been reproduced
Be sure to report to the Project Manager and explain the problem if the bug
There are dangers that can be brought.

 

 

What should the project manager and management personnel do:

1.


Developers are required to write bugs
Report and analyze the causes and hazards.

2.


According to the degree of urgency
Processing into daily/
Weekly tracking list. The problem resolution status is tracked during each opening meeting.

3.


For bugs that cannot be reproduced
It is best to hold analysis meetings attended by project managers, design developers, and testers. It is best to have peer participation from similar experts to address bugs.
Make analysis and judgment on the hazards and impacts, and determine whether the vulnerability can be deemed as non-reproducible.
, Bug
Close the trail.

4.


For common bugs
There must be records and Cause Analysis and Countermeasures for tracking, so as to avoid the occurrence of Mao Cao.

5.


Use a good development process to ensure the quality of the developed products.

6.


Cultivate developers' quality awareness, pay attention to code review, UT
.