Quality is delighting customers
Low Severity and High Priority: If a company logo is not properly displayed on their website.
Low Severity and Low Priority: There is mistake like “You have registered success” instead of successfully success is written.
High Severity and Low Priority: If we have a typical scenario in which application gets crashed, but that scenario exists rarely.
High severity and High Priority: A show stopper bug due to which we are unable to proceed our testing.
Example: High Priority and Low Severity Defect
Suppose in one banking application there is one module ATM Facility. in that ATM facility when ever we are dipositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly with out any mistake means only missing of message . in this case as it is happenig properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be confuse for this.
high priority means developer will fix critical issue
Low severity bug means tester will raise minor issue.
High Priority: Is something like for example in your application the home page having any important link .While you click the link the page shows unexpected error and not loading the page. This is a high priority bug.
Low Severity bug: Is something like for example in your application some inner page displaying contents having any spelling mistake or font change .This we can say Low Severity.
Great explanation Rakesh!
Severity and priority in few words:
Severity - based on the defects functional impact on the application
Priority - based on the business impact of the issue
High priority: Developer has to fix the issues immediately.
low severity: Developer can fix the we he has the time.
Check this out