Post-Subset Actions
Search Knowledge Base by Keyword
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:
- ADDPKEYS: Adds Primary Key Constraints to the Subset in the Staging Database.
- ADDFKEYS: Adds Foreign Key constraints.
- ADDKEYS: A composite action that performs both ADDPKEYS and ADDFKEYS, adding both Primary and Foreign Key Constraints to the Staging Database.
- VALIDATEPKEYS: Checks that all Primary Keys are unique.
- VALIDATEFKEYS: Checks whether Foreign Keys can be added to the data.
- VALIDATEKEYS: A composite action that runs both VALIDATEPKEYS and VALIDATEFKEYS.
- DELETEORPHANS: Removes rows that do not fulfil Foreign Key constraints. This is useful if FoundCriteria have been specified.
- Data edits: Various actions will edit the resultant data Subset:
- DROPFKEYS: Drops Foreign Keys.
- DROPPKEYS: Drops Primary Keys.
- DROPKEYS: A composite action that runs DROPFKEYS and DROPPKEYS, dropping both Foreign and Primary Key Constraints.
- TRUNCATE: Deletes the data from the target Database or Schema, allowing you to subset iteratively.
- 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:
Action | Definition | Informed by data in the following sheets | Populates/overwrites data in |
---|---|---|---|
GETMETADATA | Retrieves the metadata from the Source Data that is needed to run the Subset A composite action, it runs the TABLES, GETKEYS and FINDIDENTITYCOLUMNS actions. | ||
TABLES | Retrieves metadata from the source database. | Tables | Tables |
GETKEYS | Retrieves metadata from the source database. | ForeignKeys | |
FINDIDENTITYCOLUMNS | Finds identity columns in the source database | Tables | |
PREPENV | Creates tables and indexes in the Staging Database. | ||
BUILDMODEL | Creates the rules to drive the Subset. | SQLCriteria Tables ForeignKeys SoftKeys HashCodes | ProcessModel RuleList |
SUBSET | Writes data to the staging database. | FoundCriteria HashCodes | SubsetResults |
ADDPKEYS | Adds Primary Key Constraints to the Data Subset. | Tables ForeignKeys | |
ADDFKEYS | Adds Foreign Key constraints. | Tables ForeignKeys | |
ADDKEYS | Runs ADDPKEYS followed by ADDPKEYS. | Tables ForeignKeys | |
VALIDATEPKEYS | Checks that all Primary Keys are unique. | Tables ForeignKeys | |
VALIDATEFKEYS | Checks whether Foreign Keys can be added to the data. | Tables ForeignKeys | |
VALIDATEKEYS | Runs VALIDATEPKEYS followed by VALIDATEFKEYS. | Tables ForeignKeys | |
DROPFKEYS | Deletes Foreign Keys from the Data Subset. | Tables ForeignKeys | |
DROPPKEYS | Deletes Primary Keys from the Data Subset. | Tables ForeignKeys | |
DROPKEYS | Runs DROPFKEYS followed by DROPPKEYS. | Tables ForeignKeys | |
TRUNCATE | Deletes the data from the target Database or Schema, allowing you to subset iteratively. | ||
DROP | Drops the tables created by the PREPENV action . |
The Knowledge Base articles on data subsetting will 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.
The Data Subsetting of the Knowledge Base does not provide instructions on exposing a Subset to a shared server or self-service test data web portal. This process is generic to all Test Data Automation utilities.
-
-
-
- IEnumerable to Data Reader
- Data Table to List
- Nested String List to Data Table
- List to Data Table
- IEnumerable to List
- List to IEnumerable
- Remove from List
- Exists in List
- Value Exists in Dictionary
- Key Exists in Dictionary
- Remove from Dictionary
- Get from Dictionary
- Clear Dictionary
- Add to Dictionary
- Clear List
- Add to List
- Show all articles ( 1 ) Collapse Articles
-
-
-
-
- Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
- The ForeignKeys Sheet - Specifying which Foreign Keys to read from the Source Database
- The Tables Sheet: Defining Metadata that will be read from the Source Database
- The ProcessModel sheet – Toggling Subset Rules
- Refining the Control Spreadsheet
- Overview of the Advanced Control Spreadsheet
- Introduction
-
- Drop both Primary and Foreign Keys (The composite DROPKEYS Action)
- Validate Both Primary and Foreign Keys (The composite ValidateKeys Action)
- Add Both Primary and Foreign Keys (The Composite ADDKEYS action)
- Drop Tables
- Truncate Data
- Delete Orphans
- Drop Primary Keys
- Drop Foreign Keys
- Validate that Foreign Keys are Unique
- Validate that Primary Keys are Unique
- Add Foreign Keys
- Add Primary Keys
- Overview of Post-Subset Actions
-
-
- Use Event Hooks to call VIP Flows
- Different Methods for Connecting to Source Databases
- PreProcess Variables and Parameters
- Using SQL Functions to query Databases and Using the Queries in Data Generation Functions
- Summary of the Process to Configure the Test Data Configuration sheet
- How the PreProcessVariables Table is used in the Configuration sheet
- Sample Commerce Configuration Sheet Examples
- Adding Event Hooks in Configuration sheet for custom functionality
- How to Configure the Synthetic Test Data Configuration Control Sheet
-
-
-
-
-
- The UI Recorder
- Test Modeller – Maintenance
- Test Modeller Core (Linux) Optional – Postgres LDAP
- Test Modeller Core (Linux) Optional – SSL Certificate Installation
- Test Modeller Core (Linux) Optional – Active Directory
- Test Modeller Core (Linux) Installation
- Test Modeller: Software Pre-requisites
- Test Modeller : Installation components
- Test Modeller : System requirements (Windows, Linux)
-
-
-
-
-
-
- Common Problems
- Extend Test Modeller (Advanced)
- Edit Code Templates (Advanced)
- Import existing framework / custom page objects (Advanced)
- Execute Tests (Java)
- Generate Automation Code
- Build a Model (Java)
- Scan an Existing Web App
- Configuration (Java)
- Prerequisites (Selenium Java)
- Welcome Selenium (Java)
-
-
-
-
- Generate Optimised Test Cases and Data into Excel
- Implement Naming Conventions
- Page Object Generation
- Intelligent Page Objects
- Customising Page Objects
- Import Custom Code Snippets
- Rule-Based Test Generation
- Trigger Automation Execution from within Test Modeller
- Automation Configuration
- Test Data Automation for Gherkin Specifications
-
-