Configuring the Jenkins environment for running tests

If your Jenkins environment has the HCL OneTest API Test Execution plug-in installed, you can use it to run tests without the need for Apache Ant. Use of the plug-in can provide improved test execution shutdown if a job is aborted. Alternatively, you can use the Ant plug-in to run an Ant script that will in turn run the tests.

Before you begin

Running tests by using the HCL OneTest API Test Execution plug-in

Procedure

  1. On the Jenkins dashboard, create a new project or modify an existing project.
  2. On the Project page, click Configure.
  3. Under Build, click Add build step.
  4. Select Run HCL OneTest API Tests. The following dialog is displayed:

    runtests

  5. Fill in values for the task as required: Enter values for the following: Installation directory, Project, Environment, and Tests. If you leave the Installation directory blank, the following environment variables will be queried at runtime to find the directory: INTEGRATION_TESTER_AGENT_HOME and INTEGRATION_TESTER_HOME. If no value is found, the job will fail. These variables must be visible to the user or the service account that is running the Jenkins master or slave. If you update either of the environment variables, you must restart the Jenkins master or slave for the values to take effect.

    Optionally, click Advanced to view and update the other fields as needed. For a detailed description of any field, click the question mark icon that is next to it. Also see Run tests by using an Ant task.

  6. Click Save.

Running tests by using the Ant plug-in

Procedure

  1. On the Jenkins dashboard, create a new project or modify an existing project.
  2. On the Project page, click Configure.
  3. Under Build, click Add build step.
  4. Select Invoke Ant.
  5. Click Advanced.
  6. In the Build File field, enter the location of the Apache Ant script that was generated by HCL OneTest API.
  7. Click Save.
Feedback