Quality is delighting customers
Regression Testing: After completion of (completion of testing)one feature/functionality and then one change request/modification made to this feature/functionality and then testing of this feature/functionality AGAIN, this type of testing called Regression Testing.
Example: One Application form has developed and completed and then one CR is came as to add one field called E-MAIL to this application form, then tester has to test this application form again that due to this CR made, whether application form's functionality is effected or not ?
Re Testing: If tester has posted one issue which has 4 steps and after solving from developer, tester has to test this issue in those 4 steps AGAIN EXACTLY AS IT WAS, this testing called Re Testing.
Retesting: Executing again failed test cases after fix.
Regression: Execution of impacted module test cases.
when any new cr comes we will write testcases for it and execute that testcases and also excute any dependent r impacted testcases we will excute
if any one ask what is regression testing i have to tell execution of impacted module testcases r which i have written above pls correct me
Thanks in advance
Regression Testing:Tested in New Version.
Retesting: Tested in Same Version
Regression testing : Testing entire regression suit on new build to assert new changes or defect fixes or enhancements not affected the working features.
i.e it is to confirm that no impact or side effects on working application with new changes/fixes.
Retesting : Verifying defect fixes.
Well lot of confusions...Try to see how it means literally..
it will make life simpler.
Retesting: What happens in case of rematch?..You dont modify the players rt?
same way, Retesting is testing what u have tested earlier. In testing term say, there are 10 Tesst cases. Now u executed them with build 1. It will be called Retesting if u r going to execute the same set of 10 test cases either in build 1 or build 2, build 3.....
Regression: It always involves an impact analysis. U do a regression after studying the changes and then do. Which means it will always occur if there is any change..
For clarity lets take a practical example:
1. U have received the very first build from Dev team and want to test it
U went ahead and tested it
again uor lead asks to do testing on the same build. Which means there is no change.
So u can do a Retest not Regression. Regression can start from build 2 only.
This is highly misunderstood in the Testing industry. When people recieve new build from dev they again go and run the same set of test cases without any impact analysis and call it self Regression. Its actually a Retesting u r doing on the new build. If u have not studied the changes,impact analysis and simply executing the same set of test cases in same environment and same condition, then It is a Retesting.
Hope it is clear now.
Regression testing means that no error/bug should be introduced in your software because of the newly added feature/modules. It is done for the entire software/product.
Retesting means testing the same area once again on which the code change is done.
Now, let me explain the scenario with the help of an example. The example described is only for the learning perspective.
Suppossing you are testing a calculator software which has only Addition facility and the user input can be only numbers. While providing the input as 10.6 & 10, it is giving a result as 21 instead of 20.6.
If the developer fixes this issue, then you will test this part again which is called as retesting.
Now, if a new module/feature is introduced in the same calculator s/w i.e. of Subtraction. Then we will run all the use cases once again which we have executed for addition. This is done to make sure that no errors/bugs are introduced because of the new feature.
In this case, if some errors comes/occurs in addition module, which was working fine when only addition was there, then we mark the corresponding bugs as regression bugs.
Hope this will help you understand between these two types of testing