Artifact:
|
The definition (usually formal) of a collection of test input values that are consumed during the execution of a test, and expected results referenced for comparative purposes during the execution of a test. | |
Role: | Test Analyst |
Optionality/Occurrence: | Test Data should be maintained for at least some portion of the tests, ideally in a central data store. |
Templates and Reports: |
|
Examples: | |
UML Representation: | Not applicable. |
More Information: |
Input to Activities: | Output from Activities: |
Test Data provide both a layer of indirection and a central point of modification for the unique characteristics of a test. When managed separately from the procedural aspects of the test, this enables the unique characteristics of the test to be modified independently.
Each Test-Data set should consider various aspects including the following:
There are no UML representations for this artifact or its properties.
Property Name |
Brief Description |
---|---|
Data-Set Name | A unique name used to identify this Test-Data set as a whole. |
Name | A unique name or identifier for each individual data record, entry, or combination thereof. |
Description | A short description of the contents of the Test-Data record, typically giving some indication of scope. |
Purpose | An explanation of what this Test-Data record represents and why it is important. |
Dependent Test and Evaluation Items | Some form of traceability or dependency mapping to specific elements, such as individual Requirements, Test Cases or Test Scripts that need to be referenced. |
You can normally begin gathering candidate Test Data as early as Inception phase. At this early stage, it can be useful to store the gathered data in a unrestricted format that enforces minimal rules. This allows ill-formed Test Data records to be partially captured. As the lifecycle progresses-especially as more test staff become involved-it is usually necessary to lock-down the restrictions thereby enforcing the integrity of the Test Data. By the end of the Elaboration phase, a broad selection of Test-Data types should exist, with a handful of representative data-record entries. A larger number of data records for specific focus areas should also be available; for example, the few key use cases, usage scenarios, system functions, transactions, and so on.
The Test Analyst role is primarily responsible for this artifact. The responsibilities are split into two main areas of concern:
The primary set of responsibilities covers the following identification and elicitation issues:
The secondary set of responsibilities covers the following implementation and management issues:
Both the contents 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:
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 artifacts.
Rational Unified Process |