BUG生命周期手册定义.pdfVIP

缺陷生命周期手册 Introduction :引言 Bug can be defined as the abnormal behavior of the software. No software exists without a bug. The elimination of bugs from the software depends upon the efficiency of testing done on the software. A bug is a specific concern about the quality of the Application under Test (AUT). 缺陷可以被定义为软件的异常行为。 不存在一个缺陷的软件是不存在的。 消除软件缺陷 依赖于高效率的 测试 。一个缺陷对于在测软件来讲是不容小视的。 Bug Life Cycle: 缺陷生命周期 In software development process, the bug has a life cycle. The bug should go through the life cycle to be closed. A specific life cycle ensures that the process is standardized. The bug attains different states in the life cycle. The life cycle of the bug can be shown diagrammatically as follows: 在软件开发过程中， 缺陷拥有自身的生命周期。 缺陷在走完其生命周期最终会关闭。 确 定的生命周期保证了过程的标准化。 缺陷在其生命周期中会处于许多不同的状态。 缺陷 的生命中期通过下图展示了出来： 注： 深绿色 状态为测试经理设置 浅绿色 状态为测试员设置 浅蓝色 状态为开发人员设置 缺陷各个不同的状态如下： 1. New 新建 2. Open 打开 3. Assign 指派 4. Test 测试 5. Verified 确认 6. Deferred 延期 7. Reopened 重新打开 8. Duplicate 重复 9. Rejected 拒绝 10. Closed 关闭 Description of Various Stages: 1. New: When the bug is posted for the first time, its state will be “NEW”. This means that the bug is not yet approved. 1.新建：当缺陷被第一次递交的时候，它的状态即为 新建“ ”。这也就是说缺陷未被确认 其是否真正是一个缺陷。 2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as “OPEN”. 2. 打开：在测试者提交一个缺陷后，测试组长确认其确实为一个缺陷的时候他会把状态 置为 “打开 ” 3. Assign: Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or developer team . The state of the bug now is changed to “ASSIGN”. 3. 分配：一旦缺陷被测试经理置为 “打开 ”，他会把缺陷交给相应的开发人员或者开发组。 这时缺陷状态变更为 “分配 ”。 4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for ne