HOW TO DETERMINE PRIORITY OF THE SOFTWARE DEFECT?

by admin

Software Defect Priority can be classified into four categories as i stated below:
Priority 1 – Resolve Immediately:
Example: User unable to launch ‘Funds Transfer’ page in a Banking application. When user clicks on ‘Funds Transfer’ button from Banking application home page the ‘Technical Problems’ or ‘Page Not Found’ displayed to the user.
In this example software tester should report the defect as Severity 1 or Showstopper because the system/application under test is out of service. In other words there is no work around or not usable to use the system/application unless the developer fix the defect for further usable.
In this case software tester should deem this as a top priority or Priority 1 defect to resolve immediately.
Priority 2 – High Attention:
Example: User able to launch ‘Funds Transfer’ page in a Banking application successfully but the ‘Complete Transfer’ button not clickable to initiate funds transfer.
In this example software tester should report the defect as Severity 2 or Critical because the major function of the system/application under test not working. In other words the intent of the application functionality is not usable and no workaround exists to use the application functionality unless the developer fix the defect for further usable.
In this case software tester should deem this as Priority 2 or High Attention defect to resolve the defect at the earliest.
Priority 3 – Medium:
Example: User able to launch ‘Funds Transfer’ page in a Banking application successfully and ‘Complete Transfer’ button is clickable to initiate funds transfer. But the application allows to transfer the money upto $1000 and not more than $1000. As a workaround user has to initiate funds transfer 2 times in order to transfer $2000 with each transfer of $1000.
In this example software tester should report the defect as Severity 3 or Medium because major function of the system/application under test not working but there is a temporary workaround exists to use the system.
In this case software tester should deem this as Priority 3 or Medium because this defect may be considered acceptable by the business to proceed to production and address as a post production issue.
Priority 4 – Low:
Example: Cosmetic issues in the ‘Funds Transfer’ page like spelling mistakes, page format issues.
In this example software tester should report the defect as Severity 4 or Minor because whenever components of the application are not functioning to specification but the situation is manageable i.e fix can be instituted in a future release.
In this case software tester should deem this as Priority 4 or Low because this defect may be considered acceptable by the business to proceed to production and address as a post production issue.
 

Share this article

Leave a comment

Your email address will not be published. Required fields are marked *