Monday, March 29, 2010

Severity and Priority of Bugs

SEVERITY- is the state or quality of being severe. Severity tells us HOW BAD the BUG is. It defines the importance of BUG from FUNCTIONALITY point of view and implies adherence to rigorous standards or high principles. Severity levels can be defined as follows:

Urgent/Show – stopper: Like system crash or error message forcing to close the window, System stops working totally or partially. A major area of the users system is affected by the incident and It is significant to business processes.


Medium/Workaround: When a problem is required in the specs but tester can go on with testing. It affects a more isolated piece of functionality. It occurs only at one or two customers or is intermittent.


Low: Failures that are unlikely to occur in normal use. Problems do not impact use of the product in any substantive way. Have no or very low impact to business processes
State exact error messages.


PRIORITY means something Deserves Prior Attention. It represents the importance of a bug from Customer point of view. Voices precedence established by urgency and it is associated with scheduling a bug Priority Levels can be defined as follows:


High: This has a major impact on the customer. This must be fixed immediately.


Medium: This has a major impact on the customer. The problem should be fixed before release of the current version in development or a patch must be issued if possible.


Low: This has a minor impact on the customer. The flaw should be fixed if there is time, but it can be deferred until the next release.

No comments:

Post a Comment