Severity and Priority

There are lot of confusion faced by beginners between Priority and Severity. Well, both the terms Priority and Severity are used in Bug Tracking in order to mention the importance of that bug to development team.

Severity: deals with the functionality of application
1. Severity status is used to explain how badly the deviation is affecting the build.
2. Severity type is defined by the Tester based on the written Test Cases and functionality.

Priority: deals with the customer requirement
1. Priority status is set by the Tester in order to let Developer know the time frame to fix a defect. If High priority is mentioned then the developer has to fix it at the earliest.
2. Priority status is set basd on the customer requirement.

Example: 

1) High Severity And Low Priority: If any application crashes after multiple use of any functionality (e.g. save Button use 200 times quickly then that application will crash)

Means High Severity because application chrashed but Low Priority because no need to debug right now you can debug it after some days (as its not a valid scenario because user is not going to click save button 200 times quickly)

2) High Priority And Low Severity: If any Website say "Yahoo" now if the logo of site "Yahoo" spells as "Yho" than Priority is high but severity is low.

Here the functionality of website is ok but it effect the name of the website so important to fix it quick ---Priority

Share this post