Author: Matthias Steinkogler
The goal of this blog entry is to concisely show how to use Silk Test to make functional testing part of your Continuous Integration (CI) routine, based on the example of Silk Central and Jenkins.
This document assumes that you already have the following infrastructure in place:
- A Silk Central server with valid test execution definitions, and
- A Jenkins/Hudson server set up to run CI builds.
Get Information from Silk Central
You need to retrieve the Project ID and the Execution Plan ID of the execution(s) that you want to run from your Silk Central server.
- Log in to Silk Central.
- Select Execution Planning -> Detail View.
- To retrieve the Project ID, select the project in the left tree view pane.
- You will find the Project IDhere:
- To retrieve the Execution Plan ID, select the execution definition in the left tree view pane.
- You will find the Execution Plan ID here:
Set Up Jenkins
- Install the SCTMExecutor plugin in Jenkins. This plugin connects Jenkins to your Silk Central server.
- Configure the SCTMExecutor plugin:
- In the global Jenkins configuration page, there will now be an entry SilkCentral TestManager Konfiguration.
- Enter the server’s address, and a username and password:
- Extend your CI build job.
Now, whenever your CI Build Job is executed, it also triggers the execution of the specified Silk Central execution(s).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.