5 most important stages in Defect Life Cycle.

Bug Life Cycle/Defect Life Cycle.

Before moving on to Bug life cycle. Let learn little about Bugs ....

What is Bug/Defect ?

To simplify the term we can say a defect is an error or a bug, in the application which is created

Bug/error/defects can be result of mistakes/fault/misjudgement etc. while designing or developing the application.

What is Bug Life Cycle ?

As the name suggest it is the journey of a bug covering the different states in its entire life.

There are 5 most important stages in the life cycle of a defect, you can see below.

➤When a tester executes the test cases, he might come across the test result which mismatches the expected result. This difference in the test result is referred as a Software Defect.

➤These defects or differences are referred by different names in a different organization like issues, problem, bug or incidents.

New Bug:

When a defect/bug is discovered and reported for the first time. This is beginning stage of Bug.

Assigned:

Once the Bug is reported, then it goes to the authorized person who assigns the bug to developer and is also responsible to cross the priority/severity of Bug.
This is the place where bug is analyzed and send to the next steps.

Fixed : 

This is the stage where developer find the root cause of the bug and then the bug is fixed.

 Retest:

Once Bug is fixed, Tester need to test the Fix and check if the bug  still exist or change in code might have given rise to new bug in application. Regression test is always recommended here.

If the retest is successful bug will get closed, But if the test fails then bug will be reopen.

Reopen: 

This stage will only appear in bug journey if developer failed to fix the problem completely or the root cause analysis of the issue was improper.

When Retesting of bug fails the bug is reopened and treated as a new bug and thus it will go through al the remaining stages again until its fixed completely and closed.

Deferred/Rejected/Duplicate:

Deferred - The open bug either doesn't have high impact on any functionality of application or due some time constrain it cannot be fixed in current versions, while it is moved to be fixed in latter versions. This decision is taken by assigner and authorized person like Test Lead.

Rejected - There can be many reason/scenario where bug will be rejected. For example, tester reports a bug which contradict the software requirement artifacts due to unclear or missing data.
  
Duplicate -  The reported bug is termed or made duplicate only in one case when there is similar bug already reported and it could be in open stage/getting fixed.