Regression Testing

Regression Testing

Why Regression Testing?

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.

How we test

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.

What cases we retest

  • tests with high bugs frequency
  • cases checking core functionality
  • tests for verifying features for visible for users
  • integration tests
  • failed test cases
  • complex tests
  • boundary value tests.
Regression Testing process

Last-minute fixing effect

Regression testing 600400
The majority of bugs detected by end-users after the product release are caused by last-minute issues fixing. Supposed to be fully removed, they are not retested because of limited time, lack of budget, or other reasons. But even a slight modification of software may cause inevitable changes and break the whole system.