Regression suite
The set of test cases run to confirm that existing behaviour still works after a change. It grows by default and shrinks only on purpose, which is why mature teams review it on a schedule and retire cases that no longer earn their execution time. A regression suite nobody prunes eventually becomes too slow to run when it matters.
Also called: regression pack
Regression suite versus smoke suite
Both get run after a change, and teams mix them up because the same login case often sits in both. The difference is the question each answers. A smoke run asks whether the build is worth testing at all and has to finish in minutes. A regression run asks whether anything that used to work has stopped working, and it is allowed to be slow because its job is breadth. Treat them as two selections from one library, usually made with tags, rather than two copies of the same cases.
It grows unless someone shrinks it
Every escaped defect adds a case, and nothing removes one. A suite nobody prunes ends up with cases for features that no longer exist, near-duplicates written by different people, and checks that have passed for two years without telling anyone anything. Review it on a schedule: retire cases for removed features, merge duplicates, and ask of each slow case whether a cheaper test catches the same failure.
Automate the stable middle
The parts of a regression suite that change rarely and run every release are the best candidates for automation. Cases that depend on visual judgment or change every sprint usually cost more to automate than to run by hand. When automated, the suite brings its own noise: flaky tests need a quarantine rule, or the team stops trusting red runs.
In QAM Hub
A regression selection is usually a tag across suites, turned into a run with the tag filter. For automated regression, the Tests tab (Standard and Advanced plans) tracks each test across the last 5 to 100 runs and marks it failing, flaky, stable or quarantined. Setup is in creating test suites and test cases and automation coverage reporting.