The LEAP

Automation insights and productivity tips from LEAPWORK.

All Posts

How Frequently Should You Run Your Regression Tests?

Deciding how often to perform regression tests can be a challenge. Particularly when you've automated your regression suite, and are more free to decide the frequency.

As a rule of thumb, you should run your regression tests as often as possible.

The picture below might be a good rule of thumb here: Every time you let a bug out the door, you’ll want to make sure you haven’t let a swarm of new bugs in the door.

LEAPWORK_RegressionTesting_Bugs-1

In other words, your regression suite should ideally be run whenever a change is made to the code. If your software system is large, this is only possible to do with automation. This goes particularly for agile testing teams, where the goal is to get new updates and features tested and released as fast as possible.

 

There are two ways of ensuring that your tests are run at the desired frequency: You can either run them on-demand or on a schedule. 

Scheduled tests are ideal because they ensure consistent feedback on contributed code, and won’t be forgotten or overlooked as a result of other priorities. 

If, however, your test automation tool does not provide you with the option to schedule tests, you should as a minimum run your regression suite in connection with major releases, emergency fixes and incremental code changes. 

But remember that regressions don’t just occur when you submit a change. They can occur in connection with database or system updates, new browser versions, and other changes that are outside your knowledge, and perhaps also out of your hands. 

This is why finding a tool that allows you to schedule your tests is ideal.

To learn more about what to look for in a regression test automation tool, see our checklist for evaluating regression testing tools or download our whitepaper below to learn everything you need to know about regression testing in agile teams.

Download regression testing whitepaper

Maria Homann
Maria Homann
Content Marketing Manager

Related Posts

Best Practices for Building Maintainable and Scalable Test Automation

There’s a major difference between automating twenty test cases and automating 2000 test cases; while it’s completely possible to take an ad-hoc approach when there are only a few test cases, it becomes an entirely different story when test cases run into the thousands.

How to Build Stable Test Automation

Test automation brings many benefits with it, such as increased execution and reduced risk. But these benefits may be diminished if the tests aren’t performing as intended. There are several reasons why tests become unstable, most of which you can turn around by following these best practices and guidelines.

How to Effectively Analyze Test Automation Results

If you have introduced test automation as a means to achieve more efficient testing, you’re probably also interested in making the test result analysis process as efficient as possible. This requires the right approach and the right set of tools.