Bug Life Cycle

[ test documentation ]

Bug Life Cycle describes the set of states a bug goes through, from creating a bug report to closing or rejecting it.

The bug is usually closed by a tester after the developer fixes the defect and the functionality successfully passes retesting.

The transition of a bug from one state to another is called the bug life cycle.

The current state of a bug is its status:

Created — the tester has logged the bug.
Assigned — the bug has been assigned to an assignee.
Analysis — the bug is being analysed.
Rejected — the bug was rejected and does not require a fix or is not considered a bug.
In Progress — the bug is currently being fixed.
Fixed — the bug has been fixed and is awaiting verification.
Testing — the tester is performing retesting.
Returned for Fix — the bug reappeared during retesting.
Closed — the fix has been confirmed by the tester, and the bug is closed.

The assignee changes between developer and tester depending on the bug’s status.

Task