10/17/15

Re-Testing & Regression Testing

Re-Testing: After a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This is called Confirmation Testing or Re-Testing
Regression testing:  Testing your software application when it undergoes a code change to ensure that the new code has not affected other parts of the software.

Retesting:

In this type of testing, the tester re tests the application which was earlier reported as a bug and now fixed by the developer. This bug can be due to functionality issues as well as design issues. Retesting the functionality of a button which was previously not working or testing the alignment issues of a page etc can be listed as examples for retesting.

Regression testing is done to test whether the changes made on the site have any impact on other modules which were earlier working fine. New requirement change, implementation of new functionality are some of the scenarios where regression testing is effective. Regression testing can be automated using effective automated tools such as Selenium, Quick Test Professional etc.

Regression testing:
Refer the given example for further understanding:
For example, we have a image uploading field which supports only certain image formats say JPG, PNG etc. Suppose one of the image formats failed (say JPG) and the developer fixed it. Testing the functionality, after fixing this bug is retesting. Here, testing and ensuring whether this new change (fixes) has not altered the working of other fields on that page is regression testing.
In normal cases, regression testing is carried out only after retesting of the application. But there are exceptions where both testing are carried out simultaneously. While testing a website, make sure that the application have undergone both retesting and regression testing.



0 comments:

Post a Comment