Properties for execution with Tosca Distributed Execution
Once you have created an XML file, specify which TestEvents the Tosca Continuous Integration Client (Tosca CI Client) should forward for execution.
To do so, use the property TestEvent to filter for one of the following things:
For reasons of speed, Tricentis recommends that you filter for UniqueId or NodePath rather than the name of a TestEvent.
If you use multiple repositories with one Tosca Distribution Server, you have to set additional, custom properties as described in chapter "Custom properties for executing with multiple repositories".
Filter for the name of a TestEvent
Use the property TestEvent if you want to filter for the name of a TestEvent. You can filter for one or more TestEvents. In this case, each TestEvent in the repository must have a unique name.
The value of the property in the XML file has to be an exact match for the name of the TestEvent in Tosca Commander.
In the following example, the Tosca CI Client filters for the TestEvent with the name SampleTestEvent.
<?xml version="1.0" encoding="utf-16" ?>
<testConfiguration>
<TestEvents>
<TestEvent>SampleTestEvent</TestEvent>
</TestEvents>
</testConfiguration>Filter for the system ID of a TestEvent
Use the property TestEvent if you want to filter for the system ID of a TestEvent. You can filter for either its UniqueId or its NodePath.
The value of the property in the XML file must be an exact match for the value of the UniqueId or the NodePath in Tosca Commander.
You can filter for one or more TestEvents. In the example below, the Tosca CI Client triggers the execution of two different TestEvents:
-
The TestEvent with the UniqueId 123456789
-
The TestEvent with the NodePath /Execution/SampleTestEvent
<?xml version="1.0" encoding="utf-16" ?>
<testConfiguration>
<TestEvents>
<TestEvent>123456789</TestEvent>
<TestEvent>/Execution/SampleTestEvent</TestEvent>
</TestEvents>
</testConfiguration>