DEV Community

Cover image for Bug life cycle in software testing
Alex K. for HireTester

Posted on

Bug life cycle in software testing

A bug or defect detected in software goes on a fascinating journey through various stages, corresponding certain bug statuses right until being resolved or closed. What are these stages? Let’s track the route.

New
This status is applied to new, lately discovered, and added to a tracking system bugs.

Assigned
These are the bugs that have been already assigned to a certain specialist for checking, fixing, or verification.

Open
This status shows that the specialists entrusted with the bug are actively inspecting it. They can also assign another status to the bug: Duplicate, Rejected, Deferred, or Not a Bug.

Fixed
As its name implies, the bug gets this status after the fixing is completed and when a QA engineer can continue the verification process.

Retest
This status is a signal for a QA engineer to retest the bug, confirm if it has been indeed fixed with no impact on corresponding functionality.

Reopen
If the bug has been reproduced during retesting, it gets the Reopen status and goes to the developer for re-investigation.

Verified
The status used for bugs the QA engineer could not reproduce during testing.

Closed
This status shows that all verification procedures are completed, and the bug does not exist anymore.

https://hire-tester.com/

HireTester #qa #softwaretesting

Top comments (0)