缺陷(defect)

缺陷信息

1.缺陷编号

2.缺陷的状态

  new-新建

  open-打开

    reopen-关闭的缺陷-再次打开

  fixed-修复

  closed-关闭

  rejected-拒绝

  postpone-拖延

3.缺陷标题

4.严重程度

  5-critical-最高优先级

  4-VeryHight-非常高优先级

  3-hight-高

  2-medum-中

  1-low

5.缺陷优先级

  5-Urgent-最高

  4-VeryHight-非常高

  3-hight-高

  2-medium-中

  1-low-低

6.所属模块

7.缺陷的详细描述

缺陷报告注意事项

1.缺陷报告不能有缺陷

2.表达和描述简洁,准确

3.一个缺陷一个报告

4.缺陷一定是可重现的

5.避免出现模糊的词汇

6.不能有个人感情色彩

7.出现bug过程一定要详细

缺陷跟踪流程

1.new新建状态

  要提交一个缺陷,首先就是新建状态

2.open打开状态

  确认缺陷有效后,为打开状态

3.fixed修复状态

  由缺陷的处理人把缺陷处理完成之后设置为修复状态

4.closed关闭状态

  验证缺陷确实修复成功后,一般由缺陷的发起人设置状态为关闭状态

5.reopen重新打开状态

  一个已经关闭的缺陷再次出现,就要设置重新打开状态

缺陷分析需要注意的点

1.哪个模块问题最多

2.哪个测试工程师测试的缺陷最多

3.各类缺陷的数量占比

4.开发是否可以及时修复缺陷

5.开发人员一次修复缺陷占比

6.软件是否可以正常发布

————————

Defect information

1. Defect number

2. Defect status

New – New

Open open

Reopen – closed defect – reopen

Fixed – Fixed

Closed closed

Rejected rejected

Postpone delay

3. Defect title

4. Severity

5-critical-highest priority

4-veryhigt-very high priority

3-high-high

2-medum-medium

1-low

5. Defect priority

5-urgent-max

4-veryhigt-very high

3-high-high

2-medium

1-low-low

6. Module

7. Detailed description of defects

Precautions for defect report

1. The defect report shall be free from defects

2. The expression and description are concise and accurate

3. One defect and one report

4. Defects must be reproducible

5. Avoid vague words

6. No personal feelings

7. The bug process must be detailed

Defect tracking process

1. New status

To submit a defect, the first step is to create a new state

2. Open status

After confirming that the defect is valid, it is open

3. Fixed repair status

The defect handler sets the defect to repair status after the defect is processed

4. Closed state

After verifying that the defect is successfully repaired, the status is generally set to closed by the initiator of the defect

5. Reopen status

If a closed defect reappears, it is necessary to set the reopening state

Points needing attention in defect analysis

1. Which module has the most problems

2. Which test engineer tests the most defects

3. Proportion of various defects

4. Can defects be repaired in time

5. Proportion of defects repaired by developers at one time

6. Can the software be released normally