Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

explain bug life cycle

Answer Posted / vidya

The duration or time span between the first time bug is
found (‘New’) and closed successfully (status: ‘Closed’),
rejected, postponed or deferred is called as ‘Bug/Error
Life Cycle’.

(Right from the first time any bug is detected till the
point when the bug is fixed and closed, it is assigned to
various statuses which are New, Open, Postpone, Pending
Retest, Retest, Pending Reject, Reject, Deferred, and
Closed.

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’.

This way, any bug that is found ends up with a status of
Closed, Rejected, Deferred or Postponed.

Is This Answer Correct ?    3 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

tell me 3 defects in FRS document, while doing FRS review which u have found in the last 3 years ? could u plz answer brahma412@yahoo.co.in

2475


what are metrics and what are metrics did u collect in you are project

2356


Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing? plzzzzzzz i need ur help.

2268


Can test condition,testcase and testscript help u in performing the static testing

2070


i have done B.E. computer in 2009 i have done software testing course and also 6 months exp in testing on live project as trainee, now a days i am searching job in pune. can any one tell me any opening in pune?

2002


Can you explain usability testing?

1154


What is the difference between pilot and beta testing?

1200


Can anyone write test cases on google account creation page in the testing template format , urgent pls and explain if possible how to execute also

1995


What is localization testing (l10n testing)?

1274


Can anybody help i put the pharma and bank project in my resume, but i dont know what to tell about them, any body tell the where can i get the information about them,what i need to tell about these applications,please help me

2153


What is the difference between code walkthrough and code review? What is the difference between walkthrough and inspection?

2994


How the application is launched to the production environment?

1670


What are the roles of glass-box and black-box testing tools?

2134


can u write some high level scenarios on ms outlook express

2764


explain ur testing project? how can u nexplain . what should we explain ? i have not worked on any project?

2222