Choosing Between Severity & Priority While Bug Reporting
The terms severity and priority are the two attributes used with respect to bugs in order to share the importance of a bug among the team and to fix it. There is a very thin line between severity and priority in testing. A tester must know which bug is severe and which to be handled with priority. These metrics help to determine the overall health of the project severity by measuring how badly the deviation affects the build and the urgency of the fix required.
Written test cases and functionality are the two criteria of severity used by testers to define the severity type. For example when an Application crashes because a remote link is clicked, the instance of the user clicking the remote link is rare but the impact of this application crashing will be severe. Hence, the severity is high and priority is low.
Priority: indicates the time frame within which a defect must be fixed. If high priority is mentioned then developer has to fix that defect at the earliest as this priority status is set based on customer requirement. In the case of the home page of a company website-where the name is misspelled, the priority of the fix required will be high but its severity will be low.
Here are the main differences between severity and priority quoted by Inder P Singh, Senior Test Manager and Consultant at Software Testing Space:
Post your Comment
All form fields are required.