Settings - DistributedExecution

You can find the following settings under Settings->Commander->DistributedExecution:

Check for Legacy Steps
Description	This setting allows you to control whether Tricentis Tosca should check for TestSteps that you created with Classic Engines. By default, this setting is disabled. If you enable it, Tricentis Tosca checks if there are Classic TestSteps in your TestEvents. This increases your start-up time. If you work with Execution Agents and your TestEvents contain Classic TestSteps, you must enable this setting. Otherwise, TestEvents with Classic TestSteps may be executed on Execution Agents which do not support Classic TestSteps. In this case, the Distributed Execution Monitor shows the status ERROR for the Classic TestStep and the Agent log contains the information “No log was created for this TestCase”.

Check for Legacy Steps

Description

This setting allows you to control whether Tricentis Tosca should check for TestSteps that you created with Classic Engines.

By default, this setting is disabled. If you enable it, Tricentis Tosca checks if there are Classic TestSteps in your TestEvents. This increases your start-up time.

If you work with Execution Agents and your TestEvents contain Classic TestSteps, you must enable this setting. Otherwise, TestEvents with Classic TestSteps may be executed on Execution Agents which do not support Classic TestSteps. In this case, the Distributed Execution Monitor shows the status ERROR for the Classic TestStep and the Agent log contains the information “No log was created for this TestCase”.

Monitor Url

The following setting is located at Settings->Commander->DistributedExecution->Monitor Url.

Url
Description	Enter the complete network address of the Tosca Distributed Execution Monitor.
Example	http://localhost:<port>/Monitor/

Server

The following settings are located at Settings->Commander->DistributedExecution->Server.

EndpointAddress
Description	Enter the complete network address of the Tosca Distribution Server: http://server_address:port/DistributionServerService/ManagerService.svc
Example	http://localhost:85/DistributionServerService/ManagerService.svc

EndpointAddress

Description

Enter the complete network address of the Tosca Distribution Server:

http://server_address:port/DistributionServerService/ManagerService.svc

Example

http://localhost:85/DistributionServerService/ManagerService.svc

Proxy
Description	Enter the complete network address of your proxy server, if you want to use one. http://address:port
Example	http://localhost:1234

Proxy

Description

Enter the complete network address of your proxy server, if you want to use one.

http://address:port

Example

http://localhost:1234

Cloud

The following settings are located at Settings->Commander->DistributedExecution->Cloud.

You only need these settings if you integrate Tricentis Tosca with Elastic Execution Grid via Addin.

Elastic Execution Grid is an early access feature and available as a tech preview.

Click here if you'd like to participate in the tech preview.

Client Id
This field contains the Client ID of your cloud authorization. It's prefilled; you don't need to change the value.

Elastic Execution Grid URL
Description	Enter https://<network address of your cloud instance>/<space name>. Replace <space name> with one of the following: If you created a Space for your cloud instance, enter the name of the Space. If you didn't create a Space, enter default.
Example	https://examplecompany.my.tricentis.com/default

Elastic Execution Grid URL

Description

Enter https://<network address of your cloud instance>/<space name>.

Replace <space name> with one of the following:

If you created a Space for your cloud instance, enter the name of the Space.
If you didn't create a Space, enter default.

Example

https://examplecompany.my.tricentis.com/default

Port
This field contains the listening TCP port for cloud authorization. It's prefilled; you don't need to change the value. Note: this port must be available on the machine. If it isn't, you need to configure a different port in Okta, which handles cloud authorization. If you do configure a different port in Okta, update this setting with the new port.

Port

This field contains the listening TCP port for cloud authorization. It's prefilled; you don't need to change the value.

Note: this port must be available on the machine. If it isn't, you need to configure a different port in Okta, which handles cloud authorization. If you do configure a different port in Okta, update this setting with the new port.