Test Data Modeling

The main reasons for not copying the entire production data set into the test environment are size and complexity. Smaller test datasets are less resource intensive and make transaction tracing easier. SuperVisor simplifies the task of modeling the test dataset in two stages:

1. SuperVisor can determine which files are needed to test a suite of programs.
2. SuperVisor can select records based upon filtering and referential relationships.

Determining Which Files are Required

A test dataset can be created without supplying a list of programs. In that case SuperVisor would assume that the entire dataset from the production library list would be involved in the test. However, if the purpose of the test dataset were to test only a single process or a narrow suite of programs SuperVisor can identify which files are required based upon a list of programs.

A list of programs can be entered or selected using a SuperVisor analysis command. SuperVisor automatically expands the list of programs to include those programs called by those on the list.

SuperVisor then performs an analysis to incorporate all of the files required by the programs to be tested. This includes all files required for referential integrity and related logical files.

Filtering and Dependent Records

To reduce the number of records required to populate a test dataset, SuperVisor provides two features, filtering and dependent copying. It is unnecessary to model the entire database. Small files such as account number and shipping terms files can be copied in their entirety. But for larger files, such as open orders or history files, filtering and dependent copying can be used. 

Filtering is done by applying some logic which records are copied, such as comparing dates, customer numbers or item numbers. For example the order header file might be filtered by customer number.

Order detail and history might copied using a dependent copy. The dependent copy would select only those detail records that matched those order numbers included in the order header file. Further an inventory transaction detail file might include only those items that were contained in the test order history file.

Introducing a Conversion Program

Should the system modification being tested require that certain files change in format, such as a field expansion, the test profile can specify the use of a user written conversion program.

Stored in Test Profile

These modeling techniques can be used each time the test dataset is repopulated. The specifications are stored in the Test Profile. So, they can be reused, modified and rerun.