• Home
  • Severity and Priority in Software Testing

There are two key things in defects of the software testing
1) Severity
2) Priority

What is the difference between Severity and Priority?

The impact of the bug/defect on the application is known as the severity. It is the extent to which the defect can affect the software. In other words, it defines the impact that a given defect has on the system.

Types of Severity
There are four different levels of severity.
1.    Critical
2.    Major
3.    Minor
4.    Low

πŸ“Œ Critical
A defect that completely blocks the testing of the product/feature is a critical defect. If the application crashes or becomes unusable/not able to proceed further, the defect could be classified under critical severity.

πŸ“Œ Major
Any Major feature implemented that is not meeting the customer’s requirements/use case(s) and behaves differently than expected, can be classified under Major Severity.

πŸ“Œ Minor
A medium defect appears when the product or application doesn’t meet certain criteria or still exhibits some strange behaviors, however, the functionality as a whole is not impacted and can be classified under Minor Severity.

πŸ“Œ Low
Any corrective defects including spelling mistakes or alignment issues or font casing can be classified under Low Severity.

Priority of a defect is related to how quickly a bug should be fixed and deployed to live servers. When a defect is of high severity, most likely it will also have a high priority.
The higher the priority the sooner the defect should be resolved.
Likewise, a low-severity defect will normally have a low priority as well.

πŸ“Œ Low: 
The defect is an irritant that should be repaired, but repair can be deferred until after more serious defects have been fixed.

πŸ“Œ Medium: The defect should be resolved in the normal development activities. It can wait until a new build or version is created.

πŸ“Œ High: The defect must be resolved as soon as possible because the defect is affecting the application or the product severely. The system cannot be used until the repair has been done.

Below are the examples for different combinations of priority and severity
1.    π—Ÿπ—Όπ˜„ π—½π—Ώπ—Άπ—Όπ—Ώπ—Άπ˜π˜†-π—Ÿπ—Όπ˜„ π˜€π—²π˜ƒπ—²π—Ώπ—Άπ˜π˜† β€“ A spelling mistake in a page not frequently navigated by users.
2.    π—Ÿπ—Όπ˜„ π—½π—Ώπ—Άπ—Όπ—Ώπ—Άπ˜π˜†-𝗛𝗢𝗴𝗡 π˜€π—²π˜ƒπ—²π—Ώπ—Άπ˜π˜† β€“ Application crashing in some very corner case.
3.    π—›π—Άπ—΄π—΅ π—½π—Ώπ—Άπ—Όπ—Ώπ—Άπ˜π˜†-π—Ÿπ—Όπ˜„ π˜€π—²π˜ƒπ—²π—Ώπ—Άπ˜π˜† β€“ Slight change in logo color or spelling mistake in the company name.
4.    π—›π—Άπ—΄π—΅ π—½π—Ώπ—Άπ—Όπ—Ώπ—Άπ˜π˜†-𝗛𝗢𝗴𝗡 π˜€π—²π˜ƒπ—²π—Ώπ—Άπ˜π˜† β€“ Issue with login functionality.

Omer Khan

Leave Comment