Retesting slightly reminds regression testing but still there is a set of differences between these types of software quality checking. Retesting is more like rechecking of the earlier reproducing error. Hence its name.
What are the goals of retesting?
- Verification of specific bugs and mistakes.
- Confirmation for developers that the problem is really valid and reproducible.
- The whole module is checked in order to make sure in its correct operation.
- To assure of correct operation of a certain feature, system component or module or application.
Like any other type of software testing, retesting possesses a range of advantages among which there are:
- confirming the error removal;
- improving the whole product quality;
- quick verification - it is necessary to recheck a certain error;
- installing the new environment is not required - the same data and conditions are used.
But it is not so simple, one should not also forget about minuses of retesting.
What are the disadvantages of retesting?
- A new build is required for the fixed error verification.
- The test cases cannot be automated.
- Additional time is required for the failed test cases rechecking.
The retesting test cases can be used only after the primary testing process was completed.
Retesting may be connected with any other type of checking. Executing security testing, usability control, performance testing, load checking or compatibility testing, the specialist has detected the bug. The developer has fixed this bug. Thereafter, one should recheck whether everything operates correctly and the error was really removed.