展望2011

2007-04-06 | BUG的严重级别分类【英】

上一篇 / 下一篇  2007-04-27 22:31:55 / 个人分类:提交BUG

51Testing软件测试网 Z"})?(R!E"}

Severity
M F~AL-d2OV051Testing软件测试网cu;U;z:MqrS5]
This field describes the impact of a bug.
3c-u5ZL/@0t!~J0
tDQhKb0Blocker : Blocks development and/or testing work
u`']nJH051Testing软件测试网 e pN1h/{+g
Critical : crashes, loss of data, severe memory leak
2p9JT6v.eJJ[0
6rCjDh;b)}:N0Major : major loss of function
;i6[ SL n.Z5l0
1HD"k{ j l.@)B%]0Minor : minor loss of function, or other problem where easy workaround is present
CY]*~~(ON0
2qS Q W k0Trivial : cosmetic problem like misspelled words or misaligned text
_ dx.kes#D0
1W9j2[ XW a|!C0Enhancement : Request for enhancement

[,RL A-q0 51Testing软件测试网h] h"W tF8E

 51Testing软件测试网O|a)l%B+{

51Testing软件测试网U/d kuDM5l(c z _

Difference between priority and severity?
yiU+x!@V`N+]0
g%S#px)F [bS-LU0"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'

"l7L `+B9ULn)h0

TAG: BUG 严重级别 提交BUG

我测故我在 引用 删除 caicai1724   /   2007-04-27 22:33:03
另一个关于“严重级别”和“优先级”的回帖
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.
我测故我在 引用 删除 caicai1724   /   2007-04-27 22:32:40
我的理解
BUG的严重级别的分类被分的很详细,Blocker是最严重的情况,包括阻碍测试的执行、大部分测试用例无法执行,这个时候可以直接把版本打回去。Critical是灾难性的BUG,必须立刻通知告知开发人员进行修改,但对其他测试用例的执行影响不大。Major是执行有效测试用例时发现的比较严重的BUG。Minor是执行无效测试用例时发现的比较严重的BUG。Trivial是易修改功能影响不大的BUG,Enhancement是对某项功能点表象的建议修改,可改可不改,或者有新的功能建议,严重级别最低。
严重级别和优先级的区别
大部分情况下严重级别高的应该优先解决,但也会根据版本的发布情况将严重级别高的设置为优先级别低的,也有可能非常严重但很容易修改也可以设置优先级别低的。其他情况我还没想到。
 

评分:0

我来说两句

Open Toolbar