What a regression suite should cover before every release
Sample authorPublished 6 min readSample
Sample article. This text shows the layout. The real article replaces it before launch.
Start from what users do
A regression suite earns its run time by covering the paths people take most:
- Signing in and out
- Finding things
- Paying
- Saving their work
Rank paths by risk
Weigh each path by how often it is used and how much a failure would cost, then cover the heaviest first.
Keep the suite fast
A suite nobody waits for is a suite nobody skips. Split slow end-to-end checks from quick ones and run the quick ones on every change.
Retire tests that stopped earning their place
Features change. Review the suite with each release and remove checks for behaviour the product no longer has. Need a hand with it? Talk to our QA team.
About the author
Sample authorSample
Author profile pending
A placeholder profile. The real author, with photo and bio, comes from the people collection.
