Representation Options |
In certain domains and testing cultures, Test Ideas are either not recognized, or are considered informal
work products. As such, both the contents and format of Test-Ideas List may require modification to meet
the needs of each specific organization and project.
When they are recorded (either formally or informally), two main styles are commonly used:
-
The first is a standard text document structure using a format similar to that outlined above. Usually
multiple Test Ideas are to be presented together, whereas a single Test Idea by itself is usually not
considered to represent a sufficient list.
-
The second uses some form of table or database. Test Ideas are specified, one per row with columns
provided to facilitate sorting and filtering by different criteria. Test matrices or cause
and effect tables can be considered alternative forms of Test-Ideas List.
Some consideration should also be given to ongoing measurement of the Test Ideas for progress,
effectiveness, change management and so forth. Consider using specification-based test coverage, in which
each Test Idea or Test-Ideas List traces back to at least one specification entry to be tested. For
example, trace to the requirements specification elements to be tested which will typically reflect some
subset of the total product requirements (see Technique: Key Measures of Testing).
Optionally the Test-Ideas can be retained as part of a Test Case or Test Script. The list may also be referenced from-or in
smaller test efforts, included within-the Test Plan.
|