Test Development Engineer Growth Diary 017 - The Life Cycle of a Bug

Background:

During the previous project/iteration process, there were long bug fixes, untimely bug status, and doubts about how to transfer back to the testing process, which is not conducive to newcomers taking over the bug ticket processing.

Goal:

Clarify the specification of bug ticket circulation and bug handling time to reduce project risks caused by bug fixes.

Status flow:

Overall Status:

Instructions for filling in circulation:

1. Transfer to【Rejected】:

• • A comment must be added to explain the specific situation; if a rejection statement/comment is missing, the bug ticket will be redirected to reopen

2. Transfer to [Resolved]:

• • You can directly transfer from [Accepted] to [Resolved], skipping [Processed];
  • The corresponding defect cause category must be selected;
  • Comments must be added: add a summary description of the cause of the problem and the solution;
  • For the front-end and back-end issues, when one side (front-end/back-end) finishes processing, the one that finishes first will actively confirm whether the other side has handled it.If the other party has processed it, it will be transferred after the verification is passed; if the other party has not completed the processing, the person can be removed from the processor, and the processor who has completed the process will transfer it separately;

3. Go to [Reopen]:

• • A comment must be added to explain the latest verification results; R&D needs to pay attention to the comment information in this state in time

4. Transfer to 【Extension】:

• • Need to pass the bug review meeting, initiate R&D, and reach agreement on production, R&D, and testing, and then transfer from unified testing to deferred and legacy pool iteration;
  • In subsequent iterations, it is recommended that R&D arrange man-hours and fix no less than 30 bugs in the legacy pool every month; [Suggestion]

[Current Iteration] Repair Instructions:

1. [Test period] Bug day clearing rules:

Urgent bug:

• • Repair and submit the code on the same day, and the test and verification pass until the bug ticket is closed;

High-quality bug:

• • Submit before 16:00 on the same day, repair and submit on the same day, pass the test verification, until the bug ticket is closed;
  • Submit after 16:00 on the same day, fix and submit before 12:00 noon the next day, complete the test verification before 16:00 the next day, until the bug ticket is closed;

Zhongyou bug:

• • Fix and submit within 48 hours, the test and verification pass, until the bug ticket is closed;

Low-quality bug:

• • According to the arrangement of R&D human resources, confirm whether to postpone the circulation in the follow-up bug review meeting;
  • If there is no extension, it needs to be repaired or closed within one week;
  • If it is postponed, it needs to be repaired or closed within one month;

2. [During the test period] Test verification bug:

• Complete before 20:00 every day, and close the verification of emergency bugs and high-quality bugs;

3. [Testing period] Statistics feedback of bug list that does not meet Nissin rules:

• We will count the daily results of Zhongyou bugs every week, and email synchronous development TL for feedback;