Bug Life Cycle

Error encounters during the any stage Software Development Life Cycle testing called bug or defects because fail to perform its intended addition.
Bug life cycle is related to the bug found during testing and it starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced
Bug life cycle is also called as defect life cycle which attains different states which can be termed as its life cycle

New
Open
Assign
Deferred
Reject
Fix
Test
Reopen
Verify
Close

New-:
When a bug or defect is detected for the first time, its state is given as new and yet to be approved.

Open-:
Tester analyzes and works on detected bug and approves that the bug is genuine to be fixed. If it is genuine then tester opens the bug, its state as open.

Assign-:
Approved genuine bug assigns to the corresponding developer and the developer team for fix and resolve. Its state given as assigned.

Deferred-:
Bug is expected to be fixed in before or next releases. Bug is not addressed to fix immediately then the project manager can set the bug status as deferred.

Reject-:
Bug or defect can be rejected for any of the reasons; viz – duplicate defect (repeated or two bugs mentioned in same concept), NOT a Defect (no change in the functionality), Non Reproducible and bug is not genuine.

Fix-:
Assigned developers or team fix the bug according to bug priority.

Test-:
Check whether the defect got fixed or not by developer and ready for testing.

Reopen-:
Bug still exists in source code of the software even after bug is fixed by the developer, then test changes it’s as reopen. The bug goes through the life cycle once again.

Verify-:
Bug is retested and the test has been verified by QA. Verify bug is no more present.

Close-:
In final state of the bug that can be closed after the QA retesting or tester feels that the bug no longer exists in the software, he changes the status of the bug to close. This state means that the bug is fixed, tested and approved

 

1 thought on “Bug Life Cycle”

Leave a Reply