Data Sets Task Flow
Perform the following steps in a data subset, data masking, or data generation plan, to create a data set in the test data mart:
- 1. Open a project and create a plan with the required components.
- 2. Configure the plan properties in the Plan Settings window.
- 3. From the list of target connection types, select Test Data Mart. TDM enters the test data mart that you have configured.
- 4. Enter the Data Set Properties. TDM creates the data set version number.
- 5. Configure the error and recovery strategies and advanced settings.
- 6. Generate and run a workflow.
- 7. Monitor the workflow.
To create another version of the data set, run the plan again. For example, you create the first version of a data set with the original test data. After you run the first set of test cases, the test data changes. To store the updated test data in the test data mart, run the same plan again and create another version of the data set.
You can also enter the same data set name in a different plan to create another version of the data set. For example, to test different features of a single application, you might require different test data. Run a different plan with a different data source. Because the test data is for a single application, you enter the same data set name. You create another version of the data set from a different plan and with different data.
Data Set Creation Guidelines
Create a data set to store versions of test data in the test data mart.
Read the following guidelines before you create a data set or another version of a data set.
- •You cannot create a data set if the tables contain columns with user-defined data types. If a table contains columns with user-defined data types, mark the columns as restricted before you include the tables in a plan to create a data set. To mark a column as restricted, open the project and click Discover > Columns and select the option Restricted for the required column.
- •Verify whether the tables in the data source contain primary keys. Create logical keys in all transactional tables that do not have any primary keys. A reset operation might fail if a transactional table with null values does not have primary keys.
- •If a table contains more than two character columns with a precision of 4000 each, edit the precision to 3,999 or less. A reset operation might fail if a data set contains more than two character columns with a precision of 4,000 each and you do not disable constraints during the reset operation.