Guidelines on deciding the Severity of Defect
Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects.
A sample guideline for assignment of Priority Levels during the product test phase includes:
1. Critical / Show Stopper — An item that prevents further testing of the product or function under test can be classified as Critical Defect. No workaround is possible for such defects. Examples of this include a missing menu option or security permission required to access a function under test.
2. Major / High — A defect that does not function as expected/designed or cause other functionality to fail to meet requirements can be classified as Major Defect. The workaround can be provided for such defects. Examples of this include inaccurate calculations; the wrong field being updated, etc.
3. Average / Medium — The defects which do not conform to standards and conventions can be classified as Medium Defects. Easy workarounds exists to achieve functionality objectives. Examples include matching visual and text links which lead to different end points.
4. Minor / Low — Cosmetic defects which does not affect the functionality of the system can be classified as Minor Defects.
Related posts:
- Guidelines on writing Defect Description Defect can be expressed as “Result followed by the...
- How can one map a single defect to more than one test script? Using the ‘associate defect’ option in TestDirector one can...
- How will you generate the defect ID in Quality Center? The Defect ID is automatically generated after clicking Submit...
- What is a Test strategy? A test strategy is a document outline that describes the...
- How to ensure that there is no duplication of bugs in Quality Center? In the defect tracking window of QC, there is...
Related posts brought to you by Yet Another Related Posts Plugin.