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 / santhosh k

Bug status description:
These are various stages of bug life cycle. The status
caption may vary depending on the bug tracking system you
are using.

1) New: When QA files new bug.

2) Deferred: If the bug is not related to current build or
can not be fixed in this release or bug is not important to
fix immediately then the project manager can set the bug
status as deferred.

3) Assigned: ‘Assigned to’ field is set by project lead or
manager and assigns bug to developer.

4) Resolved/Fixed: When developer makes necessary code
changes and verifies the changes then he/she can make bug
status as ‘Fixed’ and the bug is passed to testing team.

5) Could not reproduce: If developer is not able to
reproduce the bug by the steps given in bug report by QA
then developer can mark the bug as ‘CNR’. QA needs action to
check if bug is reproduced and can assign to developer with
detailed reproducing steps.

6) Need more information: If developer is not clear about
the bug reproduce steps provided by QA to reproduce the bug,
then he/she can mark it as “Need more information’. In this
case QA needs to add detailed reproducing steps and assign
bug back to dev for fix.

7) Reopen: If QA is not satisfy with the fix and if bug is
still reproducible even after fix then QA can mark it as
‘Reopen’ so that developer can take appropriate action.

8 ) Closed: If bug is verified by the QA team and if the fix
is ok and problem is solved then QA can mark bug as ‘Closed’.

9) Rejected/Invalid: Some times developer or team lead can
mark the bug as Rejected or invalid if the system is working
according to specifications and bug is just due to some
misinterpretation.



Is This Answer Correct ?    13 Yes 4 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Explain walk-through?

984


i am a PG science(chemistry),now am working test engineer in small organization,now i will decide to move better organization please send model cv and advises

2233


how to download fullversion of JIRA(defect reporting s/w) s/w for free.can any provide web site for full version free download.

2494


What is path coverage testing?

1064


Hi, I am writing ISTQB foudation exam on 9 June 2010. Anyone please send me pdf of the book "Sample Exam Questions: ISTQB Certified Tester Foundation Level (Paperback)by John A. Estrella " to hsdantot@yahoo.com Thanks Sree

1899


Explain cause effect graph?

1012


What is random/monkey testing?

1032


What is difference between SAN and NAS? How SAN is better than NAS?

2458


Explain beta testing?

1057


What is checksheet?

1024


What is emulator?

1131


Every One is saying that Documentation is very very importent in Tester's Life.Could any one explain with proper examples..?

2184


How u r managing the staff unavailability?

2264


Mention what the purpose behind doing end-to-end testing is?

1120


What is ieee - institute of electrical and electronics engineers?

962