Browse Prior Art Database

Test Data Generator

IP.com Disclosure Number: IPCOM000073654D
Original Publication Date: 1971-Jan-01
Included in the Prior Art Database: 2005-Feb-22
Document File: 3 page(s) / 35K

Publishing Venue

IBM

Related People

Ances, LJ: AUTHOR

Abstract

In a large system, one where many programmers are writing and testing numerous programs against the same files, a great deal of duplication of effort is expended in the construction of test files. Each programmer is required to build an accurate, and up-to-date set of records that will completely test his particular job. This duplication of effort is eliminated in a test data system using one major (master) copy of each file and as many modifications (slaves) to the master as necessary.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 3

Test Data Generator

In a large system, one where many programmers are writing and testing numerous programs against the same files, a great deal of duplication of effort is expended in the construction of test files. Each programmer is required to build an accurate, and up-to-date set of records that will completely test his particular job. This duplication of effort is eliminated in a test data system using one major (master) copy of each file and as many modifications (slaves) to the master as necessary.

The master file is constructed by either entering the data in the required format, or using standard decimal and character format and having the system convert to the proper format in accordance with the file description supplied by the Copy Library. Optionally the system can, where requested, pad fields with zeros, blanks, alphabetically sequenced characters for character fields, or numerically sequenced numbers for packed fields.

The slave file is constructed by the programmer when he requires different conditions then are available within the master file. The programmer enters his file name, the key name, and the labels of the particular fields, with the data, that he wishes to change. The key field is used to combine the slave and master records, and is therefore, required for each slave record.

At the start of a test, the programmer inputs his particular slave file names. During the test when a data management request is made, the following steps occur: 1) The test system acc...