Re Testing

RE-TESTING:-

Re testing means repeat the test on same functionality.
It will happend in the following cases …...

• Testing already tested functionality again and again by using multiple sets of data to check whether the functionality works for different inputs or not 
• Once the bug is fixed , the functionality needs to be tested to confirm that it is really fixed or not 
• Testing the functionality of the application frequently to ensure that the changes made in particular module is working properly/not. 
• Re-testing is when you test the functionalities repeatedly for the issues you have raised. 

Re testing also known as Confirmation Testing.
When to Execute the test cases:-
What type of test cases has to be testing in this re-testing mentioned below

• Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions. 
• If any change is made into the application, testing only those changed test cases and not the entire test cases. 
• Executing the test cases again on the same build with multiple set of Test Data. 
• Execute the same test case repeatedly for the issues you have raised to know how it occur. 

How to do the Re-Testing as a Test Engineer:-

• Lock the Bug in the Defect Tracking tool 
• Developer will fix that defect and provide you with the official testable build. 
• Need to re-run the failed test cases to make sure that the previous failures are gone. 

Example for Re-Testing:-

There is a Project which we called as “P”

It has some modules which we called as “M1,M2,M3....”
Testing the module “M2” with the different sets of test data by repeat the same test case.
Now you found some bug in M2. after bug fixing when you test M2 to verify that bug fixed or not but you won't test M1 and M3 modules
There are some changes done in M2 module then you need to execute the test case which you already executed before to confirm the functionality working fine or not