The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.


tptReport: TPT Report

    tptExecute: Execute TPT test cases

    The "Execute TPT test cases" build step can run in two modes.
    • Just execute the tests within this Job. The given values will be used to create a command that will be executed. This command could be typed into the command line and would work.
    • Use this Job as a Master. In this mode the TPT RMI API is used to read the test cases that must be executed. For every test case a slave job is started and parameters are provided that can be used by the "Execute TPT tests slave" build step. The slaves copy their reults back to the master and the master will aggregate the test results.
    The master mode can be activated and configured by clicking on the "Advanced" button.
    • exePaths : String
    • executionConfiguration
        Array / List of Nested Object
      • tptFile : String
      • configuration : String
      • id : String
      • enableTest : boolean (optional)
      • reportDir : String (optional)
      • testSet : String (optional)
      • testdataDir : String (optional)
      • timeout : long (optional)
    • arguments : String (optional)
    • enableJunit : boolean (optional)
    • isTptMaster : boolean (optional)
    • jUnitLogLevel (optional)
    • jUnitreport : String (optional)
    • slaveJob : String (optional)
    • slaveJobCount : String (optional)
    • slaveJobTries : String (optional)
    • tptBindingName : String (optional)
    • tptPort : String (optional)
    • tptStartUpWaitTime : String (optional)

    tptAgent: Execute TPT tests as a worker for a TPT master job

    This build step expects to be executed in a job started by an "Execute TPT test cases" build step in master mode. The master job will provide some parameters used by this build step. It will execute excatly one test case and copies the result back to the master node. To execute a single test case the build step uses the TPT RMI API. The Job should be only run once on every Computer. You can achive that e.g. by Throttle Concurrent Builds Plugin
    • exePaths : String
    • arguments : String (optional)
    • tptBindingName : String (optional)
    • tptPort : String (optional)
    • tptStartUpWaitTime : String (optional)

    Was this page helpful?

    Please submit your feedback about this page through this quick form.

    Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?


    See existing feedback here.