Triggering Tests on Silk Central from a Continuous Integration Server

To run Silk4J tests from a continuous integration server, the following infrastructure is required:
  • A Silk Central server with the appropriate execution definitions.
    Note: This topic focuses on the integration with Silk Central, but you could also use another test-scheduling tool.
  • A continuous integration (CI) server, for example Hudson or Jenkins. This topic uses Jenkins as an example.

To replay functional tests from a CI server:

  1. In Silk Central, retrieve the project ID and the execution plan ID of any execution plan that you want to run from the CI server.
    1. Select Execution Planning > Details View.
    2. In the Execution Plans tree, select the project that contains the execution. The Project ID is displayed in the Properties pane of the project.
    3. In the Execution Plans tree, select the execution plan. The Execution Plan ID is displayed in the Properties pane of the execution plan.
  2. Install the SCTMExecutor plugin on the CI server. This plugin connects the CI server to your Silk Central server.
  3. Configure the SCTMExecutor plugin:
    1. On Jenkins, navigate to the Silk Central Test Manager Configuration configuration in the global Jenkins configuration page.
    2. Type the address of the Silk Central service into the Service URL field. For example, if the server name is sctm-server, type http://sctm-server:19120/services.
  4. Extend your CI build job.
    1. On Jenkins, select Silk Central Test Manager Execution from the Add build step list.
    2. Type the ID of the execution plan into the Execution Plan ID field.

      You can execute an arbitrary number of execution plans by separating the IDs with a comma.

    3. Type the project ID of the Silk Central project into the SCTM Project ID field.
Whenever your CI build job is executed, it also triggers the execution of the specified Silk Central execution plans.