Executing the same test cases on the same build with
different inputs ..

 ok i'm not sure about Suresh's Answer.

unless a tester verifies with all different inputs,testing 
is not completed.

In a Real environment of Testing,retesting means:
A tester finds a bug and reports to test lead/developer,
developer fixes the issue,and you can go ahead with your 
testing.
then the tester verifies the same functionality using same 
input which showed the bug,along with all other data 
provided to use on this functionality.
this is when you call the functionality is under retesting.

First answer is currect but i don't know abt second.

retesting means test the build using different test data.
this resting comes under data driven testing in winrunner

Retesting bugs in the system which had been identified as 
fixed, usually starting from Alpha on. 

Executing the same test cases on same functionality with 
multiple sets of data is called Retesting.In WinRunner it 
is also called as Data Driven Testing.

Executing the same testcases with same set of test data to
retest a bug which was already having status Fixed.

Answers 1, 3 and 5 are exactly correct. There is no doubt 
at all. Some the remainig answers valid for the regression 
testing.

What I see here is retesting is another conformation of the 
software for its quality and user friendly objectives so 
that fruther no user can say it is causing trouble to them.

Re Execution of test cases on the same build with diff 
input values

the reexecution of the test on same application build 
with multiple test data is called as retesting.

ReTesting means validating the bug after the bug is fixed 
by the development team.

The reexecution of atest on some application build with 
multiple test data is called retesting

hai

Retesting means check whether the bug is fixed or not.

hello every one,


Re-Testing:

    Executing all pre-defined (Same Set of Test Cases) 
which is carried after bug verification.

First: Bug File

Second: Bug Severity

Third: Bug Priority

Fourth: Bug Fix

Fifth: Bug Verification (Set by the developer to with 
release version the bug fix is done)

Sixth: May be 2nd Cycle of Testing or 3rd Cycle of Testing 
or ..........nth cycle of Testing.

THE SIXTH STAGE OF TESTING IN DIFFRENT CYCLES IS CALL RE-
TESTING, WITH RESPECT TO MANUAL TESTING. 

WITH RESPECT TO AUTOMATION TESTING THE ANSWERS ABOVE 
MENTION ARE CORRECT. 

I would like to corrct sujatha with some info: 
Cehcking whether the bug is fixed or not correct to UNIT 
testing which is done at developer environment, where as 
when it comes to Testing environment we should reffer to it 
as Verification of the Bug. 

With respect to Testing Team Re-Testing means 
executing "same set of test cases" been executed in 
all "Number of Test cycles" as depending on the SDLC model 
and STLC model or as defined or required by the Project 
mangement for that project cycle.

I hope this solves all issues! 

you can post for more details

Thanks,
Software Quality Test Team.

Re-testing means Re Testing of the Application. It is not 
Regression testing. Regression testing is done after the 
successful completion of Re-Testing.

For Example you have an application which is compose of 10 
modules. Modules 4,5,10 are interlink means. On your first 
phase of testing you find a bug on module 5 which is having 
10 test cases.

On your second phase of testing you should first do the re-
testing of the fix bug, you have to re execute all the 10 
test cases of the module, i.e Re-testing

After successful completion of  re-testing you will execute 
all the test cases of module 4, 10 as, the two module is 
inter related to the module 5. i.e Regression Testing


Thanks
Manas
manasbarik@rediffmail.com

When a Tester finds a bug in the software, the coder fixes 
the bug by making the changes in code.
Now the tester will check the same sceanrio again to see 
whether the bug still exists or it is working fine.here he 
will be exceuting only those failed test cases for that 
particular Module which were responsible for that bug. This 
is called Re- Testing. 

But the changes done in the code will have impact elsewhere 
also i.e in the other areas and Modules. So we have to 
execute all the test cases to see that the changes done in 
the code has not affected the other areas also. This is 
called regression testing.

After fix the bug, re test whether the bug which is found 
has been fixed or not, is called as Retesting.

If you can understand the main difference between Re-Testing
and Regression Testing, it makes you better understanding
about the theme of Re-Testing.

I want to explain this with a simple example:

There are 10 modules. say there is a modification in 5th
module. After doing the modifications in 5th module we have
test so that we can find out is that modification is
directly or indirectly effecting the application or not.

So, Testing only 5th module where we got the bug is
Re-Testing...

Testing entire modules from 1 to 10 is called regression
testing.

Please correct me if I am Wrong;

sbonkuri@datamonitor.com

Re-execution of all test cases with the multiple data in 
the bug impact area is called retesting.