Reasons for not needing |
Key artifact for most projects. There are differences mostly in the formality level: in some cases, this artifact
is informal and transitory, and the test team is judged based on other criteria. In other cases -- especially with
automated tests -- the test scripts and associated test data (or some subset thereof) are regarded as major
deliverables of the test effort.
|
Representation Options |
Both the content and format of Test Data may require modification to meet the needs of each specific organization and
project.
When Test Data are managed independently of procedural test concerns, there are a few different styles of storage used:
-
A simple form of ASCII text file, either special character delimited or fixed-width columns
-
A basic form of spreadsheet or database system, such as Microsoft® Excel or Microsoft® Access
-
Some form of program-generated calculation of the Test Data
-
Some form of capture, extraction, or conversion of the Test Data from an original source
-
A complex relational (RDBMS) or object (ODBMS) database management system. Many test teams make use of the same
database to manage Test Data as that used by the software being developed. This often proves advantageous in having
ready access to skilled database administrators and designers who can provide advice and support to the test team.
As mentioned, it is typical for multiple Test Data elements to be specified in a single storage container, usually
grouped by the general purpose or objective of the tests.
In some cases, the Test Data can be enclosed within the Test Script or the Test Suite work products.
|