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


How will you link the Defect to the Test case? Explain Bug
life cycle ?



How will you link the Defect to the Test case? Explain Bug life cycle ?..

Answer / ramyab.mca@gmail.com

Hai...

Requirement Traceability Matrix is able to link the
Defect to Test Case.

Bug life cycle:
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.

K,Byeee...

Thanks & Regards:
B.Ramyasri.

Is This Answer Correct ?    2 Yes 1 No

Post New Answer

More Manual Testing Interview Questions

When we have to use Boundary value analysis and when to use equivalence partitioning. Please explain with an example. Urgently required.

2 Answers  


Hi friends, Im an MBA Finance, 2 yrs of exp workng in Investment com, + around 2 yrs of exp in Manual testing in Finane domain. Im looking for manual testing jobs but not getting any calls, Im worried is manual tesing in finance domain do have any good scopes in future or not. Plz provide me ur valuable suggestion,so tht I can best decision to retain in this platform(manual testing). or not

0 Answers  


why use caffine for HPLC calibration ?

0 Answers  


define STLC life cycle step by step

3 Answers   Cap Gemini,


can anybody tell me "what is ur testing process in ur company" pls explain what is the process when v get a build?

5 Answers   Verizon,


any one plz send me test cases on fan,pen,glass,cell phone,mouse and printingpage

1 Answers   SQS,


Who should test your code?

2 Answers  


What are drawbacks in system development life cycle

0 Answers  


how to write the test case for online (credit/debit) payment

2 Answers   Bank of the West, BirlaSoft,


write 5 critical test cases on product payment form on flipkart.com?

0 Answers  


How to test back up and storage products?

0 Answers  


What is incremental intergation testing?

2 Answers  


Categories