Execution Templates

Overview

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.

Note: Available for test automation only.

Dependencies

• Testing Activities Package
• System Activitities v21.10.0 or higher

Conditions

• 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.

How it works

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.