katha

• Sep 18th, 2006

 

Regression:Is there any probelm or issue for existed functionality  due to addition of new patch or fix.

Retesting:When ever there is a major fix in regression testing, then we will go for retest, means we need to execute all the testcases, what we have executed already.

Both are not same.

Regression testing will be done based on the issues and retesting will be done with in regression testing, if there is any issue is going to fix

phanikumar

• Sep 20th, 2006

 

Hi ,

Regression testing is done on modified build i.e., build is arrived with changes or any bug is fixed.

Retesting is done on same build. this is to ensure that all major functionality is tested and nothing else missed.

They r not same at all!!!!!

Normally when build arrives tester will go for sanity testing. i.e., whether the build is stable enough, all the images/links are opening......

System testing covers functional and non-functional testings

functional testing: functioality testing,input domain testing...

non-functional: performance,security,compatability.......

I hope i might have cleared u some what.......

correct me if i m wrong......

Phanikumar,

TestEngineer

reach me: @09986293787

mail: gk.phanikumar@gmail.com

manish gupta

• Sep 22nd, 2006

 

Regression testing we do when there is any change in coding because of bug fixing or new functionality has been added and we got new build for that.Retesting we run the same test cases on the same build because of any bug fixing to check the functionality of the system.

samuel

• Oct 10th, 2006

 

Regression Testing: After debugging, testing the fixed bug and checking whether the bug has introduced any new bug in the related area or in unrelated area of the module.Retesting: Testing the same functionality or application several no. of times

Suri

• Oct 14th, 2006

 

regression testing after the bug is fixed we will test

 

retesting testing the same module for different combination

for eg take fact(n) testing for n! we will test up to n!(1,2,3,4,..............n)

 

 

Debasis

• Nov 24th, 2006

 

Regression testing is testing the critical functionalities of a module after an enhancement or a bug fix. These modules might have been working fine before. But while fixing a bug the developer might have done some accidental errors which could have resulted in some new bugs. To safe guard this we do regression testing.

After a bug is fixed, we retest it to confirm that it has been fixed properly. If not, we flag the bug as reopen and again send it for proper fixing.

So the purpose and scope of regression and retesting are completely different.

Check my site (http://bug-free-zone.blogspot.com) for testing related information.

kumar

• Dec 12th, 2006

 

Retesting os done on same built with multiple test data where as regression is done with same data.

If bug found on major functionality area we go for regression testing other types we go for retesting.

subho ghosh

• Feb 1st, 2007

 

Regression testing: is re-execution of some or all test cases after fix or chane anyRetestin: Retesting is Re-execution of all test cases

Madhavi

• Feb 1st, 2007

 

Hi All,Regression Testing means testing the application after the bugs are fixed.Retesting means, testing the application irespective of bugs fixed or not.Plz correct me if I am wrong.Thanks,Madhavi

villjuj

 Profile Answers by villjuj Questions by villjuj

• Feb 7th, 2007

 

Regresstion Testing-For exisiting build ,we have executed set of test cases ,that we are executing with the new build(may have some bug fix or new functionality or features might have added)Re Testing- Repeat the execution of test cases after a bug is fixed to verify the bug has fixed properly.If not fixed properly,Reissue the same.

Guest

• Feb 14th, 2007

 

Regression Testing :Steps:1)The re-execution of test cases on new version build which are failed in old version build.2)Also execute those test cases which are related with above test cases.In order to check whether the related test cases are passed or failed.Ex : Test Case(1) + Test Case(2)=100If Test Case(1) is failed in old version build,then execute Test Case(1) and Test Case(2) in new version build,because Test Case(1) depends on Test Case(2) or TestCase(2) depends on TestCase(1).Retesting :Execution of all Test Case(Passed or Failed) of build.

vikram prakash

• Mar 28th, 2007

 

Regression testing ensures that our system is not effected due to some changes in our system.
Retesting testing is performed after the some changes in our system.
Both are not same, regression testing shows the how many times retesting testing
Will be performed.

udhaya

• Apr 2nd, 2007

 

Regression testing:
                    After Bug Fixing Re-execute all test Cases. Why the bug fixing can be possible for new Bugs.

Retesting:

        To check the fixed Bugs only.

Rupa Debnath

• Jul 22nd, 2007

 

The difference between Regression testing and Retesting is that :-

Regression testing is done to test whether the bug found is fixed or not and also does the fixing of the bug has created any ill effect or any further modification has arrived on the functional part of the product due to the fixation of that mentioned bug. It is done every time as a new bug is found and this is done to make ensure that the bugs are fixed and the build is doing expected work without creating anyother bug and it's not deviating the result from expected result.

Retesting is done to make sure whether the mentioned bug is fixed or not after the development team ensure that the bug is fixed. It also verifies process or also checks the procedure . It is always done after the fixation of bug

aparna

• Sep 26th, 2007

 

We can call regression testing a type of re-testing.

Regression testing as we know is testing the application to ensure that no new errors have been introduced as a result of the fixes done to a previous release and the fixes are also in good condition.

Re-testing means testing the system again mayb for a new release or the same.We may just simply need to run the test cases again without any change just for the sake of maintenance.

Lokesh thakre

• Oct 4th, 2007

 

Madhvi,

I think the difference between regression testing and retesting is this
The Re-Execution of a test on same application build with multiple test data is called ReTesting.
Regression Testing: the re-execution of a test on modified build to ensure bug fix work and possibilities of side effect
occurrence .

Lokesh
(QA)
09998772434

parsu

 Profile Answers by parsu 

• May 13th, 2008

 

A tester finds the bug and then reports the same in the tracking tool used. Now there are 2 scenarios which come up when a new build is given saying that the reported bug has been fixed.

Regression testing: When ever evsome fix has been made we have to check whether the fix has impacted any dependent functionality. So that some thing that was working correclty earlier has not been effected by the new fix.

Retesting: When ever the fix has been made and  a new build is given saying that the reported bug has been fixed. We have to retest that bug. So restesting basically means that the tester tries to confirm whether the bug he/she had reported earlier has been fixed now or not. If yes then close the bug if not then reopen the bug.

geek_niladri2009

 Profile Answers by geek_niladri2009 

• May 26th, 2008

 

Regression Testing:-After fix the bugs verify whether new faults are generated or not in the related modules or other module in system
Re Testing:- Repeat the execution of test cases after a bug is fixed to verify the bug has fixed properly.If not fixed properly,Reissue the same.

SONIA25

 Profile Answers by SONIA25 

• May 28th, 2008

 

Re-Testing "Whenever a fault is detected and fixed the software should  be restested to ensure that the  original fault has been sucessfully  removed"

Regresion testing "attempts to verify that modifications have not caused any unintended adverse effects in the unchanged software and the modified system still meet its requirement"

When a bulid arrives for testing a smoke test is run to determind the build is stable and can be considered for further testing.Testers usually do smoke testing to accept the bulid before testing.Tester here "touches" all the area of the application but without getting deep into its functionality"

I hope i am correct