- 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
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
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.
- You can make use of reusable content by creating a library with execution templates.
- You can invoke multiple placeholders in the workflow.
To run a test case inside an execution template at runtime:
- Create execution template.
- Add test case to execution template.
Create an execution template before setting it to a test cases.
- Open your workflow in Studio.
- In the Project panel, right-click the Templates folder to open the dropdown menu.
- Navigate to Add > Execution Template.
-
Enter a name for your execution template. The location of the template is the Templates folder of the project.
- Select a template on which you want to create the execution
template. You can choose between the Default Execution
Template or other execution templates stored
inside the Templates folder of your current
project.
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 or create 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.
- Select Invoke the templated workflow as isolated, if you want to run the invoked execution template as isolated. See the Isolate topic below for more information.
- 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.
When you set an execution template for a Test Case, you have the option to invoke the execution template workflow as isolated. This executes the invoked template in a separate process. This option can involve several restrictions that are described in the Invoke Workflow File activity page. Some of the restrictions are:
- Passing In arguments to an Invoke Workflow File activity that is not isolated acts as if a reference is passed, which means any changes to the object inside the invoked workflow change the object in the main workflow.
- Variables and arguments are not supported for workflow file names in Windows and cross-platform projects. This will trigger an Expressions are currently not supported error notification.
- When invoking a workflow, make sure it does not contain persistence activities. These should only be used in the main workflow.Now you can run or debug the test case as it will be executed with the execution template.
- Add test data to your test case
- Publish test case to Orchestrator
- Set application testing Workflow Analyzer rule (see Incorrect Amount of Placeholders in Execution Template)
- Open your workflow in Studio.
-
In the Project panel, right-click a test case to open the dropdown menu.
Hover the mouse over a test case to show whether it is added to an execution template.
- Click Set Execution Template and select <no execution template> from the dropdown list.
- Click Ok to confirm.
