Why do you do regression testing?
What is Regression Testing?
Regression testing is a kind of testing that is done to confirm that changes in the code is not going to impact the existing effective functionality of the product. This is to confirm the product works fine with new functionality, bug fixes or any change in the existing aspect. Previously implemented test cases are re-executed in order to confirm the impact of change.
Regression test should be a part of the release cycle and must be considered in the test estimation.
When To Perform This Test?
Regression testing is normally executed after confirmation of changes or new functionality. But this is not the case ever. For the release that is taking months to completed, regression tests must be incorporate in the daily test cycle. For weekly releases, regression tests can be executed when the functional testing is over for the changes.
Regression testing is based on retest (which is simply to repeat a test). When retesting, the reason can be anything. Say, you were testing a specific aspect & it was the end of the day- you could not finish testing and had to stop the procedure without deciding if the test passed/failed. The next day when you come back, you execute the test once more – that means you are repeating a test you executed before. The simple act of repeating a test is a retest.
Regression test at its core is a retest of sorts. It is only for the special occasion that something in the application/code has changed. It might be code, design or anything at all that dictates the overall framework of the system.
A retest that is conducted in this situation to make sure that the said change has not made an impact on anything that was already working before is called Regression Test. The most common reasons why this might be conducted are because new versions of the code have been created (increase in scope/requirement) or bugs have been fixed.
Automated Regression Testing Tools
Automated Regression Test is the testing area where we can automate most of the testing efforts. We run all the previously executed test cases on a new build.
This means that we have a test case set available and running these test cases manually is time-consuming. We know the expected results, so automating these test cases is time-saving and is an efficient regression test method. The extent of automation depends upon the number of test cases that are going to remain applicable over time.
Suggested tool:
1. Ranorex Studio
2. Selenium
3. AdventNet QEngine
4. Regression Tester
5. vTest
6. Watir
7. actiWate
8. Rational Functional Tester
9. SilkTest
10. TimeShiftX
Comments
Post a Comment