Defect/Bug life cycle

New:

When a tester finds a new defect. He should provide proper Defect reproduction steps to the development team to reproduce and fix the defect. In this state, the status of the defect posted by the tester is “New”.

Assigned:

Defects that are in the status of New will be approved (if valid) and assigned to the development team or to the developer by Test Lead/Project Lead/Project Manager. Once the defect is assigned then the status of the bug changes to “Assigned”.

Open:

The development team starts analyzing and works on the defect fix.

Fixed:

When a developer makes the necessary code change and verifies the change, then the status of the bug will be changed to “Fixed” and the bug is passed to the testing team.

Test:

If the status is “Test”, it means the defect is fixed and ready to do a test whether it is fixed or not.

Verified:

The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is “verified.”

Closed:

After verifying the fix, if the bug no longer exits then the status of the bug will be assigned as “Closed.”