What is Defect Life Cycle?
Defect life cycle is also known as Bug life cycle. It is the set of specific states that a bug goes through in its entire life.
The Purpose behind to follow defect life cycle is to coordinate and communicate the state of defect which is assigned to different assignees. i.e., Developers and QA.
This helps to make the defect fixing process systematic and efficient.
There are various tools available to track bugs and JIRA is one of the defect management tools to track all the defects with appropriate states. It is also called the JIRA bug life cycle.
Which are the different states of Defect Life Cycle?
New
When tester finds any bugs then it is reported with the current status “New”
Open
When the developer starts the analyzing the defect and working on it to fix the defect with the status “Open”
Fixed
When a developer makes the code changes and fixes the defect then marks the status as “Fixed” and assigns it back to the QA team for testing.
Retest
Testing Team starts verifying the fixed defect according to the changes done by the developer. Here, QA makes sure that changes done by developer are as per the requirement or not
Closed
If defect is working as per the requirement, then Tester marks it as a “Closed”. This is the final status of the defect that is closed by QA after Retesting or another reason to mark it as a closed is duplicate or considered as “Not a bug”.
Reopened
When the defect is rested and if it is NOT working as per the requirement then it is reopened by the QA team and assigned back to the developer for the accurate changes.
These are the basic state which is followed by most of the defect management tool like JIRA.
- QA Finds the defect and logged as Status “New”
- Defect is analyzed by the project manager.
- Project manager decides whether the defect is valid or not.
- If it is valid then need to check whether it is in scope or not.
- If the defect is not valid then defect is rejected and marked as “Rejected”
- If a defect is in scope, then need to check whether it is already raised or not.
- If defect is not in scope, then marked as “Deferred” or “Postponed”
- If Defect is already raised then marked as “Duplicate”
- If Defect is not raised then it is assigned to the respective developer to fix the defects.
- Developer starts fixing the defect and change the status to “In Progress”
- Once the defect is fixed, Developer marks the defect as “Fixed” and assign back to QA
- QA retest the defect. If Test is passed then defect is closed and QA marks it as a “Closed”
- If the test is not passed then the defect is Reopened and assigned back to the developer for fixing the defect again with status “Reopened”.
Conclusion
That’s all for the bug life cycle. It really helps to identify defect’s current status and tracks the defects in a systematic and efficient way.
She is Senior Quality Analyst at Elitech Systems. She has expertise in automated and manual Software testing, proficient in analysing a large scale project with useful insights for developers and project team.
Comments are closed.