|
针对缺陷采取怎样管理措施?
I have a similar question: What should be done after a bug is found?
An reference answer:
The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirments for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. The following are items to consider in the tracking process:
1. Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.
2. Bug identifier (number, ID, etc.)
3. Current bug status (e.g. 'Released for Retest', 'New', etc.)
4. The application name or identifier and version
5. The function, module, feature, object, screen, etc. where the bug occurred
6. Environment specifics, system, platform, relevant hardware specifics
7. Test case name/number/identifier
8. One-line bug description
9. Full bug description
10. Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool
11. Names and/or descriptions of file/data/messages/etc. used in test
12. File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem
13. Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)
14. Was the bug reproducible?
15. Tester name
16. Test date
17. Bug reporting date
18. Name of developer/group/organizaiton the problem is assigned to
19. Description of problem cause
20. Description of fix
21. Code section/file/module/class/method that was fixed
22. Date of fix
23. Application version that contains the fix
24. Tester responsible for retest
25. Retest date
26. Retest results
27. Regression testing requirements
28. Tester responsible for regression tests
29. Regression testing results
A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers. |
|