Post-Subset Actions

Further actions can be performed following a subset. Each is again informed by information in the Control spreadsheet and leverages an automated and pre-defined VIP Workflow. The  post-Subset Actions are:

1. ADDPKEYS: Adds Primary Key Constraints to the Subset in the Staging Database.
2. ADDFKEYS: Adds Foreign Key constraints.
3. VALIDATEPKEYS: Checks that all Primary Keys are unique.
4. VALIDATEFKEYS: Checks whether Foreign Keys can be added to the data.
5. DELETEORPHANS: Removes rows that do not fulfil Foreign Key constraints. This is useful if FoundCriteria have been specified.
6. Data edits: Various actions will edit the resultant data Subset:
   1. DROPFKEYS: Drops Foreign Keys.
   2. DROPPKEYS: Drops Primary Keys.
   3. TRUNCATE: Deletes the data from the target Database or Schema, allowing you to subset iteratively.
   4. DROP: Drops the tables created by the PREPENV Action.

Many of these Actions performed post-Subset create a functioning data set that can be used during testing and QA. For instance, adding Primary and Foreign Keys incorporates the relationships in the data needed for many types of automated testing.

Knowledge Base articles are provided on configuring each relevant sheet in the Basic/Advanced Control Spreadsheet, and running the Action associated with them. The below table summarises all Actions available when subsetting using Test Data Automation, and the sheets used to configure them. It also summarises which sheets the actions overwrite or populate in the Control Spreadsheet; if blank, it means that these actions are performed on the basis of the Source Data only:

The Knowledge Base articles on data subsetting will now explain how to configure and perform the Actions associated with a Basic Subset. It then sets out how to refine the Advanced Control Spreadsheet and perform iterative Subsets, before detailing the Actions that might be performed Post-Subset.