Regression Testing

A cracked old block beneath new blocks

Regression testing is performed after testing new changes and re-testing fixed bugs. During regression, the tester checks that the existing functionality hasn’t been affected, and that it still works correctly.

How to run regression testing

First, determine how much time you have for regression testing and choose accordingly:

Full regression testing

Running all tests that cover the system’s key functionality

Selective regression testing

Testing only the parts of the system that could have been affected by the changes

The regression testing process is no different from regular testing, except that the test documentation has already been prepared beforehand.

An example of a regression testing bug

Version 1.0.0

A form was implemented called «Online order».

Order total is pre-filled, and the user can enter a promo code to get a discount DISCOUNT10, the final total will be reduced by 10%.

Version 1.1.0

A new feature was added to the form payment method:

  • Pay by card
  • Pay on delivery

When you select «Pay by card», a discount is applied — 5%.

The new feature is being tested and works correctly.

Test form
«Online order»

Bug: When combining the old feature (promo code) with the new feature (pay by card), the final total is calculated incorrectly: the promo code discount is not applied if the user chooses to pay by card.
Task
Task available to premium users!
Sidebar arrow