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

What is quality circle?

1154


The later in the development life cycle a fault is discovered, the more expensive it is to fix. Why?

1676


Explain error?

1147


Explain inputs?

1054


What is quality management?

1213


What is v&v?

1136


What do enterprises do for QC 11 to prevent minimum data loss ?

2321


Can anyone provide the definitions for the following abbreviations? Thanx to anyone who could CIT CAP

2138


What are validation and verification?

1161


Hi..I want testing in worker compensation claims.. if anyone have real exp..can you explain it for me.. thanks

1969


If anyone is having ISTQB certification study materials,please send to gul.e.raina@gmail.com

2160


When you will deploy Fibre Channel SAN instead of iSCSI SAN?

2409


what is the difference between software testing and quality testing? how do they vary,waht is the process of testing in both software and quality?

2352


What is impact analysis? As a tester how will you do impact analysis in your project?

1040


What is closed box testing?

1212