Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
Search Knowledge Base by Keyword
Several sheets in the Advanced Control Sheet should never be edited. However, they can be useful for reference when defining iterative subsets. Their contents are explained below.
The RuleList sheet
The RuleList sheet is created when the BUILDMODEL action is run. sheet contains the rules to drive subsetting.
The RuleList sheet should not be edited, but is useful for reference when editing the ProcessModel sheet.
Each Rule is reflected in a row. The columns contained for each rule are:
- Direction: “DOWN” or “UP” gives the direction of the relationship between Table and RefTable.
- Schema: The Source Schema name.
- Table: The Source Table name.
- Columns: The Key Column names in the Table.
- RefSchema: The Source Schema name.
- RefTable: The Source Table name.
- RefColumns: The Key Column names in the RefTable
- FK_Name: Foreign key name
An example RuleList sheet appears as follows:
SubsetResults
This sheet displays the results of the Subset. It is generated by the SUBSET action.
Each row represents a Table and Schema name. The SubsetResults sheet displays the total number of rows in the Staging Table, and the number added by the last SUBSET action.
The columns in the sheet are:
- SchemaName: The Staging Schema name.
- TableName: The Staging Table name.
- RowsInStaging: The total number of rows in the table during staging.
- RowsAdded: The number of rows added by the last SUBSET action.
An example SubsetResults sheet appears as follows:
HashCodes
The HashCodes sheets is used by VIP to ensure that the SUBSET action is only run if the control spreadsheet contains an up-to-date ProcessModel sheet.
The sheet holds hashcodes for the SQLCriteria, Tables, ForeignKeys and SoftKeys sheets. If any of these has changed since the last BUILDMODEL action was run, the ProcessModel sheet might then be out of date.
The BUILDMODEL and SUBSET actions use the codes in this sheet to check for any changes to these tables. If the SUBSET action detects that any of the SQLCriteria, Tables, ForeignKeys or SoftKeys have changed in any way since the last BUILDMODEL action, then a warning will be given in the log. The SUBSET action will not then run unless parOverrideBuildmodelRequirement has been set to True.
An example HashCodes sheet appears as follows:
-
-
-
- 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
-
-