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.

Did you ever worked with BA's?

1 Answers   Standard Bank, Wells Fargo,

---

when we will give testdata while writing testcases r during executing testcases for both positive and negative cases we give testdata

3 Answers   PSI Data Systems,

---

Is Validation Test & Negative Tests have same meaning???Are both same???

4 Answers  

---

What is Test Coverage?

3 Answers   iNautix,

---

Hi,please help me out with my ques:as soon as the build we get from developer,how will we start testing?first all how the build we get (means which form)?who will install it in the system and how tl will assign us the work?

1 Answers  

---

wt is the diff. bet. verification and validation If possible explain with one example.

15 Answers   Syntel,

---

by testcase how to achieve 100% branch coverage for the following code. Read P Read Q Print "P" Print "Q"

2 Answers   IBM, ISTQB,

---

How performance testing can be done manually? can anyone answer this question plz?

4 Answers   Infosys,

---

Which design document supports to choose test data and how to select test data ranges ?

1 Answers  

---

What is mean by Open Source tools?

1 Answers  

---

In first version of the build i found a bug . I report it to my developers with all the procedures and that was accepted by the developers and the bug was in open state. In the next version of the build the bug was not able to reporduce it .Then wat will be the status of that bug

9 Answers   Siemens,

---

Hi all, i am planning to take ISTQB CERTIFICATION, can any one guide me by giving the links for preparing for the exams. If anyone have some materials can u send me to my mail id vpbharathi@gmail.com. Thanks in advance, Bharathi.P

0 Answers  

---