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

Tell me some of the test cases for Notepad Application?

2 Answers   Logica CMG,

---

What is a cookie testing?

0 Answers  

---

What is test stratergy?

6 Answers   Ordain Solutions,

---

Difference between ISO and CMM (No Abbrevations, Only concepts)

1 Answers  

---

who will give priority and severity for testcases?

5 Answers  

---

How to start testing after project kick off ???

2 Answers   CTS,

---

What is the role of Tester in BRS(Business Requirement Specification)phase in V-Model.

1 Answers  

---

What are SCORM Standards?

4 Answers  

---

We have a directory structure /usr/local/jboss/server/{$app_name}/log/*.log which contains 1000 log files. A web application has been logging to the cloud.log file, the attempts of a user called test. The code logs the following way: log.debug(username); where the username equals “test”. What command line application and or combinations of applications will you call in order to create a file named user_log.csv that contains the following lines, where the timestamp is sorted: timestamp,username

0 Answers  

---

Explain the difference between the verification and validation?

0 Answers  

---

can any one tell me about ieee standrad testcase formats plzzzz

1 Answers  

---

Explain Integration Testing?

2 Answers  

---