Bug Life Cycle

ref :BrowserStack

1. New

The tester finds the problem and creates a bug report.

Example:

"Login button is not working after entering valid username and password."

At this stage the bug status is New.

2. Assigned

The testing lead or QA manager assigns the bug to a developer.

Now the developer is responsible for checking and fixing the problem.

3. Open / Active

The developer starts investigating the bug.

The developer checks:

What is causing the problem?
Can the problem be reproduced?
Which code is causing it?
How can it be fixed?

If the developer believes it is not actually a bug it can instead be marked Rejected Duplicate Deferred or Not a Bug.

4. Fixed

The developer finds the problem and changes the code to fix it.

After fixing it the developer sends the updated application back to the tester.

5. Retest

Now the tester tests the same login problem again.

For example:

Enter username → Enter password → Click Login.

If Login works correctly the tester considers the fix successful.

If Login still doesn't work the bug can be reopened and sent back to the developer.

6. Verified

When the tester confirms that the bug has been successfully fixed the fix is verified.

7. Closed

Finally the tester closes the bug when no further work is required and the problem has been successfully resolved.

Other Bug Statuses

There are also some additional statuses that can happen during the process:

Rejected:
The developer believes the reported issue is not a valid bug.

Duplicate:
The same problem has already been reported in another bug.

Deferred:
The bug is valid but it is low priority so the team decides to fix it in a future release.

Not a Bug:
The reported behavior is actually expected behavior or does not affect the application's functionality.

Easy Flow to Remember

simple example

Bug Life Cycle is the journey of a bug from the time the tester finds it until it is fixed and closed. First the tester reports the bug as New. Then it is Assigned to a developer. The developer investigates it and changes the status to Open. After fixing the problem, it becomes Fixed. The tester then Retests the bug. If the fix works the bug is Verified and Closed. If the problem still exists the bug is Reopened and sent back to the developer.