- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
Execution Templates
Through execution templates you can wrap test cases at runtime to use your defined execution conditions for multiple scenarios. For example, instead of copying, pasting, and maintaining multiple test cases, you can create a single template that acts as a boilerplate to wrap the test cases at runtime.
- When you run or debug the file, the test case and its associated execution template are merged into a temporary file. The collection of arguments and variables from both files are compared by name at runtime. If the execution template shares a matching argument or variable name with the test case, it will be linked in the Invoked Workflow File after the merge. If the test case does not have any matching arguments with the execution template, the arguments from the former file will be copied to the latter.
- Moving or renaming an execution template automatically updates its associated test cases.
- When publishing a project with execution templates, any publishable test cases are merged with the execution templates. The resulting files are the project entry points.
The execution template acts as a wrapper for test cases. In the Designer panel, you can see a Placeholder activity within the execution template.
This activity is going to be replaced at runtime with an Invoke activtity, adding the invoked test case to the execution template, as you can see in the following image.
To run a test case inside an execution template at runtime, you need to follow these procedures:
Create an execution template before setting it to a test cases.
- Open your workflow in Studio.
- In the Projects panel, right-click the File Templates folder to open the dropdown menu.
- Navigate to Add > Execution Template.
-
Enter a Name for your execution template and choose the Location where it is going to be stored.
A new tab opens in the Designer panel with your execution template. You can build the template to match your testing needs.
- Click Save when your execution template is done.
To run or debug a test case with an execution template, you need to add it to an execution template (Set Execution Template). Alternatively, you can set an execution template for a newly created test case.
- Open your test case in Studio. If you do not have one yet, you can create a test case.
- In the Projects panel, right-click a test case to open the dropdown menu.
- Click Set Execution Template and select a template from the dropdown list.
-
Click Ok to confirm. The execution template is added to the test case. Running or debugging this test case will proceed according to your associated execution template.
Now you can run or debug the test case as it will be executed with the execution template.
- Open your workflow in Studio.
-
In the Projects panel, right-click a test case to open the dropdown menu.
Note: Hover the mouse over a test case to show whether it is added to an execution template or not. - Click Set Execution Template and select <no execution template> from the dropdown list.
- Click Ok to confirm.