Regression Vs. Retesting
This is the most common question I have heard during the! And, most of the times I have seen candidates getting confused and confusing the questioner as well with their answers! Even though you are working in a real time environment, and deal with the and scenarios, it is very confusing to differentiate unless you know what exactly they mean, and if you do not know what it means, you are considered no good tester.
Phew! that was very confusing indeed Well, to cut it short, we should be knowing the difference between them as a tester! Infact, the difference between them is very simple, but still many of us seem to be not able to distinguish between them. So here, we would discuss some simple points about both of the types and give some real time examples:
Regression Testing: Whenever the changes are made to the existing code (while fixing defects) a set of cases is run every time to ensure that the changes in code have not introduced any new failures in existing code, is known as Regression Testing.
The bug which was recently fixed by developers (after making some code changes or whatever) may have caused new bugs in the functionality that had already been tested. In this case, you’ll identify all other functionality that that is linked with this bug (or functionality) and execute those scenarios (test cases). This is called Regression testing
Take a simple example: You have an Regression Testing.to test, you found a bug. The developers fixed it. Now, you need to test the entire application in order to see that there is no effect of the bug fix on the application in total. Or, lets say you have a bug in a feature which you found on Vista OS English. Now, you will test for the same bug in all the different languages which your application supports. This is
If you have bugs in your previous versions or builds, checking them on the latest builds and other versions can also be called as Regression Testing.
Re-testing: This is very simple. Whenever a defect is fixed by the developer, tester verifies that defect to make sure that the defect is actually fixed, this is known as Re-testing. The functionality is again tested for a fix here. This would not include checking the system in total. TEST ONLY THE FIX. Here, you are concerned with only the fix.
Example of this would be: You found a bug. The developer fixes it and send it to you to test. You retest it to make sure that it has been fixed. If it is still not fixed, you again send it back to developers and they in turn return back to you after fixing it again. This process of retesting goes on and on until bug is fixed. This is called RE-Testing
Re-Testing is also called as Confirmation Testing. Confirmation Testing is done to make sure that the tests cases whichin last execution are passing after the defects against those failures are fixed.
We would love to hear any other examples which you have encountered in real time which would help us more in understanding these two concepts…