Template Types
Search Knowledge Base by Keyword
TestCaseTemplate
This is the master template for all code to be generated. Typically, one TestCaseTemplate is embedded per test model.
Keyword | Description |
---|---|
{{{ModelURL}}} | URL of the model |
{{{TestCaseName}} | Name of the test case |
{{{test-suite-id}}} | ID of the associated test suite being exported |
//Region – Testcases | Region to embed test case definitions code template – See TestCaseMethodTemplate. |
//EndRegion – Testcases | Terminal location to stop embedding test case definitions |
Below is an example:
TestCaseMethodTemplate
This is the test case template used for each instance of a test case (i.e. path) within the model. This is embedded when the ‘//Region – Testcases’ and ‘//EndRegion – Testcases’ keywords are embedded within a code template.
Keyword | Description |
---|---|
{{{groups}}} | Tags defined in the model |
{{{test-guid}} | Guid of the test case in test modeller |
{{{allocateTag}}} | Allocate tag. If any allocations are defined for the test case this will be replaced with the ‘AllocateTagTemplate’ |
{{{TestName}}} | Name of the test case. This is the name of the path. |
//Region – Allocate | Region to embed any ‘AllocationDataRowTemplate’ tags to initialise any allocations performed within the test case. |
//EndRegion – Allocate | End region for allocate tags |
//Region – Test Logic | Region to embed the test logic for the test case. |
//EndRegion – Test Logic | End region for test logic |
Below is an example:
AllocateTagTemplate
The tag to use for functions which have Data Allocation defined within the test case. This is embedded whenever the code template engine comes across a tag with {{{AllocateTag}}} embedded within it.
Keyword | Description |
---|---|
{{{AllocatePoolName}}} | Allocation pool name being used. |
{{{AllocateSuiteName}}} | Suite name performed. |
{{{AllocateGroupName}}} | Group of test names of the allocation to be consumed. |
Below is an example:
AllocateDataRowTemplate
This is called to initialise a new allocate data row object whenever a test case needs to access a previously unseen test allocation method this tag is embedded.
Keyword | Description |
---|---|
{{{AllocateResultName}}} | Auto-generated variable name for the allocations. |
{{{TestPoolName}}} | Name of the allocation pool that is being referenced |
{{{TestSuiteName}}} | Name of the test suite |
{{{AllocateName}}} | Name of the allocation test case |
Below is an example:
AllocateRetrieveDataValueTemplate
This is the code used to retrieve an allocated value from a test allocation object. This is only embedded in functions where the allocation is referenced.
Keyword | Description |
---|---|
{{{AllocateVariableName}}} | Auto-generated value which refers to the corresponding allocation initialised within the ‘AllocateDataRowTemplate’ |
{{{AllocateColumnIndex}}} | Index of the value required from the allocation object for the referenced parameter. |
Below is an example:
-
-
-
- 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
-
-