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.

what is RFT?

5 Answers  

---

why do you go for white box testing when black box testing is available?

6 Answers  

---

Acceptance testing is designed whether or not the software is FIT for the user to use. The concept of FIT is important in both design and testing. There are four components of FIT .what r they

1 Answers   Infosys,

---

What is the significance of version control in software testing

1 Answers   IBM,

---

please explain me with example of this question. diff between bug and diffect. don't give def please give answer with example.

14 Answers   TCS,

---

---

can u pls explain me what is boundary value analasys and equivalent partitioning

4 Answers  

---

What is Application Performance testing and Operational performance testing

0 Answers  

---

what is the difference between bug and defect? what is the definition of bug? what is the definition of defect?

3 Answers   Core Solutions,

---

What is JAVA Testing, what we do in That ?

2 Answers  

---

What are the four steps to record a test script?

3 Answers  

---

Relative to other technical groups in the company? Relative to your staff?

0 Answers  

---

How will u classify the test cases ?

5 Answers  

---