The SoftKeys sheet – Manually Defining “Soft” Keys in the Subsetted Data
Search Knowledge Base by Keyword
The Softkeys sheet is used to include “soft” Keys in the subsetted data. Soft Keys are Keys that are not implemented as hard coded constraints in the source database. They can be either Primary or Foreign Keys.
SoftKeys can be specified prior to running the Basic Subset. The definition of the Keys drives the formulation of the Subset Rules. Data Subsetting using Test Data Automation automatically formulates rules for creating a Subset that satisfies where the data satisfies the relationships defined by Primary and Foreign keys. The SUBSET action will then “Crawl” up and down the tables collecting data until it produces a data set that satisfies all the hard and soft relationships.
Note: Subset Rules are formulated to generate a set of data that fulfils the relationships in the Source Database. It therefore creates a data set where the data reflects the Primary and Foreign Key relationships. However, the core actions involved in running a Subset (GETMETADATA, PREPENV, BUILDMODEL, and SUBSET) do not implement these Keys in the Staging database. To implement them, you must perform Post-Subset actions to add Keys.
The Softkeys sheet contains the following columns:
- Active: Set to “Yes” or “No”, this will either include or exclude a relationship.
- FK_Schema: This should be left blank when defining Softkeys.
- FK_Table: This should be left blank when defining Softkeys.
- FK_Columns: This should be left blank when defining Softkeys.
- PK_Schema: The source primary key schema
- PK_Table: Primary key table name
- PK_Columns: The column names for the primary key. For composite keys the column names are delimited by a semi-colon.
- FK_Name: Foreign key name.
An empty Softkeys sheet therefore appears as follows:
To define a “soft” primary key for your Subset, simply leave the FK_Schema, FK_Table and FK_Columns cells empty. Next, specify the source primary key schema, the primary key table name, column names, and foreign key name:
You can define multiple Softkeys for a subset. To toggle between including them or not in your subsetted data, set the Active column to “Yes” or “No”.
-
-
-
- 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
-
-