What is meant by Retesting & Regression Testing?
Bharathi
Printable View
What is meant by Retesting & Regression Testing?
Bharathi
What i can comprehend your question is you want to know the difference between restesting and regression testing. [b][u]retesting [/u][/b]simply means repeating a test case whereas when it comes to regression testing a plethora of cases open. [b][u]regression testing [/u][/b]is defined as the [u]selective [/u]retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the modifications and that newly added features have not created problems with previous versions of the software regression testing is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors. It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity. [b]advantages of regression testing [/b]: [list][*]it increases our chances of detecting bugs caused by changes to an application - either enhancements or bug fixes. Note that we don't guarantee that there are no side effects.[*]it can also detect undesirable side effects caused by changing the operating environment. For example, hardware changes, or upgrades to system software such as the operating system or the database management system.[*]the regression test set is also useful for a new way of doing integration testing. This new method is much faster and less confusing than the old way of doing integration testing - but you need a regression test set to do it.[/list]
Retesting is testing the bugs are fixed or not which were reported.
Regression testing is to test whether the modifications are giving rise to new bugs.
Retesting means, testing the application with multiple inputs.
where as, regression testing means testing the application after any update in the code to ensure that modified code has not affected some where in the functionality.