Retesting

Retesting:

Confirmation testing is also known as re-testing.

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

                                                                            (or)

Re-testing is done by the tester after a bug/issue is fixed or resolved for checking that application works properly or not as per requirement specification or not.

If Tester found that bugs/issues are not resolved or fixed, He/She updates the status of bugs as “RETEST FAILED” and assigns the bug to developer again.

For Example:

Suppose you were testing some software application and you found defects in some component.

1. You log a defect in bug tracking tool.
2. Developer will fix that defect and provide you with the official testable build.
3. You need to re-run the failed test cases to make sure that the previous failures are gone.

This is known as confirmation Testing or Re-testing