Monday, April 25, 2016

Severity and Priority of bug


Every bug has two fields called as severity and priority that has always confused most of testers. 
Let us understand them with simple examples.

Severity 
It means how severe is the impact of bug on application.

Priority
It means how soon bug should be fixed.

Now we can four combinations of severity and priority.

High Priority & High Severity
Consider an application that maintains student details, and when new record is created application terminates abruptly.

High Priority & Low Severity
The spell mistakes that happens on the cover page or title of an application or company logo is missing.

Low Priority & High Severity
A feature that is rarely used in application is broken, say application has annual report feature but it picks wrong months like from Jan to Dec instead of April to March.

Low Priority and Low Severity
Any spell issues which is with in a paragraph or in alternate text of image.


No comments:

Post a Comment