Answer / aa

From Requirement Traceability Matrix , are able to link the
Defect to Test Case.

If we are using QC , directly able to link the defect to
test case and requirement through defect module, test lab
and test plan modules.

While logging defects any tracker or any tool, we will be
having option to enter Test case id , if bug is produced due
to test case fail.

Bug Life Cycle;
New -- When Tester log the defect
Open/Inprogress --When developer accept the bug
Rejected -- If developer not accept the bug.
Fixed -- When developer fix the bug
Closed --- when tester verifies the bug and its working.
Reopen-- When tester verifies the bug and its still not working.

Answer / ramyasri

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.

how we receive the build ? will there be change in version for every single bug the developer fixes ?

2 Answers  

---

what is RCA and how to do root cause analysis

1 Answers   Infosys,

---

what is v-model.why you are using v-model?& v-model follow parallelly approach is it correct?

2 Answers   Accenture,

---

How to do integration testing on duster......

0 Answers  

---

explain the Compatibility testing

5 Answers   EDS,

---

---

Hi, can any tell how a tester can be judged? i have to interview a tester, how should i judge whether he has a justified experience or not? how a person with 3 years of experience in manual testing can be judge?

0 Answers  

---

hi frinds ,,what is the difference between QA & QC , i need only real time definations ,pls pls

7 Answers   Synergy,

---

what is the format of test case document? any one can send test case excel sheet format? my id :chinna.4494@yahoo.com

2 Answers  

---

How to do test if we have minimal or no documentation about the product?

5 Answers  

---

If I want to check compability of software in a MAC OS then which steps shold I follow?

0 Answers  

---

How do we do "cookie Testing" in web based testing. what we check in that testing,anybody can explain in detail. Thanks in advance.

2 Answers   IBS,

---

what is agile testing

2 Answers  

---