Creating and Defining VIP Flows to Find and Make Data for use by Test Data Allocation
Search Knowledge Base by Keyword
See the documentation on using VIP to understand how to create and maintain flows. It is assumed you have some knowledge on how to create VIP flows.
VIP has many powerful connectors that provide direct connectivity to many products. Most products have an API layer and it is easy to add these APIs to VIP.
VIP can also call any existing scripts you have to find or make data. It is very common to have command line scripts written in Perl or PowerShell that perform useful data lookups or can make data to support testing.
There is an example in ‘c:\viptdm\dataallocation’ :
Open the flow and look at how the command script is invoked. This flow can be added into Modeller and called from the Test Data Allocation process.
In addition, VIP has a powerful set of Test Data Management utilities that can generate, mask, copy and clone data directly into databases, flat files or data queues.
For the flows to work inside the Modeller Data Allocation Framework the VIP flows must have two parameters defined:
- parRC, set it to -1 if there is a failure and 0 if it works correctly
- parReturn whatever you set it to will be returned into the Test Data Allocation as the result.
These parameters are defined in the example below:
Any input parameters you wish to override will be defined in Modeller, see Defining VIP Flows inside Test Modeller. Any output data you wish to return must be return in a list of strings.
Once you have defined your flow and moved it to the server it will be running on you need to define the process in Test Modeller.
You can do this manually or directly from inside VIP itself, this will be covered in the next section.
Example
Next, open the flow ‘VIPTestGetData.VIP’. This is an example flow you can add into your processes and can be called for Data Allocation.
Open the flow and click execute – you can see it returns a list of 10 rows. This data is being put into the Output parameter ParListOfData.
Set par1 to “1” and rerun, you will see it returns only 1 result. Reset par1 to “2” and check the results.
-
-
-
- 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
-
-