Severity and Priority are one of the most common terms used in software testing. Today we will discuss the core concepts and differences with a simple real-life example. So let's get to the point.

Severity refers that how much impact the defect/bug is creating when we are testing the application. A bug having a higher severity level means it has a higher negative impact on the user experience for the system.

On the other hand,

Priority means in which order we should follow to fix the detected bug/defect. When a bug is set as a higher priority it means the bug should be fixed as soon as possible.

• Usually, the project manager sets the Priority level, and the tester sets the Severity level.

Still, if you have confusion about severity and priority then let's see an example below:

Suppose we have an application in which we have a feature named Privacy Policy. Every time we click on the privacy policy section, every time the page is not displaying. So we can call it as high severity as it is giving a bad user experience when the users are using it. But people are hardly interested to read any kind of statement or document. So here we can set it as a low priority.

Now I think it's pretty much clear to you now. Any kind of suggestion is highly appreciable. Keep learning.