Testers do lag in fixing bugs as they don't find a definite way for fixing errors. Many times; bugs brings in commotion as each one in the team carries their own opinion about fixing bugs, sometimes testers give high priority to a particular issue where others go up against it to justify themselves saying it is less important. This is an instant where entire team of developers and testers should show unity with a single thought to improve the testing process and to stay away from bugs and “prioritization”
is the only way to do so.
Importance of priority and severity
Bug fixing is an art to be done seamlessly by which customer's expectation can be met. Priority and severity goes hand in hand to give the excellent metrics and to identify overall health of the Project, it also plays a significant role in effective debugging.
Probability and impact is taken as key point to reduce the risk factor in general.
Risk Value = Probability x Impact
In the same way when it comes to bug reduction severity and priority value is considered.
Priority = Severity Value x Priority Value (In case of bugs)
Each error has its own criticality and it is not a single error that occurs hence priority is given based on the complexity of bugs which can put down the speed of an application and here is the detailed process of prioritizing bugs as quoted in Softwaretestingstuff.
Client's expectation differs from each therefore only after a brief interaction with client and after making a study about the business flow implemented in the application priorities should be made. It is advised to have a triage meeting so that everyone can provide their inputs to identify the correct severity level to set priority.
Consult a business analysis for setting four priority levels: Critical, High, Medium, low. Set them values as 4, 3, 2, 1. 4 as Critical and 1 as low.
2) Setting Severity
Severity is customer-focused and it is a fundamental measure of a bug or a failure. Many ranking schemes exist for defining severity. Assigning Severity for a bug is done straightforward.
Using some general guidelines about the project, testers will assign severity, but severity of the bug is one of the factors for assigning priority for a bug. Set four severity levels: High, Medium, low, lowest. Set their values as 4, 3, 2, 1. 4 as highest and 1 as lowest.
For best results, this exercise can be practiced before 5 to 7 days of product release. Also for all customers reported bugs during UAT or post production release.
Eventually we need not practice this method at all instants especially in the initial stage after development.
Bug with highest priority should be fixed first. In this case bug “Bug_4” should be fixed first. Then Bug_1 and Bug_5 should be fixed as shown above.