[3] BUG MANAGEMENT
针对不同测试工具或者不同项目，都有特定的缺陷管理方法。今天重新看了一下缺陷管理方面的资料，总结一下。
Classification of bugs:
1. Bug Status
New: Recorded by tester.
Submitted: Submitted by tester to tester leader.
Opened/Reopened: Reviewed by tester leader and confirmed to be valid bug.
Assigned: Passed the project leader’s review, need to be resolved by developer.
Hold/Postponed: Defects which can not or not need to be resolved right now.
Fixed/Recovered: Fixed by developer, needs to be verified by tester.
Canceled: Not a bug or defect.
Closed: Re-tested and confirmed to be solved exactly.
2. Bug Type
Function: Business logic errors, inconvenient operation, incomplete function etc.
Performance: Load Capacity, memory, response time etc.
Interface: Spelling/cosmetic errors, typos or format errors.
Configuration: Bugs caused by building/package error or other support system problems, or beyond appropriate environment.
Suggestion: Any enhancement or non-functional improvement.
3. Severity
Critical: An abnormal end to a program, process or function resulting in corrupted data or production hold up for the user, so no work or testing can be carried out.
Major: Certain minor function not realized, but has no effect on the workaround.
Minor: Minor function mistake, cosmetic errors or user operation is inconvenient.
4. Priority
Urgent: Need to be fixed immediately.
High priority: Need to be fixed before the next building.
Medium priority: Need to be fixed before the next release.
Low priority: Implement as time permits.
Bug management procedure
1. Discover the bugs
Performer: Tester
Precondition: Nil
Activities: Tester find software errors by execute a program or system according to the test cases, then review the differences between the expected result and the actual result, record the bugs. After the record, the status of the bug is ‘New’, and then tester submit the bug to test leader, the status is changed to be ‘Submitted’.
2. Review and open the bugs
Performer: Tester leader
Precondition: Bugs in the status of ‘Submitted’, ‘Closed’ or ‘Cancelled’.
Activities:
Tester leader review the ‘Submitted’ bugs:
If confirmed as a valid bug, distribute to the project leader, set the status to be ‘Opened’.
If confirmed as a invalid bug or tester error, set the status to be ‘Cancelled’.
If needs more detailed description, reject the bug to the submitter, the status come back to ‘New’.
Tester leader examine the ‘Closed’ or ‘Canceled’ bugs:
If the problem is still existent, then set the status to be ‘Reopened’.
3. Assign the bugs
Performer: Project leader
Precondition: Bug in the status of ‘Opened’, ‘Reopened’ or ‘Hold/Postponed’.
Activities:
Project leader review the ‘Opened’ or ‘Reopened’ bugs:
If the bug need to be resolved, assign to the corresponding developer, change the status to be ‘Assigned’.
If the bug can not be resolved right now, change the status to be ‘Hold/Postponed’.
If the bug can not pass the review or has problem to the test result, project leader can reject the bug to tester team, and the status comes back to ‘Opened’ or ‘Reopened’.
Project leader review the ‘Hold/Postponed’ bugs:
If the bug can be resolved, then assign the bug to the corresponding developer as soon as possible, the status change to ‘Assigned’.
If the bug need to be canceled, then project leader should hold a mediation, after the discussion permits, change the status to be ‘Canceled’.
4. Fix the bugs
Performer: Developer
Precondition: Bug in the status of ‘Assigned’.
Activities: Developer should resolved the ‘Assigned’ bugs, the status change to ‘Resolved’. If there is any problem, developer can reject the bug to project leader or have a talk with the corresponding tester.
5. Verify and close the bugs
Performer: Tester
Precondition: Bug in the status of ‘Resolved’.
Activities: Test retest the ‘Resolved’ bugs, if the bug is solved exactly, tester should close the bug. If the verification is failed, change the status of the bug to be ‘Reopened’.
