Create and execute TestEvents

A TestEvent organizes the execution with Tosca Distributed Execution.

It contains the following objects:

• One or more ExecutionLists. An ExecutionList is a collection of TestCases that you want to execute in a specific order.

• Configurations. Configurations specify which Tosca Distribution Agents should execute which ExecutionLists within the TestEvent.

Once you trigger the execution, Tricentis Tosca transfers your TestEvent to the Tosca Distribution Server. The server then assigns the ExecutionLists to the Agents whose configuration matches the one(s) in the TestEvent.

TestEvent workflow

To create and execute TestEvents, follow the workflow outlined below. For more information, see the subsequent chapters which describe each step in detail.

1. Create a new TestEvent.

2. Assign configurations to the TestEvent.

3. If you use Tosca Distributed Execution with AOS, perform the following actions:

   • Define your results folders.

   • Define which ExecutionLists you want to split between Agents during execution.

4. Execute the TestEvent.

If you use Tosca Distributed Execution with Tosca Continuous Integration, the Tosca Continuous Integration Client triggers the execution of your TestEvents.

Create a new TestEvent

To create a new TestEvent, follow the steps below:

1. In Tosca Commander, go to the Execution tab.

2. Check out the TestEvents object.

3. Right-click TestEvents and select Create New TestEvent from the mini toolbar.

Assign configurations

Configurations specify which Agent pool should execute which tests.

Tricentis Tosca offers the default configurations Any, RDP, and SupportsClassic.

You can also use custom configurations. For instance if some ExecutionLists require Windows Vista and only a few Agents have Windows Vista installed. Consequently, only this Agent pool should execute these tests. In this case, create a custom configuration for Windows Vista and assign this configuration to the TestEvent. At run-time, the Tosca Distribution Server forwards the Windows Vista ExecutionLists only to the Windows Vista Agents.

To assign configurations to a TestEvent, follow the steps below:

1. Drag and drop the configurations that you want to use onto the TestEvent.

2. Define which Agents should execute which ExecutionList. To do so, drag and drop ExecutionLists onto the respective configurations.

If you have modified your configurations, or if Tosca Commander lists your Agents in the wrong category, check out the project root element. Then right-click Configurations and select Update configurations from Server from the context menu.

If Tosca Commander doesn't display the available Agents after a check-in, or it displays the wrong number or status of Agents, right-click Configurations and select Refresh Agents from the context menu.

Define results folders

This option is only available if you use Tosca Distributed Execution with AOS.

Tricentis offers the following results folder types:

• Custom results folders for specific TestEvents.

• A default results folder. This folder contains the results of all TestEvents which don't have a custom results folder.

After the test run, Tricentis Tosca creates a sub-folder within the test results folder for each TestEvent. Within this folder, Tosca Commander creates a TestMandate for each ExecutionList in the TestEvent.

You can change results folders if you need.

Create a custom results folder

To define a custom results folder, follow the steps below:

3. Create a new ExecutionList folder.

4. In the Properties pane of the new ExecutionList folder, enter a unique Value for the property ContinuousIntegrationBuildRootFolder.

5. Copy this value.

6. Now define which TestEvent should write its results to this folder:

   • Select the respective TestEvent.

   • In the Properties pane of the TestEvent, paste the value into the Value field of the property ResultFolder.

   Repeat this process for all TestEvents whose results should be in this particular folder.

7. You can create as many results folders as you need. To do so, repeat the following process:

   • Create a new ExecutionList folder.

   • Enter a unique value for the ExecutionList property ContinuousIntegrationBuildRootFolder.

   • Enter the same value for the property ResultFolder of all TestEvents whose results should be in this particular folder.

Create a default results folder

To define a default results folder, follow the steps below:

8. Create a new ExecutionList folder.

9. In the Properties pane of the new ExecutionList folder, set the property ContinuousIntegrationBuildRootFolder to True.

Change results folders

You can change test results folders. To do so, perform the steps below:

1. In the properties of the ExecutionList folder that you don't want to use anymore, delete the value of ContinuousIntegrationBuildRootFolder.

2. In the properties of the results folder you want to use instead, enter a value for the property ContinuousIntegrationBuildRootFolder.

   • If you enter True, this folder becomes the new default results folder.

   • If you enter a unique value, this folder becomes an additional results folder.

3. If you have TestEvents that write their results to the folder you don't use anymore, modify the TestEvent properties. Enter the value of the new results folder as the value of the property ResultFolder.

Define ExecutionLists to split during execution

This option is only available if you use Tosca Distributed Execution with AOS.

If all TestCases in an ExecutionList are independent of each other, you can split the ExecutionList between Agents. The Agents then execute the TestCases simultaneously, which speeds up the test run.

To do so, follow the steps below:

1. Select the ExecutionList whose TestCases you want to execute in parallel.

2. In the Properties pane of the ExecutionList, enter the value True for the property TCDistribution.

3. Repeat these actions for all ExecutionLists whose TestCases you want to execute simultaneously.

To disable simultaneous execution for an ExecutionList, set the property TCDistribution to False.

Execute a TestEvent

Prerequisites

To run your TestEvents, you must meet the following requirements:

	The Tosca Distribution Server is running.
	You have at least one Idle Agent.
	ExecutionLists are checked in. Tricentis recommends that you Checkin all before you trigger executions.
	Only if your tests contain Classic TestSteps: you have turned on the setting Check for Legacy Steps.
	Only if you use Distributed Execution without AOS: the Agent workspaces are closed.
	Only if you use Distributed Execution with AOS: the AOS workspace is closed.

Trigger execution

To trigger the execution of a TestEvent, right-click the TestEvent and select Execute now from the context menu.

Once the execution is done, click Update all in the Home menu to update your workspace with the results:

• If you use Distributed Execution with AOS, check your results folders.

• If you use Distributed Execution without AOS, check your ExecutionLists.

Alternatively, you can monitor the execution as described in chapter "Monitor and cancel TestEvents in the Tosca Distributed Execution Monitor".