Defining Test Data

Defining test data is the first step in the provisioning of test data in which you expose data and data sources to . Defining test data refers to the high-level process that includes:
tdm44
Defining test data is the first step in the provisioning of test data in which you expose data and data sources to
Test Data Management
. Defining test data refers to the high-level process that includes:
  • Connecting to relational data sources
  • Creating projects to contain data
  • Registering data from relational and non-relational data sources
  • Converting non-relational data to relational tables
  • Analyzing and editing imported data to prepare for other operations
Test Data Management
 supports a wide variety of data sources that you can register, including databases, flat files, mainframe databases, and more. Depending on the data type, you discover the data in one of the following ways:
  • Using the CA TDM Portal
  • Using Datamaker
  • Using format-specific utilities for formats that do not support direct registration by Datamaker or the CA TDM Portal
The following list provides a summary of the different data types you can work with and from where you should start the discovery process for each data type.
Non-Relational Data Sources (Flat Files)
Non-relational data sources, or flat files, are data sources that do not maintain data in relational tables. Common flat file types include, XSD, XML, and CSV. After you register flat files, CA TDM puts the data in a relational table format so that it can perform other operations on the data.
Work with flat files using the CA TDM Portal. 
Relational Tables
Register relational database tables to integrate the database data with CA TDM. You can then generate more data, create a subset, and more. A wide range of databases are supported, including common distributed databases, mainframe databases, and big data sources.
Work with relational tables using the CA TDM Portal or Datamaker. 
EDI Files
EDI files are a record-based file format that covers a large number of record types. There are several different EDI formats, as well. A format-specific utility is required to import the EDI files into a specialized XML file, and then import that file into 
Test Data Management
.
To work with EDI files, use the GT EDI utility.
Record-Based Mainframe Files
Several mainframe data sources are indexed, record-based files, such as ISAM and VSAM. The structure of these files is typically described in a COBOL Copybook. A format-specific utility is required to read the copybook data and parse it into a format that CA TDM can understand. You can parse Copybook data into a GT Excel file format, which you can then register in the CA TDM Portal and Datamaker.
After you register data, the following functionality is available to edit the registered data:
  • Datamaker and the CA TDM Portal provide the ability to edit table relationships based on the derived tables created during the registration process
  • Datamaker includes a utility called GTDiagrammer, which provides a visual representation of your table structure and lets you edit the data in place
When the discovery process is complete, you can progress to common data provisioning operations, such as:
  • Profiling the data and creating transformation maps for masking
  • Creating data generation rules and generate synthetic data
  • Assembling a test data warehouse of registered data that you can use to make the data available for testers