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

List 5 major test cases for Lift

4 Answers   Yahoo,


What is black box testing, and what are the various techniques?

0 Answers  


How we map test cases with the requirement in Quality Center plzzz give the procedure step by step

2 Answers  


Explain crud testing.

0 Answers  


Write test cases for yahoo sign up page.

2 Answers   NIIT,


There are 20 resources out of which 12 are manual testers, 5 automation testers and 3 performance testers. There are a bunch of projects to be tested in the organisation, the projects belong to various technologies, say 20% of projects in Java, 20% of projects in SAP, 30% of projects in .NET, 30% of projects in C# What is your approach as Test Manager in testing.

0 Answers  


how will you clarify the requirements

8 Answers   eMids, HCL, iGate, JPMorgan Chase,


what are the main challenges faced in ur project?

5 Answers  


What is a test scenario?

0 Answers  


Difference between postponed and deferred bug

1 Answers  


Hi, Please tell how to write system test cases for between two modules. please ans real time expirience people... thanks in advance..

0 Answers  


What sre the documents used in SDLC, and STLC?

2 Answers  


Categories