Actions used in subsetting
Search Knowledge Base by Keyword
The Subsetting is performed using automated VIP workflows. Each high-speed workflow performs “Actions”. The actions and workflows are executed using the VIP Server Controller. Each Action is informed either by sheets in the Basic/Advanced Control Spreadsheet, or by information read from the Source Database. Some of this information can be user defined; other information is generated by the Subset actions.
The actions to run the Basic Subset are:
- The GETMETADATA Action retrieves the metadata from the Source Data that is needed to run the Subset. It is a composite action, made up of three actions. Each action be run in a single action as “GETMETADATA”, or can be run separately. GETMETADATA is recommended for simplicity and speed. Running the actions individually is valuable for closer analysis, learning, and debugging.
- The TABLES Action retrieve metadata related to the tables in the Source Database.
- The GETKEYS Action retrieve metadata from the Source Database.
- The FINDIDENTITYCOLUMNS Action retrieves the Identity Columns for each specified table.
- The PREPENV Action create tables and indexes in the Staging Database.
- The BUILDMODEL creates the rules to drive the Subset.
- The SUBSET Action writes data to the Staging Database.
A Subset will run until one of the following completion criteria is fulfilled:
- A maximum specified number of rows is reached;
- A maximum number of recursions is reached;
- The “Found Criteria” are fulfilled;
- There are no more rows in the Source Database that match the Subset criteria. The Subset will stop recurring when no rows were added in the last recursion.
This Basic Subset will generate the Advanced Control Spreadsheet, containing additional sheets. These sheets contain additional parameters and the automatically formulated Subset rules. The information in these sheets can then be used to perform Advanced Subsets. You can subset iteratively by toggling the Subset Rules, Tables and Relationships that will be used in the next Subset.
Actions used to perform iterative Subsets after the Basic Subset include:
- DROP: Drops the tables registered by the TABLES action. You will only run this if something has gone wrong in a Subset, and you want to create a wholly new Data Subset.
- PREPENV: If you drop the tables, you will need to re-register tables before performing the next Subset.
- TRUNCATE: Deletes data from the Target Database or Schema.
- BUILDMODEL: Creates the rules to drive the Advanced Subset, based on the Control Spreadsheet.
- SUBSET: Writes the new Data Subset to the Staging Database, based on the updated Control Spreadsheet.
-
-
-
- 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
-
-