This work product represents a container for organizing arbitrary collections of related tests. This may be realized
(implemented) as one or more automated regression Test Suites, but the Test Suite can also be a work plan for the
implementation of a group of related manual tests. Note also that Test Suites can be nested hierarchically, therefore
one Test Suite may be enclosed within another.
Sometimes these groups of tests will relate directly to a subsystem or other system design element, but other times
they'll relate directly to things such as quality dimensions, core "mission critical" functions, requirements
compliance, standards adherence, and many others concerns that cut across, or are not directly related to, the internal
You should consider creating Test Suites that arrange the available Test Scripts-in addition to other Test Suites-in
many different combinations: the more variations you have, the more you'll increase coverage and the potential for finding
errors. Give thought to a variety of Test Suites that will cover the breadth and depth of the target test items. Remember
the corresponding implication that a single Test Script (or Test Suite) may appear in many different Test Suites.
Some test automation tools provide the ability to automatically generate or assemble Test Suites. There are also
implementation techniques that enable automated Test Suites to dynamically select all or part of their component Test
Scripts for each test cycle run.