To check for the bug fixes.
And this fix should not disturb other functionality.

To Ensure the newly added functionality or existing 
modified functionality or developer fixed bug arises 
any new bug or affecting any other side effect. this is 
called regression test and ensure already PASSED TEST CASES 
would not arise any new bug.

Please correct me .

Thanks & Best Regards.
Zahir hussain
CHENNAI.
Cell : 9382899885

To ensure that there is no bug & side effects due to 
changes,enhancments in the applicaiton

regression testing plays major role testing side because it 
not only tests whether bug closed or not but also checks 
the impact of that bug fixing.
More the regression testing buid is more stable

To Ensure the newly added functionality or existing 
modified functionality or developer fixed bug arises 
any new bug or affecting any other side effect. this is 
called regression test and ensure already PASSED TEST CASES 
would not arise any new bug.


There is a possibility of one error correction may introdue 
new errors..

HI

Regression Testing Performed

1. To Check whether the Fixed Bug is eliminated with the 
same Functionality as we tested earlier.
                   &
2. To check whether the corrected build should not cause 
any side effect over ther screen (or) In other Modules.

S.Ramprasad. sun_ramprasad.

To Check whether the Fixed Bug is eliminated with the 
same Functionality as we tested earlier and the corrected 
build should not effect to other functionalities.

The term "regression testing" can be applied two ways. 
First, when a code problem has been fixed, a regression 
test runs tests to verify that the defect is in fact 
fixed; "Imagine finding an error, fixing it, and repeating 
the test that exposed the problem in the first place. This 
is a regresson test" . Second, regression testing is the 
counterpart of integration testing: when new code is added 
to existing code, regression testing verifies that the 
existing code continues to work correctly, whereas 
integration testing verifies that the new code works as 
expected. regression testing can describes the process of 
testing new code to verify that this new code hasn't broken 
any old code.

Once the bug got fixed and we received the build we are
going to carry the test to check weather that bug fixed or
not this is called RETEST.

After retest We are going to carry the test for the entire
application to check because of this bug fix affects the
rest of the application or not. Simillarly some time while
adding the new functionality. This we can say REGRESSION TEST