Regression Testing VS ReTesting - Bug Reaper

                  Bug Reaper

Lean about Automation Testing,Selenium WebDriver,RestAssured,Appium,Jenkins,JAVA,API Automation,TestNG,Maven, Rest API, SOAP API,Linux,Maven,Security Testing,Interview Questions

Friday 27 September 2013

Regression Testing VS ReTesting



a.)ReTesting- This is done to check if the Fix done by the Dev for the Defect works Properly.

Regression Testing-This is done to ensure that the fix of the Defect does not have any impact on the original functionality of the other modules of the application that was working fine before applying the fix.


b.)ReTesting- It involves executing the test Cases that were failed eariler.
Regression Testing- It involves executing the Test Cases that were passed in the earlier builds.

Crunch- Re-testing is just testing the bug fix and regression testing is something when a bug is fixed it doesn't affect the other functionalities in the application.When regression testing is done its like testing the whole application.
Regression Testing is required whenever there is a
a.)Change in requirements and code is modified according to the requirement
b.)New feature is added to the software
c.)Defect fixing
d.)Performance issue fix

Regression Testing Tools



Such tools are required by the Software Testing team whenever software undergoes frequent changes

In such cases , Manual execution of test cases is not the right approach as it increases test execution time as well as  costs.
Automation of regression test cases is the smart choice in such cases.
Following are most important tools used for both functional and regression testing:
> Quick Test Professional (QTP):
> Selenium:


No comments:

Post a Comment