Bug Life Cycle or Defect Life Cycle:
Following is
a Diagrammatic Representation of Different phases of Bug Life Cycle
Today I am going to
be share what is Bug Life Cycle or what is Defect Life Cycle and what are types
of status are there. Defect Life Cycle is explain entire history of the defect.
When it was found, who was founded and now it is which status like these
details we will get.
In Bug
Life Cycle or Defect Life Cycle we have different types of Status.
·
New
·
Assigned
·
Open
·
Duplicate
·
Fixed
·
Verified
·
Re-Open
·
Closed
·
Deferred
New: When
testing team doing testing, testing team will find some Bugs. Whenever testing
team will find the Bug they wants to raise the Bug, then only Development team
will know what the issue. For that some Organization’s using some tools (Bug
zilla, QC). Some Organization’s using
Excel Sheets.
Whenever testing team will find
the Bug they want to raise the Bug, when a defect is logged and posted for the
first time then we can, Status is NEW.
Assigned:
Once the testing team posted a BUG, and then development team lead will check
and assign that bug to his team. At they set status Assigned.
OPEN: Once
the defect is raised, automatically mail will generate to the Assigned Person.
While raise the Bug at the time only testing team to will assign whom we are
going to be Assign the Bug. For that we have one option “Assigned to”. Then The
Assigned Person will open the Bug and try to fix the Bug. At the they will
change the status “OPEN”. By using theses Status we can track the Bug is in
which Status.
Duplicate:
Sometimes testing team will open same bug more than one time. When development
team open the bug to fix, if they identified the raised bug is already logged
then they will set the status as Duplicate.
Fixed: Once
the Development team is fixed the Bug, they will change the status as “Fixed”.
Then testing team will do Re-testing based on the output testing team will
“Re-open or Close” the defect.
Verified:
Once the defect is fixed by the Development team then testing will verify the
modified code. May be it will take some time to verify that code at the Testing
team will set the Status as Verifying.
If the modified code is working
is working based on the Requirement Testing team will set the status “Closed”, Otherwise testing team will Re- Open the Defect.
Re-Open:
After fixing the Bug, testing team will do Re- testing the Application based on
the Output testing team will Re-Open or Close the defect. If the application is
not working based on the Requirement then testing team will Re- Open the
Defect.
Close: If the application is working based on the
Requirement then testing team will close the Defect.
Deferred: If
the bug is changed to deferred state means the bug is expected to be fixed in
next releases.