Any software product or application goes through a life cycle called Software Development Life Cycle (SDLC). Similarly testing of the software product or application goes through the Software Testing Life Cycle (STLC).
Just like the above any Defect or Bug in the software product/ application goes through a Defect Life Cycle or Bug Life Cycle. Before going into it let’s understand what a bug or defect is.
Bug or Defect is the error that happens in the software program or application. The developer may have made some mistakes that caused the software to not function properly. These flaws in the software program or application are called the bug or defect.
It is the responsibility of the tester to find as many defects as he can in the software program or application, so that when the software reaches the customer it is of highest quality.
Defect life cycle is the various stages a defect will go through in its lifetime. A defect life cycle can change from organisation to organisation or even project to project, but the basic workflow remains the same.
The reason behind having the Defect life cycle is to track its status and also to ensure the proper handling of the defect.
Some of the common stages in defect life cycle are as follows.
Defect tracking is one of the main steps in any defect life cycle. There are two main parameters which help in effective resolution of the defects are
As the name suggests, defect priority emphasizes how soon the defect needs to be resolved based on the business requirements.
The different priority levels are P1- Critical, P2 – High, P3 – Medium, P4 – Low.
Depending on the priority of the defect, developers fix them immediately or in future.
Defect severity implies the extent of the impact that is caused by the particular defect.
The defect severity can be in the following levels. S1 – Critical, S2 – Major, S3 – Minor, S4 – Low.
A high severity and high priority bug is worked on first, while a low priority and low severity bug is fixed later.
Advantages of a Defect Life Cycle :
Difficulties in Defect Life Cycle :
The method of deriving test cases from the defects is called defects based testing technique.
In the defect based testing technique
One of the critical parameters in the defect life cycle is the bug report. The developer actually works on the fix based on the defect document or the bug report.
A good bug report has the following details:
Bug id: The unique id given to the bug.
Title: The title of the bug should be descriptive enough that it is self explanatory.
Description: Description should be short and good enough for the person reading it to understand the scenario without any assumptions.
Date: Date which the bug is reported
Priority: How urgent the bug is need to be fixed
Severity: Impact level of the bug or defect
Status: Status of the bug in its defect life cycle
Test case: The test case on which the bug is identified or reported
Build/Release version: Environment details in which the tester worked on and identified the bug
Reporter: The details of tested who reported the bug in order to contact in case of any issues
Attachments: Visual attachment, screenshots to help the developer recreate the bug.
Defect handling is just one of the tasks that a tester has. To know more in depth about testing & gain testing skills, contact us. We have various courses that will help you hone your skills in both manual testing and automation testing.