The Tricentis Continuous Integration plugin integrates Jenkins with Tricentis Tosca CI. With this plugin, you can execute Tricentis Tosca tests via Jenkins.
To trigger the execution of Tricentis Tosca tests via Jenkins, follow the steps below:
- Add a new Tricentis Continuous Integration build step.
- Optionally, configure the Tricentis Continuous Integration pipeline.
- Execute tests.
For more information on Tricentis Tosca and Tosca Continuous Integration, see the following links:
View Tricentis Continuous Integration on the plugin site for more information.
Add a new Tricentis Continuous Integration build step
To execute tests in Tricentis Tosca CI, add a new Tricentis Continuous Integration build step:
|Field name [pipeline property]||Required||Description|
Tricentis Client Path
Input the path to either the ToscaCIClient.exe or the ToscaCIJavaClient.jar file. This component is responsible for sending the execution request to your execution machines.
If you use ToscaCIJavaClient.jar, you need to install JRE 1.7 or higher on the Jenkins Slave machine and set the JAVA_HOME environment variable accordingly.
Specify the IP address of the webservice when the execution is performed on an external test computer. This component triggers the test execution.
The webservice can be the TOSCARemoteExecutionService of the external test computer (e.g. http://servername:8732/TOSCARemoteExecutionService/) or the Manager Service of the Tosca Distribution Server (e.g.).
TestEvents (Distributed Execution only)
Input the TestEvents that you want to execute, separated by semicolons. You can identify the TestEvents with their name or their system ID. If you use this setting, the Configuration File setting of this page is ignored.
Specify the path to the Tricentis CI test execution configuration XML file. The test configuration file includes more details about which items you would like to execute.
Configure the Tricentis Continuous Integration pipeline
If you use Jenkins Pipelines, you can specify Tricentis Tosca build logic with pipeline script:
After you configure the job, run it.
Jenkins job output example
Tricentis reports automatically published to Jenkins