What is the difference between retesting and regressive testing?

Showing Answers 1 - 17 of 17 Answers

kalaivani MAnoharan

  • Sep 7th, 2011

For regression testing means to test the application without any side affects.. if we are changing any modules that changes will not affects other modules...

For Retesting after fixing the bugs again we are run that same application... that s retesting..

This is my idea... i don't know whether its correct or not...


  • Sep 8th, 2011

Re testing is testing after the defect is fixed. To check whether the defect does not appear again after it is fixed.
Regression testing is to test whether the changes made to fix a particular defect, does not affect the other functions in that application.

  Was this answer useful?  Yes


  • Sep 9th, 2011

Regression testing means ,testing the same functionality again and again whenever build gets modified in-order to check all the existing functions are working .... according to the specified requirement or not.Regression test starts from 2nd build and continuous up to last build.
Re-testing means,testing the same functionality again and again with different sets of data.Retesting starts from 1st build.

  Was this answer useful?  Yes


  • Sep 10th, 2011

Re-testing means testing the application(Functionality) once defect got fixed. Where as regression testing means repeated testing to ensure existing functionality does not change. It should be as per requirement specifications.


  • Sep 14th, 2011

Re-testing is a type of testing in which one will perform testing on same Functionality again and again with multiple set of values in order to come to an conclusion whether that Functionality is working fine or not.

Regression Testing is type of testing in which one will perform testing on the already tested functionality again and again.Generally it will be done in 2 scenarios.

I)Whenever the test engineers find any defects,raised it to the development department and after rectification the next build is released then the test engineers once again will check the defect functionality and it's related parts.
II) When ever some new features are added to the application next build is released to the testing department then the test engineer will check the all the related feature of those new features once again.

  Was this answer useful?  Yes


  • Sep 15th, 2011

To start with suppose your testing an employee module in that your testing employee salary sub module after testing the employee record ,employee attendance record and all other sub modules while testing employee salary module u come across a bug related to emp name and attendance that is data integrity is not maintained, some improper data is coming through previous sub module/module,so when u log this bug and when again you retest this thing its called 'retesting' and against checking all other sub module / module which are related with this sub module/module is called 'regression testing'.

Thus retesting is testing the same bug again to see whether its fixed or not and regression testing is to test whether changes made by developers in the code or ne other change to fix the bug is not propagated in other already tested modules...

I hope this will help

  Was this answer useful?  Yes

Retesting is nothing but using different test data for the same test case.For eg: If you have a testcase , the purpose of which is to check a text field on a screen which accepts only numeric values, then Retesting would be to enter different values for the text field and check whether it accepts all values.

Regression testing on other hand involves testing other areas of the application that this field would impact.
suppose you have a submit button on screen after you enter the numeric values in text field, then click on a submit button would be one of the regression tests. Also testing other areas of application comes under Regression testing.

  Was this answer useful?  Yes


  • Sep 22nd, 2011

Regression Testing is performed to make sure that the new changes doesn't affect the other modules/application whereas retesting is to test the already tested functionality/behaviour.

  Was this answer useful?  Yes


  • Sep 29th, 2011

regressive testing starts from 2nd build
retesting starts from 1st build onwards

if any build release for testing that time starts retesting this time the test engineer find any bugs this build can send back to development team and developer can modify the build and again release testing process so this time the test engineer will check the modified build once again this is regressive testing different kinds input to be tested in retesting

  Was this answer useful?  Yes


  • Oct 11th, 2011

Regression testing : to check if an issue fixed, has brought any changes or new issues in other areas, that were working properly prior to this fix

Retesting : to check if an issue is fixed or not

  Was this answer useful?  Yes


  • Nov 1st, 2011

There is no such term called "regressive" testing. I think you meant "regression" testing. Please you correct terminology.

To the people who reply to questions: You are all doing a good job, but do not forget to read the question completely and correct the person who posed the question if necessary. Please sound confident when you answer questions..

What do you do when a developer tells you that he bug you logged/raised has been fixed? Do you take it on his face value and close the bug or do you test it again? Of course, you'd test it again. This is re-testing.

Regression testing:
(a) When you raise a major/critical bug and dev has fixed it. You re-test and close it if indeed it looks fixed.
(b) when a brand new feature is introduced to an existing application, you test the new feature and then make sure you close all the bugs related to this new feature

In the above 2 cases, you do regression testing to make sure the "newly" introduced "feature" or 'bug fixes' have not caused other surrounding (pre-existing) functional features to work in a manner that deviates from expected behavior; in short bugs!
So you pick test cases from the existing test suite (group of test cases) and run them to make sure the surrounding functionality is not affected due to the bug fixes / new feature.
That's regression testing in nutshell.


  • Nov 18th, 2012

Retesting Means Testing only particular module ( functionality) after fixing the issues.
Where as Regression testing means testing entire application functionality. After adding the new feature to the application, to make sure existing functionality does not change.

  Was this answer useful?  Yes


  • Jul 14th, 2014

Retesting - Just retest / re-validate if the defect is fixed. It’s always talking about the particular fix NOT the entire App.
Regression testing - After all Defect are Fixed and Closed, might be those changes in the code will affect other areas of the Application, So identify those areas and conduct the testing is call Regression Testing. Some times may be entire Application OR part / Particular modules of Application.

  Was this answer useful?  Yes


  • Oct 28th, 2014

Retesting means :User verify the the last test results after the fix
Regression mean:After any fix or any enhancement is there any side effects to the product..

  Was this answer useful?  Yes


  • Nov 26th, 2014

Whenever there is a change or updation in codings or requirements regression testing is performed it is done to validate that the changes had cause any impact to other modules in a project. Whereas in retesting is to validate the existing testcase after a bug has been fixed.

  Was this answer useful?  Yes


  • Dec 6th, 2014

Retesting is the testing performed on a fixed defect to verify it is working fine or not.

regression testing is the testing performed on the modified application to verify whether the fixed defect is impacting on the other related functionality of 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