Bug Severity and Priorities

Bug Severities and Priorities

Severity  Severity is defined as the characterize of impact a Defect has on the upshot or operation of a component application being tested.

 Higher enact on the system functionality will lead to the assignment of higher severity to the bug.
 Severity of the bug can be determined by combining:- Frequency of occurrence + brunt of the bug

Priority  Priority is defined as the procedure in which a defect should be hooked. Higher the priority the instantly the defect should be resolved.

Defects that leave the software system expandable are given higher priority over defects that cause a small functionality of the software to decline.

Defect priority can be categorized into three class:-

•       Low: The Defect is an irritant but repair can be done once the more serious Defect has been fixed.

•      Medium: During the normal course of the upshot activities defect should be resolved. It can wait until a advanced version is created.

•       High: The defect must be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed.

Highest /Showstoppers/Critical:- 

Any bug which breaks the application does not have a work around are marked as showstopper issues. These have very high impact on the application, user and the company. The severity may be so high that the build will need to have a full re-test once fixed.

Examples:-· Crash · Revenue related or affecting

High/Major:- Any bug that is not obvious and may or may not breaks the application is marked as high severity issues, but there exists an work around.

Example :  

• Error message display issue · 404 error 
• Redirection issue · 
• Social integration error · 
• Missing features/button

Medium: Any bug that does not break the feature/system but causes the system to produce incorrect, incomplete or inconsistent results.

Examples:-·

•  Layout issue · 
• Validation issue

Low/Minor/Cosmetic: The defect does not affect functionality or data. It does not even need a workaround. It is merely an inconvenience.

Examples:-   

• Font issue · 
• Color issue · 
• Hyperlink issue.
• Tool tip issue · 
• Fringe scenario (edge case)