RE: Difference b/w retesting and regression testing?
Example: There are 10 testcases to be passed for a requirement. But 10th testcase failed and tester raised a defect in the defect log.
Retesting: After the above defect is fixed tester need to execute the 10th testcase to check the expected result for the same.
Regression Testing: After the above defect is fixed tester need to execute the 20 of above testcases by selecting randomly to make sure that existing functionality is not broken because of the above fix.
RE: Difference b/w retesting and regression testing?
Retesting
Its a test that on the last occassion u ran it the system filed & now v repear that same test to make sure tat the failure has been eliminated.
Regression testing
V need to check that when changing the faulty code the developer doesnt introduced a new bug into the system. This type of testing is said to be regression teting.
There is a 50 chance of introducing regression faults.
The moral of the regression test says that there will be some risk areas in the software.
RE: Difference b/w retesting and regression testing?
Regression testing is any type of software testing which seeks to uncover regression bugs. Regression bugs occur whenever software functionality that previously worked as desired stops working or no longer works in the same way that was previously planned. Typically regression bugs occur as an unintended consequence of program changes.
RE: Difference b/w retesting and regression testing?
Hi
Retesting:- after fixed the bug tester will test that perticular buggy module to be ensure whether the bug actully fixed or not that is called Retesting.But to test other related modules functionality to be ensure that whether those related modules functionality affected or not is called regression testing.
RE: Difference b/w retesting and regression testing?
ReTesting:after fixing any bug u'll again re -test ur application with the given set of data to confirm that the bug is fixed.
Regression:which is nothing but RETESTING on the modified build to ensure that the bug is fixed and at the same to give an assurance that the bug fixation has no effect on the earlier functionalities.