|
Method |
Pros |
Cons |
|
Manual
creation: Testers physically enter data on an individual or case-by-case
level |
Testers
can create the data to meet specific models they need for testing. |
Data may
not reflect real world data. Data may
not be voluminous enough for performance testing. Data may
not have aged enough for certain test cases where time passage is a key
element. Process
is time consuming. |
|
Use of
Automated tools to generate data |
Saves
time |
Data may
not reflect real world data. Tools may
not be available |
|
Conversion
of live production data to the test application database. |
Data
reflects real world conditions. Allows
test of conversion processes. Provides
new and aged data. |
Conversion
may not be possible due to security issues. If new
application has new fields, the data may not be complete enough to test all
facets of application. It may be
impossible to isolate cases for conversion since individuals are related to multiple cases. It may
not be cost effective due to the effort needed to purify the data prior to
the start of testing. |
|
Conversion
of test data from other test regions |
Security
is not an issue. Allows
test of conversion processes. Provides
new and aged data |
If new
application has new fields, the data may not be complete enough to test all
facets of application. It may
not be cost effective due to the effort needed to purify the data prior to
the start of testing. |
|
OTHERS |
||