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 ?

Answer Posted / 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       View All Answers


Please Help Members By Posting Answers For Below Questions

what is API 2.0?

2065


how can you test the web environment for security testing?

2040


What is test out put?

2144


what r u r responsibilities in current project

2555


Explain severity with example and expalin each example?

4420


what are the possible test cases for online jobs search portal..if its a job seeker module and any 1 if u had worked on this proj pls share the bugs with sev and priority pls frends i need replies for these queries ..thanks in advance

7620


Does anyone have any good examples of some acceptance criteria for non-functional requirements?

2112


Any one please can u tell me what is composer? An interviewer asked me do u have experience in Composer? its urgent.

2079


Hi,all i have a desktop App. which have a feature, It's a demo version if u want full version then u have to perches it. Pls give me some idea ASAP how can i break the App.

1962


How will you determine when to stop testing?

1106


write testcases for open dialogbox

2033


What is unit level testing?

1117


What is deferred status in defect life cycle?

1233


Do you use any automation tool for smoke testing?

1284


What is the difference between load testing and performace testing?

1209