runTricentisToscaTests
- Karl Henselin
- Avnish Patel
Executes Tricentis Tosca automation tests and returns the results to FlexDeploy. This operation supports both Remote Execution (CLI) and Distributed Execution (DEX). By default, execution happens through Remote Execution; however, using (FDTT_INP_TOSCA_DISTRIBUTED_EXECUTION )this input allows you to switch to Tosca Distributed Execution.
Tosca Distributed Execution
Tosca Distributed Execution, you can distribute your tests across all available computing resources, such as computers in your network, virtual machines, or the cloud. This speeds up large test runs and leaves user machines unblocked. Tosca Distributed Execution is only available for multi-user environments.
To use Tosca Execution Clients, you need a Tosca Server 15.2 LTS or higher. It will be available in two versions: for Windows systems and Linux systems.
Test Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Tosca CI Java client path |
| Yes | The path up to the folder containing the ToscaCIJavaClient jar (e.g. C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander\ToscaCI\Client) |
Tosca Server URL |
| Yes | Tosca server Name (e.g. http://[HOST]:[Port]/TOSCARemoteExecutionService). Find this as endpointAddress in ToscaCIRemoteExecutionService.exe.config file, located at %COMMANDER_HOME%\ToscaCI |
 Tosca Username |
| Yes | Tosca Username Find this as AuthenticationUsername in ToscaCIRemoteExecutionService.exe.config file, located at %COMMANDER_HOME%\ToscaCI Â |
Tosca Password |
| Yes | Tosca Password Find this as AuthenticationPassword in ToscaCIRemoteExecutionService.exe.config file, located at %COMMANDER_HOME%\ToscaCI |
Tosca Client Id |
| No | Client ID of the Tricentis User Administration access token. This parameter is mandatory if you use HTTPS. (Note : for Distributed Execution) |
Tosca Client Secret |
| No | Client secret of the Tricentis User Administration access token. This parameter is mandatory if you use HTTPS. (Note : for Distributed Execution) |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Tosca Distributed Execution |
| No | Flag to indicate if it is a Tosca Distributed Execution. |
Tosca Server URL |
| No | Tosca Server URL to connect. If not provided, value from the Test Instance will be used. |
Tosca Username |
| No | Tosca Username. If not provided, value from the Test Instance will be used. |
Tosca Password |
| No | Tosca Password. If not provided, value from the Test Instance will be used. |
Test Config file path |
| No | Test Config file path (e.g., C:\Tosca_Projec\Tosca_CommonRepositories\TestConfig.xml). If relative, it is assumed to be in the FD_ARTIFACTS_DIR. |
Project Name |
| No | Project root name of the Tosca project where the event is located (mandatory for Distributed Execution). |
Test Event Names |
| No | Provide unique names of the events that you want to execute separated by ## (for Distributed Execution ex : testEvent1##testEvent2 ). |
Test Events Config File Path |
| No | Absolute or relative Test event config file path. Relative path will be assumed in FD_ARTIFACT_DIR (for Distributed Execution). Note( either
|
Result File Path |
| No | Absolute or relative Result folder path. Relative path will be assumed in FD_TEMP_DIR (for Distributed Execution).</Description> |
Provide Latest Script File |
| No | Absolute or relative DEX script file path. Relative path will be assumed in FD_ARTIFACT_DIR (for Distributed Execution). |
|
| No | Additional Arguments (for Distributed Execution) |
Use PowerShell 6+ |
| No | The script is intended for use with Tosca Distributed Execution. Check If you want to execute the script on PowerShell 6+. If it is unchecked then it will execute on PowerShell 1-5. |
Artifacts
This operation consumes the test config file from artifact repository.
Endpoint Selection
This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the Target. Selecting a specific resource will result in selection of endpoints associated to the Target which have that resource defined.Â
Endpoint Execution
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.Â
- style