24 | Defect Severity and Defect Priority

Published on Aug 17, 2021 | By Tesvan team

Defect Severity

 

Every defect impacts on the system at some level. This impact is measured by the “Severity” parameter. Severity type is categorized by Software Tester based on the Test Case and functional / requirement understanding. It also  indicates the seriousness of the issue occurring on the application. Each Defect management tool categories Severity in different way.

   

Severity levels

A defect that completely crashes the system and Tester is no longer able to move further with the testing. In another scenario when whole feature / functionality is missing from the application, this can be considered as a Blocker defect. Almost all the time Blocker severity defects are having highest priority.


Critical Severity: A highly severe defect causing the system failure or functionality collapse. But user is able to access some of it’s functions or the same scenario is executable some other way. Almost all the time Critical severity defects are having highest priority.

Major Severity: Defect falling under Major severity is generally functionality specific defects. It does not cause any system failure kind of situation. But such defects are equally important and they should be resolved without any unnecessary delay.

Minor & Trivial Severity: Defects having small UI issues, spelling mistakes in content, minor alignment issues, color shades are reported as minor or trivial defects. These issues do not affect any of the functionality and keeping they open long time won’t make any difference.

  

Defect Priority

Priority is defined to set the order in which the reported defects should be resolved. Usually Priority is set by Software Tester or QA Lead and developers focus on higher priority defects first following the descending order. Priority can be categorized in three layers.

Priority levels

High Priority (P1): Defects falling under P1 category must be resolved and closed as soon as possible. Due to such defects testing of entire application is blocked and Tester can not move any further.

Medium Priority (P2): Once all the defects with High priority are resolved, next focus should be on Medium level defects. Normally functional defects such as a feature is not working as it is supposed to be, major cosmetics errors, validation errors are considered as Medium priority defects. Such issues don’t stop you to perform further testing.

Low Priority (P3): These defects are taken into consideration once all High & Major priority defects are resolved. Minor UI issues, spelling mistakes, alignment issues, color code mistakes should be considered as Low priority defects. In short, by providing Priority to a Defect we set the order in which all the reported defects to be resolved.

 

Examples

SCENARIO 1: HIGH PRIORITY & BLOCKER SEVERITY

  • A very common example, User is not able to Login into application with proper credentials. This is a very critical scenario which needs to be fixed as soon as possible.
  • In an E-Commerce website User is not able to add the produce into the Cart / not able to check-out for payment from the cart. If occurred on the live application, this issue can impact on the business at great level.
  • After registration, User is not getting the Link to complete the registration process.
  • System is crashed when providing invalid keywords (e.g: XSS scripts) in the Search box.

SCENARIO 2: LOW PRIORITY & LOW SEVERITY

  • Minor spelling mistakes on the pages like “Site Map”, “Career” or “Company Blog” pages.
  • Color of the button on About Us page is slightly different.
  • Minor alignment issues in the content of the Company Blogs page.

SCENARIO 3: HIGH PRIORITY & LOW SEVERITY

  • A very common example, “Company Logo” is not displayed as expected. This defect is not affecting any functional scenarios but it can impact on the company’s brand value. So, this issue should be fixed without any delay.

 

 

Useful links
1. Defect severity and priority article/eng/
2. Defect severity and priority article/rus/
3. Defect severity and priority video tutorial/eng/
4. Defect severity and priority video tutorial/rus/

Next Lessons


25 | Defect Report

Aug 17, 2021

Defect report is a document that identifies and describes a defect detected by a tester. The purpose of a defect report is to state the problem as clearly as po...

By Tesvan team

26 | Test Case

Aug 18, 2021

A TEST CASE is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The p...

By Tesvan team

27 | Test Script

Aug 18, 2021

Test Script A TEST SCRIPT is a set of instructions (written using a scripting/programming language) that is performed on a system under test to verify that the ...

By Tesvan team

28 | Test Plan

Aug 18, 2021

A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project.Test Plan tem...

By Tesvan team

29 | Agile model

Aug 18, 2021

Agile is a coding practice that follows the rules and principles of agile software development. In this Agile Tutorial, you will learn the fundamentals of Agile...

By Tesvan team

Interesting For You



09 | System testing

Aug 12, 2021 | By Tesvan team

System testing System testing is performed on a complete, integrated system. It allows checking system's compliance as per the requirements. It tests the overal...

37 | Git

Aug 19, 2021 | By Tesvan team

To transfer to the remote repository, run this command as well:git pushIn order, on the contrary, to get information from the remote repository to the local rep...