Child pages
  • Tricentis Continuous Integration

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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:

  1. Add a new Tricentis Continuous Integration build step
  2. Configure the Tricentis Continuous Integration pipeline
  3. Execute tests

For more information on Tricentis Tosca and Tosca Continuous Integration, see the following links:

 

Plugin Information

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)RequiredDescription
Tricentis Client Path (tricentisClientPath)YesPath to either ToscaCIClient.exe or ToscaCIJavaClient.jar file. If ToscaCIJavaClient.jar is used, JRE 1.7 or higher should be installed on Jenkins Slave machine and JAVA_HOME environment variable should be set accordingly
Endpoint (endpoint)Yes

This specifies the IP address of the webservice when the execution is performed on an external test computer. The webservice can be the TOSCARemoteExecutionService of the external test computer or the Manager Service of the Tosca Distribution Server

TestEvents (Distributed Execution only)NoInput the Test Events that you want to execute, separated by semicolons. You can identify the TestEvents with their name or their system ID. For more details, refer to our manual. If you use this setting, the Configuration File setting of this page is ignored.

Configuration File (configurationFilePath)

NoPath to Tricentis CI test execution configuration XML file

Configure the Tricentis Continuous Integration pipeline

If you use Jenkins Pipelines, you can specify Tricentis Tosca build logic with pipeline script:

Pipeline configuration
pipeline {    
    agent any
    stages {
       stage('Build') {
          steps {
             tricentisCI tricentisClientPath: '$TRICENTIS_HOME\\ToscaCI\\Client\\ToscaCIClient.exe', configurationFilePath: 'configuration.xml', endpoint: 'http://localhost:8732/TOSCARemoteExecutionService/'
          }
       }
    }
}

Execute tests

Once the job is configured, simply run the job. Here is Jenkins job output example:

Tricentis reports are automatically published to the Jenkins:


  • No labels