Bug Severity Guide Lines

The Bug severity will display what is the impact on the SUT according to the QA tester.

In order to avoid miss understandings and inconsistencies it is best that a table of sort be presented and agreed upon between all QA testers and vs. the Development group.

please review such a table below:

Low

• GUI ‘cosmetics’
• General minor issues

Medium

• Missing\wrong messages
• Not perfect functionality
• GUI friendliness
• GUI - Spelling errors
• Documentation errors

High

• Feature malfunction
• ‘Bad’ errors messages
• Fields validation
• Translation problems
• Missing Install Shied
• Missing documentation
• Wrong version

Show Stopper

• System\Component Crash
• Data loss
• Missing Feature
• Security intrusion
• Performance failures
• Customer determination

QA Stopper

• Stops Testing progress

One can argue about the table above the only thing critical is to have such a table, and that all the relevant parties agree on it.

In a similar manner there must be a way to report the bug's priority according to project requirements.