Versions Compared


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



This plugin lets you run TestComplete tests from Jenkins. The plugin provides a build step that lets you include TestComplete tests into your Jenkins builds. Also, the plugin maintains a list of test runs and lets you view test results directly from within Jenkins.


Wiki Markup



  1. Prepare a test computer (node) for automated testing. Make sure the node has everything it needs to run tests successfully:
    • It has TestComplete or TestExecute installed.
    • It has required browsers, test data files, and other helper files and applications.
    • If you have a desktop tested application, make sure the node has that application installed before the TestComplete tests start working.
      To copy files to the node, you can use the CopyToSlavePlugin, or copy the files manually.
  2. Add the TestComplete Test step to your Jenkins build.
  3. Customize the step’s properties:
    • Select the test runner: TestComplete or TestExecute.
    • Specify the TestComplete project suite file and select tests to be run.
    • Important: Select the Run interactive user session check box, if needed (see below), and specify additional parameters for the run.
  4. Run the build as you would normally do this.
  5. After the build run is completed is over, you will see the TestComplete Test Results link on the build’s page.
    Click the link to view test results. In the subsequent screen, click the link in the Test column to explore detailed test results.


The node must run an interactive user session. Otherwise, TestComplete (or TestExecute) will be unable to interact with the UI of the application under test.
To create an interactive user session:



Version History

Version 1.2
  • New feature: Generating test reports in the MHT format.
  • New feature: Support for generating and publishing JUnit-style reports.
  • New feature: Now you can use Jenkins variables to configure the TestComplete Test step.
  • Fixed: An exception occurred when the TestComplete Test step was added to a Conditional Build Step.
Version 1.3
  • New feature: Support for TestComplete 11 and TestExecute 11.
  • Fixed: It was impossible to run jobs with TestComplete Test steps on different nodes in parallel.
  • Fixed: The TestComplete Jenkins plugin worked incorrectly if a slave node was controlled via a service started from a JNLP application.