Topic: Retesting vs Regression Testing

Hi,

1. Retesting involves the check for the functionality of the previous and the present
 build is stable or not,
incase of Regression testing is checking for  the newly added functionality causing any errors in terms of functionality and the
common functionality should be stable in the latest and the previous versions

2. Regression testing is done to verify wheather the bugs has been fixed after review of not,

Retesting is done to check the functionality of the application with newer version or release no. .,

3. Retesting and Regression Testing are slightly different in the sense....they are to be executed on different test cases...
E.g. If there are 1000 test cases to be executed in the first build....And of the 1000 test cases, 100 fail and 900 pass....
Then after bug fixes and when the 2nd build is received, REGRESSION Testing has to be done on the 900 test cases and the remaining 100 test cases are to be RETESTED.

4. When a bug is found, it needs to be communicated and assigned to developers that
can fix it. After the problem is resolved, fixes should be re-tested with the same test data.

Additionally,determinations should be made regarding requirements, software, hardware, safety
impact, etc. to make sure the application works as expected.

Testing the application once the bug is fixed with new test data to check the fixes didn't create other problems
elsewhere.

Rgds,
Varun

RETESTING: Testing the application with multiple sets of 
test data is Retesting.

REGRESSION TESTING: Test the bug fixes r working properly 
as the specification and test, by fixing these bug any 
other feature may get impacted (conduct impact analysis) is 
regression testing.