Defect/Bug life cycle is a cycle which a defect/bug goes through during its lifetime. It starts when defect/bug is found and ends when a defect/bug is closed, after ensuring it’s not reproduced. The Life cycle of the bug can be shown diagrammatically as follows. Defect/Bug life cycle includes following steps or status:
New: Defect/bug found for the first time and its state is new.
Assigned: After the tester has posted the bug it will assign the bug to corresponding developer and the developer team. Its state is assigned.
Open: At this state the developer has started analyzing and working on the defect/Bug fix.
Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing team.
Verified: The tester tests the bug again after it got fixed by the developer. If the bug is not present in the software.
Reopen: If the bug still exists even after the bug is fixed by the developer, and bug goes through the life cycle once again.
Closed: If the tester feels that the bug no longer exists in the software after testing, he changes the status of the bug to “closed”.
Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the Defect/Bug.
Rejected: If the developer feels that the bug is not genuine, he rejects the bug.
Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases.
Not a bug: The state given as “Not a bug” if there is no change in the functionality of the application.