There is a dichotomy when it comes to regression testing.
Not enough regression testing and you risk bugs slipping through to production, too much regression testing and you and your team become swamped.
This means smaller more regular releases or changes to run regression testing against.
An exploratory testing session using previous session notes can guide testers enough but also still free them to catch bugs that test scripts might miss.
It’s also important to look at a team’s maturity, culture and development approach and assess how that might impact your regression testing approach.
A good regression testing strategy encourages targeting your testing towards areas of the product that are more at risk of changing than others, instead of exhaustively testing every part of the product again and again.
Addressing those factors can give you a better approach to regression testing and help manage the workload.
Let’s break down some concepts around regression testing, and try to understand the why, the when, and the how of a regression testing approach.