|
Severity & Priority in software testing
Severity
refers to the level of impact, the defect has created on the users. Say
If a particular defect has occured in an application and if more than
80% of the users are affected by the defect, the defect type is
"Critical
Similarly if only 50% of the users are affected, in such cases the severity of the incident can be treated as "Seroius".
However priority refers to the "Urgency" with which the incident has to be fixed.
In most of the cases a critical incident can be of high priority, however the vice versa need not be true.
For example a user might request the support team member to
change the font size and font color of the text in a web page and in
this case for the user, it might be of high priority, however it is not
a critical or serious incident.
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
|
http://
http://
Contributed by:
Rohit kakria
I am software developer, moderator of xpode.com
Resourse address on xpode.com
http://www.xpode.com/Print.aspx?Articleid=15
Click here to go on website
|