Severity vs. Priority:
Severity -
“Seriousness of a Defect”
- Showstopper –
the most serious concern like a system crash, Corrupted data etc.
- Critical –
A significant concern (broken functionality without a workaround).
- Major –
A concern due to broken functionality but has a Workaround.
- Minor –
A lesser concern (broken functionality with a workaround).
- Trivial –
An insignificant concern (cosmetic).
Priority -
“Importance of a Defect”
- Urgent –
Highly visible and/or stops all project efforts
- High –
Stops some project efforts (and no workaround exists)
- Medium –
Slows project efforts (but a workaround exists)
- Low –
Barely visible and/or does not affect project efforts
Severity
|
Priority
|
Severity is used to determine the IMPACT of the defect on the application.
|
Priority is used to signify the LEVEL
OF URGENCY of fixing the defect
|
It’s like Effect of defect on application
|
It’s like how soon the defect has to be fixed.
|
It is defined by Software Tester
|
Initially defined by Tester and Finalized by Project/Tech Manager
|
Ranges from Show stopper to Cosmetic defect
|
Ranges from Urgent to Low
|
Defect Categorization
Category
|
Definition
|
Example
|
High Severity
High Priority
|
A bug that corrupts the
database, A bug results in 404 Error etc
|
Lift stops at 34th floor
instead of 30th floor
|
High Severity
Low Priority
|
Application crashes due to
weird testing, Crashes after 4000 sessions due to improper maintenance.
|
Banking site expiry screen
|
Low Severity
High Priority
|
Client names and Designations
are placed one for the other, Blunder spelling mistakes etc
|
Switching on the fan
switches the lights as well.
|
Low Severity
Low Priority
|
Grammatical errors, Alignment
issues, Some cosmetic issues are examples.
|
ABC.com is shown as abc.com.
|
Comments
Post a Comment
We appreciate your valuable Suggestions/Feedback