It defines as the gravity of the bug on the system or application being tested.It refers the side effects of the bug on the system.
Majorly Severity can be categorized as:
Priority” means something deserves prior attention or associate with scheduling. It define the order in which developer resolve a bug. If the priority of the bug is high then bug will looked immediately or sooner and if priority is low it will be looked in future.
Priority can be categorized majorly as:
Example of High Priority and Low Severity defects: Suppose there is an web application and its logo name is misspelled then it will be an example of high priority and low severity because spell does not impact the user, it will impact the brand name.
Example Low Priority and High Severity defects: Suppose an application crashes on a particular scenario or event and occurrence of that particular scenario or event is very rare or less frequent so its a case of low priority and high severity.
High Priority and High Severitydefects: Suppose an e-commerce application hangs on adding multiple item on the cart then it will be a case of High Priority and High Severity defects.
Low Priority and Low Severity defects: If there is an application and inside the application site content is misspelled then it will be case of low priority and low severity