In certain domains and testing cultures, Test Cases are considered optional work products, whereas in others they are
highly formalized and mandatory. As such, both the contents and format of Test Cases may require modification to meet
the needs of each specific organization or project.
When they are recorded (both formally and informally), two main styles are followed:
The first is a standard text document structure using a format similar to that previously outlined in the Brief
Outline. Often, multiple Test Case instances or variations are specified in a single document, grouped by the
general purpose or objective of the tests.
The second style uses some form of table or database. Test-Case instances are specified, one per row, with columns
provided to facilitate sorting and filtering by different criteria.
Some consideration should also be given to ongoing measurement of the test cases for progress, effectiveness, and so
forth. Consider requirements-based test coverage, in which each Test Case traces back to at least one test idea and at
least one system requirement, which represents a subset of the Product requirements (see Technique: Key Measures of Testing).
As mentioned, it is typical for multiple Test Case instances or variations to be specified in a single document,
usually grouped by the general purpose or objective of the tests. This may be realized as multiple execution conditions
described within the one document, one per unique Test Case instance.
Optionally the Test Case can be enclosed partially or completely within the Test-Ideas List or Test Script.