What is Difference between REGRESSION TESTING and RETESTING.

Questions by jitusonawane   answers by jitusonawane

Showing Answers 1 - 32 of 32 Answers


  • Feb 28th, 2006

Regression - You will do all the test procedures once you make any new change or add a new functionality
Retesting - You will do testing for only the Changed Scenario


  • Feb 28th, 2006


Regression Test. We will test all the modules, ones u make any change in the application. Just make suere whether the added functionality have been affected the existing functionalit or not.

Where as in ReTesting, we will test only particular module, in which u made changes.


  • Mar 3rd, 2006

Regression Testing means to test the entire application to ensure that the fixing of bug will be affecting anywhere else in the application

Retesting means executing the same test case after fixing bug to ensure the bug fixing.


  • Apr 6th, 2006

 Retesting is to test the same application with multiple test data.

 Regression Testing is to test the modifies build to ensure the bug fix work and ocurrences of side effects.

  Was this answer useful?  Yes


  • Nov 12th, 2006

Retesting means::we test only for particular module what u made changes.....regression testing: we test all modules even if u made a change for one module

  Was this answer useful?  Yes

Ajay Kuamar Rai

  • Mar 28th, 2007

Regression Testin: In Regression Testing , we test the  whole appliaction after change is made  to make sure that  , changes  does not effect   previous functionality
ReTesting : In retesting , we  tset ony only particular things that is  working properly or not after change is made.In this  we did not test all functionality.

  Was this answer useful?  Yes


  • May 11th, 2007

Regression Testing: We can conduct the test on a modified build to ensure the bug fix work and occurence of side effects in that build.

Retesting: We can do the test on a build to ensure the correctness of the modified functionality.

  Was this answer useful?  Yes


  • Jun 11th, 2007

Regression: Testing the entire module after bug has been fixed.

Retest: Testing the specified bug after bug has been fixed.

good luck

  Was this answer useful?  Yes


  • Jul 20th, 2007

RETESTING : Testing a same application/build in order to find the defect is called as retesting.

REGRESSION TESTING: It is carried out to check whether a changed component of the application/build has introduced any new bug or not.

  Was this answer useful?  Yes

Murali Reddy R

  • Jul 26th, 2007

The re-execution of test on modified by build to ensure bug fixing work and accurence of any side effects, Test engineer coduct using this test on automation. Retest means re-execution of a test with multiple test data to validate a function.

  Was this answer useful?  Yes

Retesting: This means testing a particular module after fixing the identified bug to ensure that changes are working correctly.

Regression Testing: This means testing the entire module to ensure that changes made in particular module do not affect previous functionality.


  • Sep 18th, 2008

Retesting: If any change is made into the application, testing only those
changes and not the entire application is known as Retesting.

Regression Testing: If any change is made into the application, testing the
entire application to ensure that changes made has not broken any existing
functionality is known as Regression testing.

  Was this answer useful?  Yes


  • Sep 4th, 2009

Retesting means testing bugs which are produced and Regression means checking new functionality added which will not affect other areas of application.

  Was this answer useful?  Yes


  • Oct 22nd, 2009

Regression Testing: Testing of a previously tested program following
modifications to ensure that defects have not been introduced or uncovered in
unchanged areas of the software, as a result of changes made.  It is
performed when the software or its environment is changed.

Re-testing: Testing that runs test cases that failed the last time they were
run, in order to verify the success of corrective actions.

  Was this answer useful?  Yes


  • Oct 25th, 2009

When the changes are introduced to the code or environment then regression testing is done WHERE the tester RETESTs the changed code with same inputs he used during first iteration so that test is covered and no new bugs are introduced due to changes made.

  Was this answer useful?  Yes

Regression Testing: Testing an application aftre a bug is fixed. It is again of three types Unit regression testing, Regional Regression Testing and Full Regression Testing.

Unit regression testing: Testing the application for the particular Bug fixed like the warning Messages, pop ups etc, fixing these will not affect the application

Regional Regression Testing: Testing a module for a bug fixed in the application. like suppose username field accepts "8-15 numbers", but requirements is changed to 10-20 "characters". we will have to test whole Login module.

Full Regression Testing: Full Regression Testing is testing the whole application if a critical bug is fixed and has impact on vaious other modules. This also done before release, to ensure application is working fine.

Re-testing: Testing the application again or re-executing the Test cases. Though aftr a release there remains no difference between Full regression testing and RE-Testing

  Was this answer useful?  Yes

REGRESSION Testing is testing an application or build software with an intention that it does not have any impact on other areas or modules of build software. 

Whereas, RETEST is testing a build software again and again with an intention to minimum the defects.

  Was this answer useful?  Yes

Regression Testing: This is done after the bug is fixed to ensure that while fixing the bug? other functionalities are not affected and are working fine, so we need to have a good idea how the corrected functionality? is linked to other codes are functionalities ,modules and we can execute only those test cases which are related to it.

Retesting:Once the bug is fixed , the functionality needs to be tested to confirm that it is really fixed and this testing is called as retesting.

  Was this answer useful?  Yes

Regression Testing:
If a piece of Software is modified for any reason testing needs to be done to ensure that it works as specified and that it has not negatively impacted any functionality that it offered previously. This is known as Regression Testing.
Re Testing:
Testing the already tested functionality again and again by using multiple sets of data(Test Data)
If not correct,reply me

  Was this answer useful?  Yes

faiz dafedar

  • Oct 4th, 2011

REGRESSION TESTING :It is finding of new errors in existing functionality after changes have been made to the application and checking whether that error has affected other part of the application.

RETESTING. :Testing a particular module for a particular bug by testing again and again

  Was this answer useful?  Yes


  • Nov 1st, 2011

In regression testing: you are testing on module that has been already been tested. The functionalities have been tested but you have to test them again.

Re-Testing: Very similar to regression testing. You are testing on a module that has been already tested.

  Was this answer useful?  Yes

prashant baviskar

  • Nov 3rd, 2011

Regression Testing : Testing the application as because the change made in any Module of the application has hamper ed the other part of the application or not is called as Regression Testing.

Retesting : Testing the Defect after it is fixed (testing the Released Defects) is called as Retesting.

  Was this answer useful?  Yes

vamshi patha

  • Nov 5th, 2011

Regression testing is done after a new module is added to the project........retesting is done on the complete project for the second time.............

  Was this answer useful?  Yes


  • Dec 23rd, 2011

Testing Conducting On The modified build whether the resolved defect is effecting to the remaining functionalities or not

  Was this answer useful?  Yes

Regression Testing is done to check whether adding/deleting/modifying any module in the application is affecting any modules or not i.e. it ensures that other modules are not affected by the change.

Re-Testing is done to check whether the bug reported earlier in a particular module is fixed or not.

  Was this answer useful?  Yes

aswani kolla

  • Apr 16th, 2012

Retest is the process of checking whether the reported bugs are been fixed or not by the development team

Where as Regression is conducted after few changes in build we have to verify those changes are effected to some other places in application/not?

  Was this answer useful?  Yes


  • Apr 20th, 2012

ReTesting: we will test the fixed bug/failed test case with multiple test data whether the issue working as per the functionality

Regression Testing: we will test total or related scenarios/functionality (passes test cases along with failed test cases earlier which are got fixed now) to make sure that should not produce/cause the new defects after code/config changes

  Was this answer useful?  Yes


  • Jun 18th, 2012

RETESTING: testing the application again to ensure whether the defects are really resolved/closed or not.

REGRESSION TESTING: testing whether the fixing of bugs has affected other functionality of the application?

  Was this answer useful?  Yes


  • Jun 21st, 2012

Retesting: Testing the functionality of the application frequently to ensure that the changes made in particular module is working properly/not.
Regression: Testing the entire functionality of the application again and again in different builds to ensure that the changes(add new module/ delete some functionality/ modify the existing application/CR/ defect fixes) made does not affect the existing application functionality.

  Was this answer useful?  Yes


  • Nov 5th, 2012

Retesting is testing again after fixing a defect. we are testing the particular module only what we have changed and testing the test case in the same build.
Regression testing is the testing the system which doesnt give any new defects through changing or fixing code in any area.The main objective of regression testing is to validate the changes introduced which does not adversely affect the whole code due to new product releases enhancement or error fixing.Here we are testing the test case in the new build and testing the entire module.As a regression tester we need to ensure that it wont give any negative impact or defect on the existing functionality of a application, if any modification or enhancement comes in the application.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions