Scribd
Upload
40 views1 page

Quality Center Priority and Severity Levels

Scenarios and defects will be ordered by their priority and severity levels respectively. There are four levels for both: low, medium, high, and critical, with critical being the highest. Low priority scenarios test non-essential features while critical scenarios test essential components. Similarly, low severity defects have minimal impact and workarounds while critical defects prevent testing due to major broken components.

Uploaded by

Rda Shahul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
40 views1 page

Quality Center Priority and Severity Levels

Scenarios and defects will be ordered by their priority and severity levels respectively. There are four levels for both: low, medium, high, and critical, with critical being the highest. Low priority scenarios test non-essential features while critical scenarios test essential components. Similarly, low severity defects have minimal impact and workarounds while critical defects prevent testing due to major broken components.

Uploaded by

Rda Shahul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Quality Center Priority and Severity Levels

Scenarios will be ordered by Priority levels.


Defects will be ordered by Severity levels.
Scenario Priority Description
1 - Low
A low priority scenario tests features that may or may not
be specifically identified in business requirements. A failed
low priority scenario can result in a lower-quality customer
experience, however should not have an impact to
business.
2 - Medium
A medium priority scenario tests a system function or sub-
function identified in the business requirements. A failed
medium priority scenario could result in an impact to a
portion of the business, with some financial, quality and
customer service implications.
3 - Hi!
A high priority scenario tests a maor system component
that is significant in meeting business requirements. A
failed high priority scenario could result in a significant
impact to business, with financial, quality and customer
service implications.
" - Critical
A critical priority scenario tests a maor system component
that is essential in meeting business requirements. A
failed critical priority scenario could result in a maor
impact to business, with financial, quality and customer
service implications.
De#ect Severity Description
1 - Low
A minor issue that imposes minimal loss of functionality,
but for which there is an acceptable and easily
reproducible wor!around. "esting or system processing
can proceed without interruption. "his should be resolved
if#when there is time, but it may be deferred until the next
release at the business sta!eholder$s discretion.
2 - Medium
A significant issue where a smaller piece of functionality or
smaller system component is not wor!ing properly. "he
testing or system processing can continue. "his should be
resolved before release of the current version in
development, or a patch must be issued if possible.
3 - Hi!
A maor issue where a large piece of functionality or maor
system component is not wor!ing properly. "here is a
wor!around% however, and testing or system processing
can continue. "his must be resolved as quic!ly as
possible.
" - Critical
A maor issue where a large piece of functionality or maor
system component is completely bro!en. "here is no
wor!around and testing or system processing cannot
continue. "his must be resolved immediately.

You might also like