Child pages
  • Tricentis Continuous Integration

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Tricentis Continuous Integration plugin integrates Jenkins with Tricentis Tosca CI and allows users . With this plugin, you can execute Tricentis Tosca tests via Jenkins.

For more details To configure Jenkins for the execution of Tricentis Tosca tests, perform one of the following actions:

Once you have configured Jenkins for Tricentis Continuous Integration, execute your tests.


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

You can execute your tests via Tosca Remote Service or Tosca Distributed Execution.

 


Wiki Markup
{jenkins-plugin-info:pluginId=tricentis-ci}

Executing tests from Jenkins

...

Anchor
add_build_step
add_build_step
Add a new Tricentis Continuous Integration

...

build step

...


To execute tests in Tricentis Tosca CI, add a new " Tricentis Continuous Integration " build step should be added:

Image RemovedImage Added


Field
Name (
name [pipeline property
)
]RequiredDescription

Tricentis

Client Path (tricentisClientPath)

client path

[tricentisClientPath]

Yes
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

is used

, you need to install JRE 1.7 or higher

should be installed

on the Jenkins Slave machine and set the JAVA_HOME environment variable

should be set

accordingly.

Endpoint

(


[endpoint

)

]

Yes
This specifies

Specify the

IP

address of the webservice

when

. This component triggers the test execution

is performed on an external test computer. The webservice can be the TOSCARemoteExecutionService of the external test computer or the Path to

.

If you execute your tests via Tosca Remote Service, the endpoint needs to point to the TOSCARemoteExecutionService (e.g. http://servername:8732/TOSCARemoteExecutionService/).

If you execute your tests via Tosca Distributed Execution, the endpoint needs to point to the Manager Service of the Tosca Distribution Server (e.g. http://servername:8732/DistributionServerService/ManagerService.svc).

Configuration File (configurationFilePath)

No

TestEvents (Distributed Execution only)

[testEvents]

No

Input the TestEvents that you want to execute, separated by semicolons. You can identify the TestEvents with their name or their system ID.

This field is optional. It can only be used if you execute your tests via Tosca Distributed Execution.

If you use this setting, leave the Configuration File setting of this page empty. Otherwise, this build step fails.

Configuration file

[configurationFilePath]

No

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.

If you use this setting, leave the TestEvents setting of this page empty. Otherwise, this build step fails.

Anchor
configure_pipeline
configure_pipeline
Configure the Jenkins pipeline for Tricentis Continuous Integration

...


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

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

Execution

...

Anchor
execute_tests
execute_tests
Execute tests

After you configure the job, run it.

Jenkins job output example

...

Image RemovedImage Added

Tricentis reports

...

automatically published to

...

Jenkins

...