优秀是一种习惯,生命是一个过程,不求进步很大,只求每天进步一点点,无为之道!

BUG的严重级别分类

上一篇 / 下一篇  2007-12-19 13:18:10 / 个人分类: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是对某项功能点表象的建议修改,可改可不改,或者有新的功能建议,严重级别最低。
严重级别和优先级的区别
大部分情况下严重级别高的应该优先解决,但也会根据版本的发布情况将严重级别高的设置为优先级别低的,也有可能非常严重但很容易修改也可以设置优先级别低的。其他情况我还没想到。

TAG: BUG

寒舍 引用 删除 glf_0061   /   2007-12-21 23:20:00
啊!怎么办?看的我晕乎晕乎的哦。
 

评分:0

我来说两句

日历

« 2024-05-01  
   1234
567891011
12131415161718
19202122232425
262728293031 

我的存档

数据统计

  • 访问量: 7595
  • 日志数: 10
  • 书签数: 4
  • 建立时间: 2007-12-10
  • 更新时间: 2007-12-20

RSS订阅

Open Toolbar