Understand Severity And Priority Of A Defect In Software Testing

Hello Folks,

In this post, we will see an important concept of manual testing which is also a frequently asked interview question for both freshers and experienced. We will understand below points:

  • What do you understand by severity and priority of a defect?
  • Differentiate between severity and priority.
  • Types of severity and priority.
  • Who decides severity and priority?
  • Key factors in deciding severity and priority

Define severity and priority: 

A defect has many attributes and “Severity” and “Priority” are one of them. Normally tester always gets confused in deciding severity and priority of a defect. We can define severity and priority as below:

  1. Severity: It is a question which asks “How critical defect is?”.
  2. Priority: It is a question which asks “How soon it should be fixed?”.

I hope you can now differentiate between terms “Severity” and “Priority”.

Types of Severity and Priority:

If we talk at a very high level, Severity and Priority are only two types:

Severity:

  1. High Severity
  2. Low Severity

Priority:

  1. High Priority
  2. Low Priority

But it will be very difficult to decide proper severity and priority of a defect. You may find some defect which is neither at high severity nor low severity. That is the reason you will find many organization has further categorized types of severity and priority as below:

Severity:

  1. Blocker
  2. Critical
  3. High
  4. Moderate
  5. Minor

Priority:

  1. High
  2. Medium
  3. Low

Note: These types may vary organization by organization and project by project. You may find more or less categorization.

Who decides Severity and Priority of a defect?

This is most confusing thing. Ideally tester needs to provide only severity of a defect while priority of a defect should be decided by developers. But you will see in many organizations both attributes are given by testers. In mid-sized and small companies you can see that a developer, testers and product owner decides these attributes after discussion. These practices differ from organization to organization.

How to decide Severity and Priority of a bug?

There are many driving factors of deciding severity and priority of a defect. I can list some below:

  1. Which testing methodology is being used: Traditional SDLC models are not quick as Agile and DevOps mythologies. Severity and priority may differ in both because you have more time in traditional SDLC and product might not be in production.
  2. Testing Phase: Severity and priority of a defect found in early phase of testing will be different from later phase of testing.
  3. Environment: QA, Staging, Mainline or Production defects will have different strategies of deciding severity and priority of defect.
  4. Functionality and Modules
  5. Timeline, budge and resource availability.

 

All above points are totally based on my corporate experience as I have worked in MNCs to startups. Others might have different options. It will be good if you can share them in comment section.

If you have any doubt, feel free to comment below.
If you like my posts, please like, comment, share and subscribe.

#ThanksForReading
#HappyTesting

Author: Amod Mahajan

My name is Amod Mahajan and I am an IT employee with 4+ years of experience in Software testing and staying in Bengaluru. My area of interest is Automation testing. I started from basics and went throw so many selenium tutorials. Thanks to Mukesh Otwani as his tutorials are easy and cover basics to advance. I have habit of exploring concepts by deep diving. I used to make notes. I thought of sharing my knowledge through posts and now I am here. #KeepLearning #ShareLearning