Scribd
Upload
2 views12 pages

Bug Life Cycle

The document outlines the concepts of severity and priority in the bug life cycle, defining severity as the impact of a defect on software functionality and categorizing it into levels such as Critical, Major, Moderate, and Minor. It also explains priority as the urgency of fixing defects, with examples illustrating the relationship between severity and priority levels. The document provides specific scenarios to clarify how different severity and priority combinations affect the handling of software defects.

Uploaded by

avrrohith
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views12 pages

Bug Life Cycle

The document outlines the concepts of severity and priority in the bug life cycle, defining severity as the impact of a defect on software functionality and categorizing it into levels such as Critical, Major, Moderate, and Minor. It also explains priority as the urgency of fixing defects, with examples illustrating the relationship between severity and priority levels. The document provides specific scenarios to clarify how different severity and priority combinations affect the handling of software defects.

Uploaded by

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

Bug Life Cycle

Check!!

✓ What is Error?

✓ What is Defect ?

✓ What is Bug?
Types of Testing
Bug Life Cycle
What is Severity?

❑ Severity is a measure or parameter which indicates the


impact of the bug in the software.

❑ Severity means how severe the defect is affecting the


functionality.

❑ It is usually categorized into several levels to help assess


how severely the issue affects the system and the user
experience. Common severity levels include:
Severity Levels
Severity levels

❑ Critical: Defects that cause the software to crash or lead to data loss, making the application
unusable.

Example: A login screen that consistently crashes upon entering valid credentials.

❑ Major/High: Major issues that significantly impact functionality or usability but do not
make the software entirely unusable.

Example: In an e-commerce application, customers cannot add items to their shopping cart.
Severity levels

❑ Moderate/Medium: Defects that affect the software's usability or functionality


but have reasonable workarounds.

Example: An online form that occasionally fails to submit, but retrying usually works.

❑ Minor/Low: Minor issues that do not severely impact functionality or usability and are
often cosmetic.

Example: A typo in a non-essential part of the application.(spelling mistakes)


Priority and its Levels
➢ Priority is a parameter to decide the order in which defects should be fixed.

➢ Priority means how fast/urgently the defect has to be fixed.


Severity and Priority Levels

❑ Severity: Critical | Priority: Critical/Immediate


Example:

➢ A critical security vulnerability is discovered in an e-commerce website that allows


unauthorized access to customer payment information. Immediate action is required to
prevent a potential data breach and financial loss.

❑ Severity: High | Priority: High

Example:

➢ The products added to the cart of an e-commerce website are not visible on the
payment page.

➢ The login button of the application is not working.


Severity and Priority Levels
❑ Severity: Moderate/Medium | Priority: Medium

Example: A bug is found in a social media app where users sometimes experience
a slight delay in loading their newsfeed. While it's an annoyance, it doesn't render
the app unusable. The fix is scheduled for the next regular app update.

❑ Severity: Minor/Low | Priority: Low

Example: In a word processing software, there's a minor formatting issue where


line spacing isn't consistent when using a specific font style. It doesn't affect the
core functionality and is considered a low priority, slated for a future update
Severity and priority levels
Severity: High| Priority: Low

Example: Application is working fine on latest versions of browsers but on


older version not inter-actable or user friendly. This is high severity bug which
affects the functionality and people of using older versions could be low.

Severity: Low | Priority: High


Example: Logo mismatch is also an example. It doesn’t affects the
functionality of an application, but still we have to give priority to our
client/customer so it’s an example for low severity and high priority defect.

You might also like