when a bug is raised for the first time then the satus of
the bug is said to be New
when the bug is fixed by the developer then the developer
will  update the staus of the bug as fixed
when the tester observes the same bug on a modified
application then the status of the bug is said to be reopen
when the tester observes the bug is fixed then the tester
will update the status as close
when there is a Controversy over a raised bug than the bug
status is update to hold till the immediate supervisor or
the client clarifies

Bug life cycle has
New - when the bug is found.
Assign- Test lead assign the bug to developer to rectify.
Open- Once the developer starts working on it, then the 
state is open.
Fix- Once the bug is fixed
Reopen-If the fixed bug is erraneous, then it will go for 
retesting.
Close- Once all the bugs are fixed and completed.

Hi,

There is no new status for the bug in the real time.

Whenever a bug occurs tester will give open as status then 
sends it to the development team to resolve it. Then the 
status changes from open to fixed/resolved. After bug 
fixing developer sends that to testing team for 
verification, then its status is verified. If the bug is 
resolved completely tester will close the bug otherwise he 
wil reopens the bug and sends it to development team for 
resolution.
open-tester
fixed/resolved-developer,rejected due to duplicate, deffered
verified-Tester           Not a bug   
close-Tester
Re-open- tester

basically there r 5 steps of bug life cycle
1.creation:
   in this step identification of bug can be done by tester
2.Assinged:
   in this step the bug assinged to a developement team.
3.Evaluation:
   in this step bug is evaluated which is done by developer.
it means which module or what line of codes are creating 
the problem which is identified by developer.
4.Fixing:
   in this step bugs r fixed and its makes change in source 
repository.
5.verify:
  in this step bugs r verified that bugs r fixed or not 
which is conducted by testing.

Hi,

There are seven different life cycles that a bug can passes
through: 

< I > Cycle I: 
1) A tester finds a bug and reports it to Test Lead. 
2) The Test lead verifies if the bug is valid or not. 
3) Test lead finds that the bug is not valid and the bug is
‘Rejected’. 

< II > Cycle II: 
1) A tester finds a bug and reports it to Test Lead. 
2) The Test lead verifies if the bug is valid or not. 
3) The bug is verified and reported to development team with
status as ‘New’. 
4) The development leader and team verify if it is a valid
bug. The bug is invalid and is marked with a status of
‘Pending Reject’ before passing it back to the testing team. 
5) After getting a satisfactory reply from the development
side, the test leader marks the bug as ‘Rejected’. 

< III > Cycle III: 
1) A tester finds a bug and reports it to Test Lead. 
2) The Test lead verifies if the bug is valid or not. 
3) The bug is verified and reported to development team with
status as ‘New’. 
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’. 
5) The developer solves the problem and marks the bug as
‘Fixed’ and passes it back to the Development leader. 
6) The development leader changes the status of the bug to
‘Pending Retest’ and passes on to the testing team for retest. 
7) The test leader changes the status of the bug to ‘Retest’
and passes it to a tester for retest. 
8) The tester retests the bug and it is working fine, so the
tester closes the bug and marks it as ‘Closed’. 

< IV > Cycle IV: 
1) A tester finds a bug and reports it to Test Lead. 
2) The Test lead verifies if the bug is valid or not. 
3) The bug is verified and reported to development team with
status as ‘New’. 
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’. 
5) The developer solves the problem and marks the bug as
‘Fixed’ and passes it back to the Development leader. 
6) The development leader changes the status of the bug to
‘Pending Retest’ and passes on to the testing team for retest. 
7) The test leader changes the status of the bug to ‘Retest’
and passes it to a tester for retest. 
8) The tester retests the bug and the same problem persists,
so the tester after confirmation from test leader reopens
the bug and marks it with ‘Reopen’ status. And the bug is
passed back to the development team for fixing. 

< V > Cycle V: 
1) A tester finds a bug and reports it to Test Lead. 
2) The Test lead verifies if the bug is valid or not. 
3) The bug is verified and reported to development team with
status as ‘New’. 
4) The developer tries to verify if the bug is valid but
fails in replicate the same scenario as was at the time of
testing, but fails in that and asks for help from testing team. 
5) The tester also fails to re-generate the scenario in
which the bug was found. And developer rejects the bug
marking it ‘Rejected’. 

< VI > Cycle VI: 
1) After confirmation that the data is unavailable or
certain functionality is unavailable, the solution and
retest of the bug is postponed for indefinite time and it is
marked as ‘Postponed’. 

< VII > Cycle VII: 
1) If the bug does not stand importance and can be/needed to
be postponed, then it is given a status as ‘Deferred’.

Plz correct me if i m wrong...
Regards..
nitin9360@gmail.com

Bug life cycle starts with the identification of defect in 
the application. Bug is reported to the developer n 
developer fix the bug (tester never fix any bug )


Plz correct me if i m wrong...
Regards..
Lokesh Kumar Chauhan 
lokesh_kumar_chauhan@yahoo.com
Mobile - 09350229669
Noida

The Bug Life Cycle,

New(Tester) - 
Assigned(To Developers)
Open(Developers)
Fixed (Developers)
Reopen(After Fix the Defect Executed by the Testers again 
the defect is not fixed change the Status as Reopen and 
Send to Developers)
Closed(Review By TL or Testers)

SR.Ashok - Perot Systems.