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

About Testing

0 Answers   Syntel,


What is the Technique followed to test Login Screen(Web) BVA or Equivalent Partition why?

10 Answers   IBM, RTG,


what is test bed?

10 Answers   HCL,


What is mean by Sanitation Testing?

17 Answers   Synergy,


What is Buddy testing?

14 Answers   Kanbay,


Consider if there is no Test lead, No Test Manager and QA Manager. If you are the senior test engineer, you are getting pressure from the client to give the build. But you see that, there r 5 high and 5 low sevierity bugs. So, what you will do and how you interact with the client.

14 Answers   Sonata, Xerago,


Can u specify one Deadlock or Processlock issue in a client server application?

1 Answers   Kanbay,


What parameters are you testing for as a Systems Tester ?

1 Answers  


what is the Exact difference between Sanity and Smoke testings

5 Answers  


Who prepared use case document? Tester or developer!

4 Answers   Mphasis,


Tell me the test cases for Notepad?

2 Answers   Patni,


How can I do a documentation of Test Cases? Which steps are in it?

4 Answers  


Categories