bug级别分类

2014-10-20 10:02 6403人阅读 评论(0) 收藏 举报
 分类：

版权声明：本文为博主原创文章，未经博主允许不得转载。

 

目录(?)[+]

 

由于要做bug数据分析，要了解缺陷管理系统的分类方法，去网上搜索到如下分类法：

英文参考：

BUG的严重级别分类

Severity

This field describes the impact of a bug.

Blocker: Blocks development and/or testing work

Critical: crashes, loss of data, severe memory leak

Major: major loss of function

Minor: minor loss of function, or other problem where easy workaround is present

Trivial: cosmetic problem like misspelled words or misaligned text

Enhancement: Request for enhancement

 

Difference between priority and severity?

"Priority" is associated with scheduling, and "severity" is associated with standards. "Piority" means something is afforded or deserves prior attention; a precedence established by order of importance (or urgency). "Severity" is the state or quality of being severe; severe implies adherence to rigorous standards or high principles and often suggests harshness; severe is marked by or requires strict adherence to rigorous standards or high principles, e.g. a severe code of behavīor. The words priority and severity do come up in bug tracking. A variety of commercial, problem-tracking/management software tools are available. These tools, with the detailed input of software test engineers, give the team complete information so developers can understand the bug, get an idea of its 'severity', reproduce it and fix it. The fixes are based on project 'priorities' and 'severity' of bugs. The 'severity' of a problem is defined in accordance to the customer's risk assessment and recorded in their selected tracking tool. A buggy software can 'severely' affect schedules, which, in turn can lead to a reassessment and renegotiation of 'priorities'


 
 
 
另一个关于“严重级别”和“优先级”的回帖
In layman terms, we can say Severity means how much the bug is impacting the system.
Priority means how quickly it should be resolved. It doesn't mean always that high severity bug is always high priority.
Let's say an example where your report application crashes if you will take print out of the same during third try without closing the application.
In this case your bug is of critical severity but the priority to resolve it is low. As in real scenario this will happen rarely.
Take another example, where in company web site. Logo of the company is not proper but your application is working fine. In that scenario it is low severity bug but priority is highest.
 
BUG的严重级别的分类被分的很详细，Blocker是最严重的情况，包括阻碍测试的执行、大部分测试用例无法执行，这个时候可以直接把版本打回去。Critical是灾难性的BUG，必须立刻通知告知开发人员进行修改，但对其他测试用例的执行影响不大。Major是执行有效测试用例时发现的比较严重的BUG。Minor是执行无效测试用例时发现的比较严重的BUG。Trivial是易修改功能影响不大的BUG，Enhancement是对某项功能点表象的建议修改，可改可不改，或者有新的功能建议，严重级别最低。
严重级别和优先级的区别
大部分情况下严重级别高的应该优先解决，但也会根据版本的发布情况将严重级别高的设置为优先级别低的，也有可能非常严重但很容易修改也可以设置优先级别低的。
 
中文参考：

7级分类法

      Blocker级别——中断缺陷
          客户端程序无响应，无法执行下一步操作。
    Critical级别――临界缺陷，包括：
          功能点缺失，客户端爆页。
    Major级别——较严重缺陷，包括：
          功能点没有满足需求。
    Normal级别――普通缺陷，包括：
                    数值计算错误
                    JavaScript错误。
   Minor级别—一次要缺陷，包括：
                    界面错误与UI需求不符。
                    打印内容、格式错误
                    程序不健壮，操作未给出明确提示。
  Trivial级别——轻微缺陷，包括：
                    辅助说明描述不清楚
                    显示格式不规范，数字，日期等格式。
                    长时间操作未给用户进度提示
                    提示窗口文字未采用行业术语
                    可输入区域和只读区域没有明显的区分标志
                    必输项无提示，或者提示不规范。
 Enhancement级别——测试建议、其他（非缺陷）
                    以客户角度的易用性测试建议。
                    通过测试挖掘出来的潜在需求。
 
5级分类法
 
A类---导致系统崩溃、死机；出现不可挽救的数据丢失或损坏、内存泄露
B类---导致程序模块丢失或未实现；软件错误导致数据丢失；用户需求未实现
C类---发现影响被测功能正确实现的问题
D类---一般性错误或者功能实现不完善等
E类---一些建议性的错误
 
附图表：