Define which tests to execute

You can define which tests the Tosca Continuous Integration Client (Tosca CI Client) should trigger for a particular test run.

For execution with Tosca Distributed Execution, this is mandatory. You need to tell the system which TestEvents to execute.
For execution via Remote Service or on the build server, this is optional.

By default, the system executes all ExecutionLists for which you have set the property ContinuousIntegration to True. You can modify the execution command to limit the execution to a particular subset of these ExecutionLists.

For instance, you can choose to only execute ExecutionLists that contain your smoke tests.

To define the execution command to the Tosca CI Client, follow the steps below:

Prepare the workspace that will execute your tests:
- For information on how to prepare your Remote or build server workspace, see chapter "Prepare the workspace".
- For information on how to prepare your Tosca Distributed Execution workspace, see chapter "Create and execute TestEvents".
Create an XML file that defines which properties the Tosca CI Client should filter for.
Once you launch the execution of your tests, define call parameter -c.

The Tosca CI Client then accesses the XML file and triggers the execution of all tests with the specified properties.

Create the XML file

You can give the file any name and save it to any directory the Tosca CI Client has access to.

When you create the XML file, follow the format below:

Copy

<?xml version="1.0" encoding="utf-16" ?>
<testConfiguration>
</testConfiguration>

Within the testConfiguration tags, define the properties you want to filter for.

Depending on how you run the execution of your tests, you can specify different properties: