Software Testing Tutorial#43 - Severity and Priority in Software Testing

In this Software Testing Tutorial, we will learn about Severity and Priority in Software Testing. Severity indicates how bad the defect is and what is the impact of the defect on the software, whereas the priority determines the urgency of fixing the defect.

Defect severity is assigned by the software testers and priority is mostly assigned by Product owners or person who represents business or customer. Defect severity and priority are very important information to be assigned to defects so that development team can understand the order in which they need to fix the defects.

Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links.

Help me in spreading the knowledge, please hit LIKE, SHARE, and SUBSCRIBE for the latest tutorials. More tutorial playlists below:

🔶 ENROL IN MANY FREE TRAININGS ON RCV ACADEMY PORTAL 🔶

🔶 FOLLOW US ON TWITTER 🔶

🔶 LIKE US ON FACEBOOK 🔶

🔶 OUR TUTORIAL WEBSITES 🔶

🔶 GET MY TRAININGS ON UDEMY 🔶

#SoftwareTestingTraining #SoftwareTestingTutorial #SoftwareTestingBootcamp #SoftwareTesting #QA #QATraining #QATutorials #RcvAcademy #SoftwareTestingMentor

[manoj_mafiosi]

**Notes: Severity and Priority in Software Testing - Software Testing Tutorial #43**


**Understanding Severity:**
- Severity measures how severe or impactful a defect is on the software.
- Similar to assessing pain levels; minor issues have low severity, while critical problems have high severity.
- Assigned by testers based on how much the defect disrupts functionality or testing.

**Understanding Priority:**
- Priority indicates how urgently a defect needs to be addressed and fixed.
- It determines the order in which defects should be resolved, based on time.
- Labeled using categories like P1 (immediate), P2 (high), P3 (medium), and P4 (low).

**Assigning Severity and Priority:**
1. **Critical Defects (S1, P1):**
- Highest severity and priority.
- Block crucial functionality or crash the software.
- Demand immediate resolution.

2. **Low Severity, High Priority (e.g., S3, P1):**
- Low severity but high priority.
- May include minor issues with a significant impact on reputation.
- Require immediate attention.

3. **Medium Severity and Priority (e.g., S2, P2):**
- Many defects fall into this category.
- Neither critical nor minor but need timely resolution.
- Assigned medium priority (P2).

4. **Low Severity and Priority (e.g., S4, P3):**
- Minimal impact and no hindrance to critical functionality.
- Low in both severity and priority.
- Assigned low priority (P3).

**Conclusion:**
- Severity measures the impact of a defect, while priority determines how soon it should be fixed.
- Assigning severity and priority guides development teams on issue resolution.

[mazharkhatri]

Nice and informative video
Can you make a video defects severity and priority for AzDo?

[divyagupta]

Very well explained sir👍 sir can you take my mock interview for manual testing(fresher) please

[sumnareddy]

Got my doubt cleared ..Thank you..can you plese take mock interview for me as 3 years of fake experience

[gauravchugh]

Sir who decides priority, tester or developer?

[YOGESHKHAIRNAR]

While Bug Severity and Priority are important and plays a critical role in the decision making, we need keep in mind few things mentioned here

[yitingchen]

severity(嚴重性):
priority(優先序): 對於軟體出現的錯誤，有多緊急要去處理它。