Bug Life Cycle

Bug Life cycle: Stages of a Bug that goes through its entire life cycle from New to Close.

? New: When a bug is logged and posted for the first time. Its state is given as new.

? Assigned: After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to the corresponding developer and the developer team. It’s state given as assigned.

? Open: At this stage, the developer has started analyzing and working on the defect fix.

? Fixed: When the developer makes necessary code changes and verifies the changes then he/she can make the bug status as ‘Fixed’ and the bug is passed to the testing team.

? Pending retest: After fixing the defect the developer has given that particular code for retesting to the tester. Here the testing is pending on the tester's end. Hence its status is pending retest.

? Retest: At this stage, the tester does the retesting of the changed code which the developer has given to him to check whether the defect got fixed or not.

? Verified: The tester tests the bug again after it got fixed by the developer. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “verified”.

? Re-open: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “reopened”. The bug goes through the life cycle once again.

? Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the bug status to “closed”. This state means that the bug is fixed, tested, and approved.

? Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “duplicate“.

? Rejected: If the developer feels the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “rejected”.

? Deferred: The bug, changed to deferred state means the bug is expected to be fixed in the next releases. The reasons for changing the bug to this state have many factors. Some of them are the priority of the bug may be low, lack of time for the release, or the bug may not have a significant effect on the software.

? Not a bug: The state is given as “Not a bug” if there is no change in the functionality of the application. For example: If a customer asks for some change in the look and feel of the application like a change of color of some text then it is not a bug but just some change in the look of the application.

#testing ?#software ?#team ?#stage ?#defect ?#defectlifecycle ?#buglifecycle ?#bug ?#errors ?#qualitycontrol ?#qualityassurance ?#manualtesting ?#softwaretesting