Read Time - 3 Minutes
What is regression testing?
Essentially, regression testing occurs when a new functionality is added to a site to ensure the update has not negatively affected the core site code. A pack of tests are run and can also be performed on a site after previous bugs have been fixed. Regression testing would need to be performed if new content and updates were added, and if any configuration changes have occurred that could affect the existing site functionality.
Read our 2020 complete guide to website testing.
One of the benefits of software regression testing is that is can be performed on any environment, including pre and post-releases, focusing on key areas which pose a possible risk.
The benefits of regression testing
Regression testing captures any issues that may have been introduced due to a new functionality or any site changes. Performing this type of testing on a pre-launch site ensures that any present bugs are identified and categorised ready for your internal teams to solve, significantly reducing the likelihood of customers encountering any issues on the live site.
Regression testing can also be used as a method of quality assurance. In this instance, you would want to make sure the new functionality added works as theorised, ensure it has been positively tested and qualifies whether the actions match the expected outcomes. This type of quality assurance might not produce a list of bugs, but it does ensure the new functionality and the site work in positive alignment.
Examples of regression testing in action
For one of our smaller ecommerce site clients, we ran a tailored project in which two regression packs were run a month over a 12 month period, in line with their release schedule. For this regression test strategy, each test pack contained 75 test cases each and identified 12 critical defects, which if launched would have had a major negative impact on customers. This impact could have resulted in a significantly reduced conversion rate and revenue intake for the year. Subsequently impacting bottom-line results, and questioning the quality of work produced by internal teams from higher management.
In the case of a large-scale global brand, we have run 150 regression testing packs over the past 12 months. These packs were deployed over 5 different environments from development to production. The results of these tests have identified over 2000 different defects which would have had a major impact on customer experience.
What happens during a regression test?
Digivante has two different approaches to regression testing. The first type occurs when the client provides the regression pack, which is then translated into our system via the Digivante portal and deployed to our community of expert regression testers. Our internal teams will also review the supplied regression pack, identifying any gaps or possible issues to ensure an accurate amount of coverage is provided, improving the overall results of your test.
The other approach is employed when a client hasn't supplied a regression pack or the current regression pack is out of date. During this process, our internal teams will construct a regression pack from scratch for the client's website or app. Throughout the construction stage, we maintain a high level of collaboration to ensure the coverage encompasses all areas of focus while providing an open forum for the client's internal teams to provide feedback.
How does Digivante perform regression testing? Click here to find out.