Re-Testing

How would you estimate the amount of re-testing likely to be required?

How would you estimate the amount of re-testing likely to be required?

Hi Ajit,

Retesting is mostly done for the Defects. In General, Validation of defect is also called as Defect Retesting. The time estimation for retesting a defect is done by the severity of the defect, which may either be Very high or high or medium or low.

Following are the points that are taken into consideration for calculating the estimation for Retesting.

1. The Data required for validation.
2. The complexity of the reports that are to be generated
3. The complexity involved in terms of database validation
4. Number of Regression test cases that are to be executed.
5. Number of validations required for retesting the defect (i.e, how many times the same test case to be executed with different sets of input)
6. The team composition involved in retesting
7. Strength of the team involved in retesting, i.e., whether the tester has already retested the same defect.

Hope this would have helped you.

Regards,
Ganesan

[QUOTE=judhajit;22686]How would you estimate the amount of re-testing likely to be required?[/QUOTE]

It depends on what you have to retest and in which environment you will retest it.

Hi Ajit,
Re-testing is nothing but testing the defect in the next release.

We used to track defects using Quality Center 9.0 as a bug tracking tool.When the developer fixes the defect raised by a tester,he will change the status of the bug as "Retest".We have to re-test the defect in the next release.we have to keep track of the "Build Release Date".Once you reach the Build Release Date,we have to re-test the defect.

There is no estimation about re-testing.

Ultimately Every company will have a rule like ,after particular percentage of bugs are flushed out,the build is stable.

Please correct me ,if i am wrong...

Regards,
Krishna
The undertaking of a new action brings new strength....