How to Decide Test Case Priority

Let’s see, How can you decide Test Case Priority. Assigning priorities to test cases is ultimately a subjective process that relies on QA Engineers to use their judgment based on past experience and their knowledge of customer usage of the product under test.

In light of the subjective nature of this process, the following are recommended guidelines for assigning test case priorities.

 

When assigning test case priorities consideration should be given to the following questions:

  1. If the test cases fail what would be the severity & priority of the resulting bug report?
  2. If the test case were failing late in a release cycle what would be the action was taken for the bug (e.g. hold up the release, defer to 1st maintenance release with release note/KB, defer to future release without release note/KB)
  3. How many steps or conditions do the test case stray from the expected primary use cases for the feature?
  4. Should the test case be included as part of the feature handoff/demo from Development?

 

Priority 0 test cases

  1. Would result in a critical bug with showstopper/test-stopper priority when failing (e.g. testing for the feature cannot proceed).
  2. Would hold up a release if failing.
  3. Cover the default or primary path/use case for the feature.
  4. Would be included as part of the feature handoff/demo.

 

 

Priority 1 Test Cases

  1. Would result in a critical/severe bug with immediate or pre-release priority when failing.
  2. Could possibly hold up a release if failing but also may be deferred and documented with a release notes/KB entry.
  3. Cover minor deviations from the primary use cases for the feature.
  4. Would not be included as part of the feature handoff/demo.

 

Priority 2 Test Cases

  1. Would result in a severe/non-critical bug with post-release priority when failing.
  2. Would not hold up a release and most likely would not be documented with a release notes/KB entry.
  3. Cover severe deviations from the primary use cases for the feature such as boundary conditions and negative testing.
  4. Would not be included as part of the feature handoff/demo.

 

 

0 Comment

Leave a Reply