In [1, Marick], Brian Marick describes a "test catalog", which contains various common test idioms to be applied to recurrent cases. A "test catalog" entry might be something simple like: "for a String parameter, make sure to test what happens when passing an empty String." It might be something more complex like testing different "incorrect" IP addresses passed to a method that's expecting a String containing an IP address.
Marick's writing suggests that a tester will find and apply these test catalog entries to the test suite manually. That is, they will build test requirements by looking at the specification for a subsystem, then will consult the catalog to find testing idioms for "common" pieces of the specification. Finally, they will use these idioms to generate test requirements and test specifications, which they will merge with the requirements and specifications constructed specifically for this subsystem.