Welcome to the final episode in our new series “Integrating testing into your development flow”. Today we are going to be looking at “Regression Testing”.
In our last presentation we will be talking about User Acceptance Testing. What it is, when should we do it, who does it, and why is it so important?
Today we will be talking about the last step in the test process Regression Testing. Specifically, what it is, when should we do it, who does it, and why is it so important?
What Is Regression Testing
Regression Testing is nothing but a full or partial selection of already executed test cases which are re-executed to ensure existing functionalities work fine. We do this type of testing to make sure that new code changes do not have any side effects on the existing functionalities. Regression testing is started after functional testing, to verify that the other functionalities are working. In the corporate world, regression testing has traditionally been performed by a software quality assurance team after the development team has completed work.
This series comes from our mentoring/mastermind classes. These classes are virtual meetings that focus on how to improve our technical skills and build our businesses. The goals of each member vary. However, this diversity makes for great discussions and a ton of educational value every time we meet. We hope you enjoy viewing this series as much as we enjoy creating it. As always, this may not be all new to you, but we hope it helps you be a better developer.