High Priority & Low Severity Bug
When on Home page of a website Name of site is wrong, it is low severity bug as it is not going to affect the major functionality but since it’s the home page of the website it may create bad impression on customers.
Here it should be High Priority.
High Priority & Low Severity
If we want to take a printout of a page or any document then if Printer doesn’t allow us take printout, it is a High Priority Bug as it is related to Functionality but since we can take the printout from another Printer or we if can change the configuration then it is Low Severity Bug as we are getting our work done anyways without letting it affected by malfunctioning of Printer
Defect severity determines the defect criticality whereas defect priority determines the defect immediacy or urgency of repair
1. High Severity & Low Priority: Suppose there is an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. In this application, there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request.
2. Low Severity & High Priority: Suppose there is a spelling mistake or content issue on the homepage of BT.com website which has daily laks of hits all over
3. High Severity & High Priority: Suppose there is an application which gives some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. In this application, there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will hamper the functionality of the application immediately within a week. It should be fixed urgently.
4. Low Severity & Low Priority: Suppose there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.
0 comments:
Post a Comment