Regression testing: This is a kind of testing your software application when it undergoes a code change. It helps to ensure that the new code has not affected other software parts.
Re-Testing: After a bug or fault is detected and fixed, the software should be retested to confirm that the original defect has been effectively removed. This is called Re-Testing or Confirmation Testing
The distinction between re-testing and regression
Regression
· To find out the issues which may get introduced because of any modification in the app
· The purpose is that any new change in the application should not bring in any new bug in existing functionality
· Verification of bugs are not countable in the regression testing
· It can be done in parallel with retesting
· For regression testing test cases can be automated
· Defect verification is not coming under this type of testing.
· Regression testing is performed only when any fresh new feature is implemented or any modification has been carried out to the code.
Re-testing
· To confirm whether the failed test cases in the final execution are working appropriately or not after the glitches have been fixed
· It ensures that the bug or issue is resolved and the functionality is working as anticipated
· Verification of bugs are incorporated in the retest
· Retesting is done before the regression testing
· For re-test, the test cases cannot be automated
· Defect verification always comes under Retesting
· It is executed in the same environment with the same data but in new build
Follow me on:
Comments
Post a Comment