Article 2 of 5
Test Suite
A named group of cases you want to work with together.
A suite is how you find the twelve cases about payments among three hundred. Suites usually follow the product — Authentication, Payments, Profile — because that is how work is assigned and how failures are read.
Grouping by type (“all UI cases”) sounds tidy but ages badly: when checkout breaks, you want everything about checkout, not everything that happens to be a UI check.
What it is made of
- Name
- The feature or area: “Payments”.
- Description
- What belongs here, so the next person adds cases to the right suite.
- Members
- The test cases in the suite; a case belongs to one suite at a time.
Rules that save you later
- Keep suites the size of a feature, not the size of the product.
- If a suite never gets run as a whole, it is probably the wrong grouping.