Run tests with Tosca in the cloud

The integration with Tosca in the cloud is in the open beta phase and available as an early access feature. We don't guarantee full functionality or usability in the current or future Tosca versions.

Once an admin has enabled the integration, Tosca users can run their Tosca tests in Tosca in the cloud.

What you can run in Tosca in the cloud

Tosca in the cloud supports tests for HTML applications such as online forms, e-shops, and other web applications based on HTML.

Basic workflow

To run tests in Tosca in the cloud, follow the steps below:

  1. Create ElasticExecutionGridEvents out of your ExecutionLists. Elastic Execution Grid is the execution service of Tosca in the cloud.

  2. Set Characteristics to determine which Tosca in the cloud Agents execute your tests.

  3. Define how Tosca in the cloud Agents should run your tests.

  4. Push your ElasticExecutionGridEvents to Tosca in the cloud.

  5. View results.

Create ElasticExecutionGridEvents

An ElasticExecutionGridEvent is a collection of ExecutionLists that you want to execute in Tosca in the cloud.

To create ElasticExecutionGridEvents, follow the steps below:

  1. In Tricentis Tosca, check out the project root element.

    This is an important step. Checking out the project root element ensures that Tricentis Tosca adds all necessary property definitions when you create the ElasticExecutionGridEvents folder.

  2. Create an ElasticExecutionGridEvents folder. To do so, right-click the Execution folder and select Create ElasticExecutionGridEvents folder from the mini toolbar. You only need to do this once.

Create a new ElasticExecutionGridEvents folder

  1. Create a new ElasticExecutionGridEvent. To do so, right-click the ElasticExecutionGridEvents folder and select Create ElasticExecutionGridEvent from the mini toolbar.

  2. Drag and drop the ExecutionLists that you want to run in Tosca in the cloud onto the ElasticExecutionGridEvent.

  3. Create as many ElasticExecutionGridEvents as you need.

Set Characteristics

Characteristics determine which Tosca in the cloud Agents execute your tests.

When admins set up Tosca in the cloud Agents (see the Tosca in the cloud manual), they define Agent Characteristics. Typically for the operating system and installed applications.

Let's say your tests require Google Chrome, but only two Agents have Google Chrome installed. In this case, the admin gives both an "Google Chrome" Characteristic.

In Tricentis Tosca, you specify which Characteristics you want to apply to your tests. If you have tests that involve Google Chrome, apply the "Google Chrome" Characteristic to them. Tosca in the cloud forwards these tests only to the "Google Chrome" Agents.

Only Tosca in the cloud Agents that match all Characteristics that you specify for your tests can execute them.

Make sure that the combination of Characteristics you select in Tosca is available in Tosca in the cloud.

To set Characteristics for your tests, follow the steps below:

  1. Select an ElasticExecutionGridEvent.

  2. Open the Properties pane.

  3. For the property AgentCharacteristics, enter the following information into the Value field: <Name of the Characteristic>=<Characteristic value>.

    For instance, Browser=Firefox.

    If you're unsure about Characteristic names and values, contact an Tosca in the cloud admin. Names and values depend on what the admin defined during the Tosca in the cloud Agent setup.

  1. You can specify multiple values for the same Characteristic name. To do so, separate the values by comma. For instance, Browser=Firefox,Chrome.

    You can also specify multiple Characteristics with different names. To do so, separate the names by semicolon. For instance, Browser=Chrome,Explorer;InstalledApps=SAP.

Let's say you have an ElasticExecutionGridEvent called GUI_tests. To execute the tests in this ElasticExecutionGridEvent, Tosca in the cloud Agents must have Salesforce, Chrome, and Firefox installed.

You have 3 Tosca in the cloud Agents.

Agent A has the following Characteristics:

  • One Characteristic named InstalledApps with the value SAP.

  • Two Characteristics named Browser, one with the value Chrome and one with the value Firefox.

Agent B has the following Characteristics:

  • One Characteristic named InstalledApps with the value Salesforce.

  • One Characteristic named Browser with the value Chrome.

Agent C has the following Characteristics:

  • One Characteristic named InstalledApps with the value Salesforce.

  • Two Characteristics named Browser, one with the value Chrome and one with the value Firefox.

To find the right Agent for execution, you add the following value to the property AgentCharacteristics of the ElasticExecutionGridEvent GUI_tests:

InstalledApps=Salesforce;Browser=Chrome,Firefox

At run-time, Agent C receives the tests for execution, since it's the only Agent with all required Characteristics.

Define how Tosca in the cloud Agents should run your tests

With Characteristics, you define which Tosca in the cloud Agents should execute your tests.

You can also define how these Agents should execute your tests.

Let's say you have two Tosca in the cloud Agents that are suitable for a particular ElasticExecutionGridEvent. Should only one Agent execute all TestCases? Or can you split tests between Agents?

Tosca in the cloud offers the following execution types:

  • SequentialSingleMachine: one Agent executes all TestCases in sequence.

  • SequentialMultipleMachines: TestCases are split between Agents, but executed in sequence. This speeds up execution by distributing test efforts between Agents.

  • Parallel: multiple Agents execute the TestCases within the ExecutionList in parallel. This is the fastest way to execute. However, Agents don't execute tests in sequence. Only choose this option if there are no dependencies between your TestCases.

By default, all ExecutionLists use the type SequentialSingleMachine.

If you want Tosca in the cloud to execute an ExecutionList differently, follow the steps below:

  1. Select the ExecutionList.

  2. In the Properties pane of the ExecutionList, select a different value for ExecutionFlow.

You need to set the property in the original ExecutionList.

You can’t do this in the ExecutionList within the ElasticExecutionGridEvent.

Select a value for the property ExecutionFlow

Push ElasticExecutionGridEvents to Tosca in the cloud

How you push tests to Tosca in the cloud depends on how the admin has setup up the integration:

  • Integration via Addin.

  • Integration via Automation Object Service (AOS).

If your admin has set up integration via Addin, follow the steps below:

Now that you have associated your ElasticExecutionGridEvents to ExecutionLists and the environment setup is complete, you can push them to the Tosca in the cloud. To do so, follow the steps below:

  1. Ensure that the tests you want to push aren't empty.

    • Each ElasticExecutionGridEvent must have at least one ExecutionList.

    • Each ExecutionList must have at least one TestCase.

  2. Right-click one or more ElasticExecutionGridEvents and select Execute from the context menu.

  3. In the subsequent window, sign in to Tosca in the cloud with your Tosca in the cloud credentials.

    You can also sign in or out separately. To do so, right-click the ElasticExecutionGridEvents folder and select Log in to Elastic Execution Grid or Log out from Elastic Execution Grid from the context menu.

  1. If the push was successful, the next screen shows the following information:

    • Which ElasticExecutionGridEvents were pushed to Tosca in the cloud.

    • Their corresponding IDs in Tosca in the cloud.

  2. Click OK.

If your admin has set up integration via AOS, follow the steps below:

  1. Ensure that the tests you want to push aren't empty.

    • Each ElasticExecutionGridEvent must have at least one ExecutionList.

    • Each ExecutionList must have at least one TestCase.

  2. If you have made changes to your tests, check in your changes.

  3. To push your tests, right-click one or more ElasticExecutionGridEvents and select Execute and import results from the context menu.

  4. If you use Tosca Server with an HTTPS binding and this is not a Tosca Server Repository workspace, sign in with your Tricentis User Administration credentials.

Please note: Tricentis Tosca doesn't display any Tosca in the cloud error messages. Instead, AOS logs all Tosca in the cloud issues in C:\ProgramData\TRICENTIS\Logs\ToscaAutomationObjectService.

View results

Where you can view your results depends on how the admin has setup up the integration:

You can view your results in Tosca in the cloud only.

You can view your results in Tosca in the cloud and in Tricentis Tosca. Tricentis Tosca displays the results on the ExecutionLists.

Tricentis Tosca only displays the results of tests that you triggered in Tricentis Tosca. If you trigger executions directly in Tosca in the cloud, Tricentis Tosca does not display those results.