Today we will learn about Priority & Severity with live example and interview question with answer...
Priority :
Priority defines how important the bug is. This field describes the importance and order in which a bug should be fixed. The available priorities range from P1 (Most Important) to P5 (Least Important)
“The Order in which the defect should be fixed.”
Severity:
“The Order in which the defect should be fixed.”
Severity:
Severity defines how severe the impact is on the system of the bug.
“How critical the defect is.”
Following are the list of Severity Levels and meaning of each level:
1. Blocker [P1] - Blocks development and/or testing work
2. Critical [P1] - Crashes, Loss of Data, directly impacts on the required functionality
3. Major[P2] - Major loss of function, directly impacts on the required functionality
4. Normal[P3] - Slight deviation from the required functionality 5. Minor[P4]- Minor loss of function or problem where easy workaround is present
6. Suggestion[P5]- Proposal from Testing Team
Continuing....
“How critical the defect is.”
Following are the list of Severity Levels and meaning of each level:
1. Blocker [P1] - Blocks development and/or testing work
2. Critical [P1] - Crashes, Loss of Data, directly impacts on the required functionality
3. Major[P2] - Major loss of function, directly impacts on the required functionality
4. Normal[P3] - Slight deviation from the required functionality 5. Minor[P4]- Minor loss of function or problem where easy workaround is present
6. Suggestion[P5]- Proposal from Testing Team
Continuing....
No comments:
Post a Comment