Answer / lakshmanaraj bg

Confirmation testing is also known as re-testing.

Retesting is planned based for the defect fixes listed in Build Notes.

Retesting is carried out to verify defect fix / fixes.

Retesting is done to make sure that the tests cases which failed in last execution are passing after the defects against those failures are fixed.

Retesting involves executing test cases that were failed earlier.

Retesting always takes higher priority over Regression testing i.e., Regression testing is done after completing Retesting.

This is known as confirmation Testing or Re-testing.

Answer / rabi

confirmation testing refers 2 acceptance testing that is performed on the system prior to its delivery

What is the diffrenece b/t regression and integration testing????

7 Answers  

---

Explain paradigms for interfacing module?

0 Answers  

---

what is the diff between smoke testing & monkey testing?

9 Answers   Logica CMG,

---

What does the test strategy include?

1 Answers  

---

What is IEEE 829? (This standard is important for Software Test Documentation-Why?)

2 Answers   Ordain Solutions,

---

What the purpose of testing?

0 Answers  

---

In one project, How much “%” effort made by SQA Tester? e.g. : developer = 35%, manager = 10%, etc.

0 Answers  

---

if i am giving you a module to test but no specification is provided to you then on what basis you will write test cases?

2 Answers   TCS,

---

What is the involvement of tester in SDLC?Explain.

3 Answers   AZTEC, TCS,

---

What is the difference between Outsourced Testing and Crowdsourced Testing

0 Answers  

---

what is build acceptance test?

7 Answers  

---

What is test idea? What is tets plan?

3 Answers  

---