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

What about the test case if the field only takes a certain number of characters or a minimum number?

1122


Can you explain the pdca cycle and where testing fits in?

1194


what is entry and exit criteria and explain it?

1428


Unix question: 1)command to print a list of files containing a particular word. 2) what does a .profile mean. 3) what is a file server? 4) Command to move towards left in vi editor explain grep and find commands using example.

2435


How to overcome pesticide paradox?

1109


What is bug severity?

1110


How do you scope,organise and execute a test project.

2108


Can list out some disadvantages of manual testing?

1044


Which was the most interesting bug you found.

2964


Define brain stromming and cause effect graphing?

1117


how will you test a wine filled bottle along with 100 glasses

2279


What is a critical bug?

1032


hi can anyone tell me about vision plus testing? and what about its future

22468


For any web application, what are the possible login features that should be tested?

1292


Do you think tools are required for managing change. Explain and please list some tools/practices which can help you managing change.

2001