Call parameters for execution via Remote Service

Once you are ready to execute your tests, call up the respective Tosca Continuous Integration Client (Tosca CI Client) with the help of call parameters, using the command line.

Launch from Windows operating systems

If you launch your tests from Windows operating systems, call up ToscaCIClient.exe.

In this case, the Tosca CI Client will behave in the way you have previously specified in the ToscaCIClient.exe.config file.

Launch from operating systems other than Windows

If you launch your tests from operating systems other than Windows, call up ToscaCIJavaClient.jar.

In this case, the Tosca CI Client will behave in the way you have previously specified in the config.properties file.

To call up ToscaCIJavaClient.jar, you need to install a Java Runtime environment.

For information on software versions and hardware requirements, see the Tricentis Tosca system requirements.

Call parameters

If you have set up Tosca Continuous Integration for execution via Remote Service, use the following call parameters:

Call parameter	Description	Optional
-m distributed	Specifies that the tests should be executed on another workstation.
-e	Defines the endpoint of the Remote Execution Service. If you have replaced the host name with the IP address of the Remote Execution Service in the ToscaCIClient.exe.config or in the config.properties, this call parameter is not mandatory. If the endpoint address in the ToscaCIClient.exe.config or in the config.properties contains the host name, you must use call parameter -e. Example: -e “http://192.168.1.12:8732/TOSCARemoteExecutionService/”	(X)
-c	Use this parameter to specify the path of the XML file that defines which ExecutionLists should be executed in this test run. Example: -c “c:/temp/CITestExecutionConfiguration.xml”	X
-r	Specifies where the test results will be stored. You need to have write access to the specified directory. This call parameter overrides the setting PathToResultFile in the ToscaCIClient.exe.config or in the config.properties for this test run. Example: -r “c:/temp/result.xml”	X
-x	If the value of the -x parameter is set to True, the system uses a specific ExitCode to exit the Tosca CI Client in this particular test run. Call parameter -x overrides the setting ConsiderExecutionResult in the ToscaCIClient.exe.config or in the config.properties for this test run. Example: -x True	X
-l	Use call parameter -l if you want to change the Tosca CI Client user name that the system will accept for this particular test run. The value for call parameter -l must match the value of the setting AuthenticationUsername in the ToscaCIRemoteExecutionService.exe.config file. Call parameter -l only overrides the ToscaCIClient.exe.config or the config.properties for this test run. Example: -l SampleUsername	X
-p	Use call parameter -p if you want to change the Tosca CI Client password that the system will accept for this particular test run. The value for call parameter -p must match the value of the setting AuthenticationPassword in the ToscaCIRemoteExecutionService.exe.config file. Call parameter -p only overrides the ToscaCIClient.exe.config or the config.properties for this test run. Example: -p SamplePassword	X
-t	Specifies the structure of test results. Call parameter -t only overrides the ToscaCIClient.exe.config or the config.properties for this test run. Example: -t junit	X

Example

The command line below calls up the ToscaCIClient.exe with the following information:

The tests should be executed on another workstation.
The system should only execute the ExecutionLists with the properties defined in the file CITestExecutionConfiguration.xml, located at c:/temp/.
The results of this particular test run should be saved to c:/temp/result.xml.

ToscaCIClient.exe -m distributed -c “c:/temp/CITestExecutionConfiguration.xml” -r “c:/temp/result.xml”

The command line below calls up the ToscaCIJavaClient.jar with the same information:

java -jar ToscaCIJavaClient.jar -m distributed -c “c:/temp/CITestExecutionConfiguration.xml” -r “c:/temp/result.xml”