Bug Summary Process

These days with the project officially on-line, the issue of a full-blown bug, no statement of good bugs, program personnel and testers have been communicating, the bug can not be accurately and effectively modify the closure, this on-line system is fatal.

Bug Summary Idea

1. Collect the problem of online leak detection

2. Detailed analysis of the Bug mechanism and the cause of the missed test for each missing question

3. Based on the above reasons to think about how to improve, to avoid the problem of leak detection

4. Implementation of the improvement programme

5. Repeat the above steps to continuously optimize the quality improvement of the Test team through positive loops

Bug Summary Process :

In order to facilitate the operation and operations of the process, a summary process and forms are established on the company's internal system:

To illustrate:

One day, the small Wang Test ERP project on-line, there are many online statistics incorrect questions. Xiao Wang received this question feedback, the first time to follow up and deal with the problem, confirm the problem exists, while cooperating with the development and other people to trace the cause of the problem, after the problem was traced, because of the coverage of the database, the development followed by the issue of remediation.

Process Walkthroughs:

1. After receiving this question, Lao Wang will let Xiao Wang enter this issue into the PMO summary form

2. According to the following information, Xiao Wang fills in the PMO separately:

A. cause of the problem (including development reasons and test reasons )

Development reasons:

Xxxxxxxxx

Test reason:

1) test for the development of the XX template is not fully in-depth, resulting in the XX module has been modified, but also stay in the black box test plane;

2) Test design considerations, Input method coverage case leakage test.

B. Problem classification ( What type of problem is this )

the problem in the example is not understood by the implementation of the development changes, so the problem type is judged as "insufficient use case design" and "insufficient knowledge of design level" and " Test experience, insufficient test divergence "

C. Development of solutions

First determine whether the first bit is empty, if not empty (old format), the old format is mapped to the new format, and then read in the new format, if it is empty, directly in the new format read

D. Test the Improvement Program ( based on the problem reason to deduce how to improve, to avoid recurrence of similar problems )

1) starting from the vx.x version, the Test team will draw a development implementation flowchart for each module to further understand the development implementation;

2) in the pre-launch test checklist to increase the coverage installed case, from the process to ensure the quality of testing;

3) in the process, the Code optimization or code reconstruction and other technical requirements of the change content research, and output "impact scope" evaluation report.

4) Organize XX test points to form a document, every time you test XX according to the document. If XX has changed, add test points on this basis.

3. Lao Wang to the small Wang fill out the form of the various contents of the audit, the contents of the various fields to understand in depth, fill in the correct, the old Wang for approval, the form will be in the implementation of the improvement Program.

4. Follow-up Lao Wang will urge Xiao Wang's improvement program implementation, such as: Xiao Wang finishing XX test point document.

5. When the above improvements have been implemented, Xiao Wang put this form to the improvement completed by the Lao Wang Audit closed.

It is through the above process, accumulated a lot of experience, testing ability steadily improved, gradually became the pillar of the team.

"Reflection is a mirror, which can make our mistakes clear, so that we have the opportunity to correct." --Heine "

Bug Summary Process