QATestLab executes regression testing to verify that a system operates properly according to the specified requirements after modifications or changes. By retesting the same test cases, we make sure that no side-effects appear in existing functionalities, and a new code does not affect the old one. We perform regression testing when requirements, that might cause code modification, were changed, new features were implemented, and detected bugs were fixed.
To determine a proper frequency of regression testing, e.g., after bug fixing or build updating, we take into account the software specifics, deadlines, and available testing means. As successful regression test runs cause the increment of suite volume, we are always trying to minimize the size of test suite to stay within the time schedule and project budget.
By performing regression testing, we can retest entire test suites. But the technique requires much time and resources. To avoid extra expenses, we conduct regression test selection and execute particular tests that potentially may detect issues. Based on business goals and functionality characteristics, we assign test cases with correspondent priority to reduce the test suite size.
In order to make regression testing efficient, we select test cases for re-execution on the basis of particular parameters.