What is Bug ? Benefit PM understand Bug Life Cycle to prioritize task

Bug

Bugs are any form of non-compliance with the implementation of the product development plan.

Bug Life Cycle

In software testing, the Bug Existence Cycle is the exact collection of phases that a defect or bug goes through throughout its life. The goal of the defect life cycle is to make the defect repair process predictable and efficient by readily coordinating and communicating the current status of the defect as it changes to multiple assignees. (https://www.guru99.com)

Bug Life Cycle

1. Bug Found -> Bug reported by QA
2. QA Lead Review the Bug -> in this section QA Lead will decided this report is duplicated or not ? in scope or not ? and duplicated or not ?
3. Then QA Lead, Dev Lead, and/or PM can decided the bug can be fixed directly or not if not there are several decision such as :

• To fix update -> means the bug that we have reported will be fixed in the next SDLC.
• Will Not Fix -> The bug that we have reported will not be fixed it can be considered not enough time, the risk of other bugs appearing, repair is too difficult and minor bugs
• Not a bug-> the bug that we reported, was not a bug.
• Cannot reproduce -> the bug doesn’t appear when the developer rechecks from the step we reported

4. Then if developer fix the bug then QA will recheck again if the bug still open then will back again to the developer until the bug status is closed

Bug Priority and Bug Severity

Bug Priorities are those that must be addressed depending on priority handling and completion time.

Bug Severity is a bug that has to be corrected depending on the degree of harm to the program and its usability.

What is the difference?

Bug Priority

• Purpose -> specify the order in which the developer must resolve defects
• Category -> Low, Medium, High
• Actionable -> indicates how quickly the bug should be fixed
• Perspective -> Business Value and Priority Status based on customer needs

Bug Severity

• Purpose -> degree of impact of defects on the operation of the product
• Categories -> Critical, Major, Medium, Minor, Cosmetic
• Actionable -> shows the seriousness of the defect in the product function
• Perspective -> Functionality and Severity status based on technical aspects of the product

Example Bug Priority and Bug Severity in Facebook

Mini Study Case

1. Force close happens between versions of 6.0 and 4.4 inclusive range (assume that no Android is run below 4.4 while using the apps).
2. Environment: production.
3. Every android version has different users percentage

Step 1

• Reproduce the bug and save the evidence
• Set up the priority and severity (reasoning will explain at next slide)
• Create Bug Report

Step 2

1. Based on usage of Android version the priority that can be check from High to Low consist of Android version 6, 51.1 and 4.4
2. For severity because it is force closed the severity consist of Critical

Step 3

1. QA Team push the issue to QA Lead
2. While QA lead review the bug report QA Team will do test to another Android version the priority can be seen from table

Step 4

1. QA Team pass to Dev team and fix the problem directly based on the priority

Step 5

1. After Dev Team fix it and said the issue has been fixed
2. QA Team recheck again the problem and if the problem has been clear the status move to CLOSED

Notes

1. The re-test from another Android device will inform directly to Dev Team
2. QA Team propose the new SOP for mitigate the problem to PM

References

Defect/Bug Life Cycle in Software Testing

https://fadhilara.medium.com/bug-priority-bug-severity-3b2a94e3ab29

https://medium.com/@masginta/jenis-jenis-dan-tingkatan-bug-pada-software-bagaimana-cara-mengelompokkan-bug-sesuai-4785e5337ca7https://www.lambdatest.com/blog/bug-severity-vs-priority-in-testing-with-examples/

https://www.softwaretestinghelp.com/how-to-set-defect-priority-and-severity-with-defect-triage-process/

https://www.guru99.com/defect-severity-in-software-testing.html