Analysis and Comparison of Regression Testing Tools

Abstract

Changes are the indispensable part of any software life cycle. Regression testing performs to ensure that, after making any changes in software, the existing functionality is not being affected. The purpose of regression testing is to detect unexpected faults—especially those faults that occur because a developer did not fully understand the internal code correlations when he or she modified or extended code that previously functioned correctly. So, regression testing provides different tools to test the adverse effect of changes on stand alone and web applications/pages. In this paper, various Web based and Window based Regression tools will be analyzed and them a comparison will be presented on these tools. Regression vs. Retesting:- Regression testing can be performed at each stage of development to fix the bugs after change. Retesting is not fully equivalent to Regression test. The major distinction between regression and retesting is that Regression testing is performed to ensure that no adverse has would be detected after making changes in application where as Retesting is performed to fix the code. Defects can be opened again to fix the code in retesting, but in regression the major aim is deny the adverse effect of change and can use only selected test cases in regression testing. Both testing occur side by side but having different objectives. Regression testing can be performed by any of the following approaches as