RE: what test you perform mostly? Regression or retest...
Retesting is the repeated execution of the test case which results in a fault,with the aim that fault has been cured,Regression testing is the renewed testing of already tested program or part after modification with the aim that the modification had not introduced a new fault or exposed any maskfault
RE: what test you perform mostly? Regression or retest...
Retesting is the repeated execution of the test case which results in a fault,with the aim that fault has been cured,Regression testing is the renewed testing of already tested program or part after modification with the aim that the modification had not introduced a new fault or exposed any maskfault
RE: what test you perform mostly? Regression or retest...
Testers often perform the retesting.
According to me retesting is nothing but repeating the execution of test case more than one time with the intent of findings bug.Repeat the testcase execution number of times to verify that functionality work as expected.
Regression testing is carried out only after having new build in which new feature might be added or the previous one might be changed due to the requirement change or due to bug fix. It is carried out on the whole build at once. While regression testing also, we are actually going back and Retesting the software to to check whether the old functionality is not affected by the new modifications.
RE: what test you perform mostly? Regression or retest...
We perform regression testing so many times in the application.Because there are no of versions are released in that application. So,in every version we fix the bugs and these bugs are affected to remaing modules or not is verified that's way we perform regression mostly.
Retesting is depending upon the functionality of the application.This is not compulsory to test the entire application again compaire to regression.
RE: what test you perform mostly? Regression or retesting in your testing process?
Regression testing has been found to be useful, but it is very hard to quanify its value. Ideally, the regression test should be broader than the original bug, as broad as it is practical to do. Regression tests are a relatively low priority because most of them are unlikely to find new bugs, but they take very little effort to create because it is necessary to verify the fix, and the regression is very closely related to that verification. But the whole regression suite should certainly be run before a major version, such as before a beta release, even if it will take an enormous amount of automated test resources because it can prevent an embarrassing regression.
