0% found this document useful (0 votes)
26 views12 pages

Severity & Prioriry

The document outlines the concepts of severity and priority in bug tracking, defining severity as the impact of a bug and priority as the order in which defects should be fixed. It categorizes severity into six levels (blocker, critical, major, minor, trivial, enhancement) and priority into three levels (high, medium, low). Additionally, it provides examples of different combinations of severity and priority to illustrate their implications in software development.

Uploaded by

Akhil Suresh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views12 pages

Severity & Prioriry

The document outlines the concepts of severity and priority in bug tracking, defining severity as the impact of a bug and priority as the order in which defects should be fixed. It categorizes severity into six levels (blocker, critical, major, minor, trivial, enhancement) and priority into three levels (high, medium, low). Additionally, it provides examples of different combinations of severity and priority to illustrate their implications in software development.

Uploaded by

Akhil Suresh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

SEVERITY & PRIORITY

NOUFIA NAZAR
SEVERITY

 The impact of the bug on the application is


known as severity.
 It can be blocker ,critical ,major ,minor ,
trivial and enhancement for the bug.
 QA engineers determines the severity level of
the defect.
TYPES OF SEVERITY

• Blocker -blocks development and/or testing work


• Critical -crashes , loss of data ,severe memory
leak
• Major –Major loss of function (functionality defect)
• Minor –Minor loss of function (alignment issue)
• Trivial –Grammatical errors
• Enhancement –Request for improvment
PRIORITY

 It is defined as a parameter that defines the order in


which a defect should be fixed.
 Defects having a higher priority should be fixed first.
 It refers to how quickly the defect should be rectified.
 Types of priorities are high ,medium and low.
TYPES OF PRIORITY

 High –It is a major impact on the customer


application , and it has to be fixed first.
 Medium –In this the problem should be fixed before
the release of the current version in development.
 Low –The flow should be fixed if there is time , but it
can be deferred with the next release.
DIFFERENT COMBINATIONS OF
SEVERITY &PRIORITY

High severity and high priority

High severity and low priority

Low severity and high priority

Low severity and low priority


EXAMPLE FOR HIGH SEVERITY AND
HIGH PRIORITY

 In a web application , after filling the login details the


user cannot click the login button.
 The products added to the cart of an e-commerce
website are not visible on the payment page.
 A bug in an online banking app that prevents users
from making transfers potentially affecting
thousands of customers.
EXAMPLE FOR HIGH SEVERITY & LOW
PRIORITY

 In a photo editing app one filter is not working.


 Informative pages such as disclaimer and privacy
policy are crashing ,which may impact other major
system functionality .
 There are some buttons on the website which are
overlapping . Although clickable, are creating a fuss.
EXAMPE FOR LOW SEVERITY &HIGH
PRIORITY

 There is a spelling error in the name of google


on the home page ,it falls under the category
of high priority and low severity.
 The logo of the company’s welcome page is
distorted.
 The action buttons are not visually appealing
or the information on the page appears hazy.
EXAMPE FOR LOW SEVERITY & LOW
PRIORITY

 A spelling mistake on the page of the site which is


not frequently visited.
 The colour of any text does not match the theme of
the website.
 The error message displayed is incomplete stating
“you have registered success” instead of the correct
phrase “successfully” to confirm the registration.

You might also like