Creating a new Allocated Test
Search Knowledge Base by Keyword
Now you have set up an Allocation Pool, click on ‘New Allocated Test’ to set an Allocated Test up. The popup below will show, you will need to specify fields for the details, configuration, parameters and expected results sections.
Details
Test Name: Enter a Test Name, the Test Name must be unique within the Suite.
Suite Name: Choose from existing Suite Names or enter a New One. Test Names are unique within a Suite.
Test Criteria: Pick from the drop-down list.
Tags: You can enter Tag names here, use Tab to create as many as you like. The Tags can be used to filter your allocation pools later.
Below is an example of a new Allocated Test:
Configuration
Click the ‘Configuration’ tab, the following screen will show:
How Many: Enter how many allocated values you would like. This will default to whatever has been set in the definition of the test type.
Unique: Do you want the allocated value to be just for this test only? If it is not set other tests may use the same allocated value.
Prep environment: You can set up the data allocation to run jobs to prepare the data environment before the automation framework is run. Set this if this is a stand-alone piece of SQL to be run prior to the automation.
Below is an example of a new Allocated Test:
Parameters
Click the ‘Parameters’ tab, the following screen will show:
The parameter values will come over from the Parameters associated with the Test Type definition. You can fill these in with the required values to lookup the data you need for this specific test.
Below is an example of a new Allocated Test:
Expected Results
Click the ‘Expected Results’ tab, the following screen will show:
You can pass down values into the automation if you wish that can be used as the expected results.
You have now created an Allocated Test.
-
-
-
- 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
-
-