Table of Contents
Use the SilkCentral integration to run any test suite managed by Borland's SilkCentral Test Manager (see Using the SilkCentral Integration). SilkCentral may be integrated as part of the build job or used as part of a non-originating workflow (secondary process) on any Build Life. Once the tests have been run, metrics are available on the Build Life Reports and Tests tabs (see also Run SilkCentral Build Workflow and Run SilkCentral Secondary Workflow).
How the integration is used will typically be determined by (a.) the type and duration of the test suite to be run; and (b.) when the test suite is to be run. For example, to run Unit (or other short duration) tests as part of a Continuous Integration build, the Run Tests step must be included as part of the build process. See Use SilkCentral as Part of a Build.
The integration may also be used to run long tests, such as functional tests, as part of a secondary workflow that does not require any other job steps. See Use SilkCentral as Part of a Secondary Workflow.
In order to use the integration, AnthillPro must first be configured with SilkCentral (see Set Up SilkCentral). The integration is implemented as an AnthillPro job step configured on the Job Configuration page. When using the integration, click the Create Step button (or select the Insert After/Before icon) to add the step to a job. Once the job is configured, it is then added to the workflow under the Definition tab.
SilkCentral Step:
Run Tests. Runs a test suite using Borland SilkCentral Test Manager. May be used as part of an originating and/or non-originating workflow.
This tutorial will follow a simple project configuration that first uses the SilkCentral Run Tests step as part of an originating workflow (i.e., a Continuous Integration build job) to run Unit tests, and as a secondary workflow to run functional tests, etc. The example in this tutorial uses Subversion, but the basic configuration is similar for any repository type. Your jobs will vary, but the SilkCentral integration is added as a job step similar to what is described below.
Once set up as a SilkCentral user, AnthillPro must be able to access the server in order for the integration to work. Any steps relying on the SilkCentral integration will not work until the configuration is complete.
All fields may contain scripts and/or property lookups. See Scripting.
You must have AnthillPro administrative privileges. See Manage Security.
A project must be active in AnthillPro. See Simple Continuous Integration.
The SilkCentral URL must be available.
AnthillPro must be set up as a SilkCentral user. See SilkCentral documentation.
Go to System > SilkCentral Test Manager from the Integrations menu.
On the Borland SilkCentral Test Manager Integration page, click Edit.
Configure the integration:
Borland SilkCentral Server URL. Provide the SilkCentral server URL.
User Name. Give the SilkCentral user name assigned to AnthillPro.
Password. Provide the password AnthillPro will to connect to the SilkCentral server.
Password Script. To use a script or property lookups for the password, leave the Password field blank and enter the script here. See Scripting.
Click Set then Done.
The SilkCentral integration allows AnthillPro users to automate the test orchestration process by configuring a build (originating) workflow to run SilkCentral-managed tests during the build, or as a non-originating workflow (secondary process) to be run on any successful Build Life. This section only covers the steps necessary for creating a build job that uses SilkCentral and a secondary workflow that kicks off the test manager. While your job configuration will vary, the SilkCentral integration is used similar to what is described below.
The Set Up SilkCentral section of this tutorial must be complete.
You must have administrative privileges. See Manage Security.
A project with at least one Build Life must be active in AnthillPro (if using the integration as part of a secondary workflow). See Simple Continuous Integration.
To run Unit (or other short duration) tests as part of a Continuous Integration build, the Run Tests step must be included as part of the build process that typically includes a set working directory, get changelog, and publish changelog step. Once the SilkCentral Run Tests step is added to the build job, AnthillPro will kick off the tests associated with the step as part of the build, and provide feedback on the Dashboard Build Life page.
The items below only cover the steps necessary to using the SilkCentral integration as part of a build workflow. For detailed configuration instruction, see Simple Continuous Integration.
Each build job is different; however the SilkCentral step is configured similar to what is below. It is also possible to configure AnthillPro to make decisions to pass or fail the build based on the results of the tests run during the build.
Go to Administration, select the project that is to be tested, and click the Add Job icon.
On the New Job Configuration page, choose No (do not use the Job Wizard). Click Select.
On the next page, name the job, give a description (optional) and click Set.
Follow the steps for creating a job. See Simple Continuous Integration.
Run Tests. Click the Insert After button of the step prior to the point where the Run Tests step is to be included (e.g., typically after the set working directory, build, get changelog steps), expand the Silk Central Test Manager folder, select Run Tests step, and click Select.
Name the step.
Description. Provide an optional description.
Project Name. Give the name of the SilkCentral project.
Tests. Provide the path, relative to the SilkCentral project, of all the tests to be run by this job. If the tests are to be identified by scripts, separate them by a comma; if the path is hard coded, each test can be input on a separate line.
Ignore Missing Tests. Check the box to have AnthillPro ignore any missing tests. If a test is defined in the Tests field above and is missing, AnthillPro will fail the job unless the box is checked.
Execution Server Host. To restrict the host on which the tests can run, give the location of the SilkCentral Execution Host. If left blank, AnthillPro will run the tests on any of the available hosts.
Execution Server Port. If the execution server is restricted to a particular port, give it here. Inputting a value of -1 (negative one) will allow the tests to run on any available port.
Show Additional Options (advanced). Select the Show Additional Options link to configure more options.
Is Active. Select No to temporarily deactivate the step without deleting it; otherwise select Yes.
Continuation Condition. Select the condition which must be met for the process to continue (all steps pass; previous step passed; any step failed; always; or never).
Ignore Failures. Select Yes if this step should not affect the determination for step continuation or the status determination of the job.
PostProcessScript. Select a script for determining when commands should count as fail or succeed.
Timeout Enter the time in minutes after the start of the step when AnthillPro will consider the step as timed out and abort it.
Click Save.
The SilkCentral job must be executed as part of a build workflow in order to run Unit tests as part of the Continuous Integration build. This section assumes familiarity with the originating workflow creation process, and only covers the topics necessary to adding the job (see Configure SilkCentral Build Job) to the workflow.
Go to Administration and select the Add Workflow icon of the appropriate project.
Check Originating Workflow and click Select.
Configure workflow. Complete workflow configuration is beyond the scope of this tutorial; for detailed instructions on workflows, see Simple Continuous Integration.
On the workflow Main page, select the Definition tab.
From the drop-down menu, choose Embedded Definition and click Select.
Left-click the Start icon and select Insert Job After.
Select the Build job created in the Configure SilkCentral Build Job section, a job pre-condition script, and click Insert Job.
Go to Dashboard and select the workflow created in the Configure SilkCentral Build Workflow section.
On the workflow Main page, click the Build button.
Once the workflow is complete, go to the Build Life page and select the Reports tab.
Select the test from the Publish Reports menu. A detail of each test run (not shown) is also available.
Once the workflow is complete, go to the Build Life page and select the Tests tab.
To drill down on each step on the Build Life Summary page, see Trace a Build Life to Source.
To automatically kick off long tests (e.g., functional tests), the SilkCentral Run Tests step is typically configured as part of a secondary workflow which is run on an existing Build Life. The integration does not require any other job steps to be run as part of the workflow, and, for example, can be scheduled to kick off the test suite using a schedule or trigger (see Triggers and Scheduled Builds).
The items below only cover the steps necessary to using the SilkCentral integration as part of a secondary (non-originating) workflow. For detailed configuration instruction, see Run a Simple Deployment.
The Run Test step may be used on its own; however, depending on the needs of each project, the job may require other steps to start a virtual machine, pass links, evaluate scripts, etc.
Go to Administration, select the project that is to be tested, and click the Add Job icon.
On the New Job Configuration page, choose No (do not use the Job Wizard). Click Select.
On the next page, name the job, give a description (optional) and click Set.
Follow the steps for creating a job. See Run a Simple Deployment.
Run Tests. Click the Create Step button, expand the Silk Central Test Manager folder, select Run Tests step, and click Select.
Name the step.
Description. Provide an optional description.
Project Name. Give the name of the SilkCentral project.
Tests. Provide the path, relative to the SilkCentral project, of all the tests to be run by this job. If the tests are to be identified by scripts, separate them by a comma; if the path is hard coded, each test can be input on a separate line.
Ignore Missing Tests. Check the box to have AnthillPro ignore any missing tests. If a test is defined in the Tests field above and is missing, AnthillPro will fail the job unless the box is checked.
Execution Server Host. To restrict the host on which the tests can run, give the location of the SilkCentral Execution Host. If left blank, AnthillPro will run the tests on any of the available hosts.
Execution Server Port. If the execution server is restricted to a particular port, give it here. Inputting a value of -1 (negative one) will allow the tests to run on any available port.
Show Additional Options (advanced). Select the Show Additional Options link to configure more options.
Is Active. Select No to temporarily deactivate the step without deleting it; otherwise select Yes.
Continuation Condition. Select the condition which must be met for the process to continue (all steps pass; previous step passed; any step failed; always; or never).
Ignore Failures. Select Yes if this step should not affect the determination for step continuation or the status determination of the job.
PostProcessScript. Select a script for determining when commands should count as fail or succeed.
Timeout Enter the time in minutes after the start of the step when AnthillPro will consider the step as timed out and abort it.
Click Save.
The SilkCentral job can be executed as part of a secondary (non-originating) workflow in order to run functional (or other) tests on an existing Build Life. While there are numerous ways to use the SilkCentral integration to automatically run testing suites, your particular workflow will be similar to what is presented here. For example, you can set up the workflow to run on a scheduled trigger (see Triggers and Scheduled Builds) that kicks off the testing suite, or can even include functional and other long running testing as part of the build process (see also Use SilkCentral as Part of a Build).
Go to Administration and select the Add Workflow icon of the appropriate project.
Check Non-originating Workflow and click Select.
Configure workflow. Complete workflow configuration is beyond the scope of this tutorial; for detailed instructions on workflows, see Run a Simple Deployment.
On the workflow Main page, select the Definition tab.
From the drop-down menu, choose Embedded Definition and click Select.
Left-click the Start icon and select Insert Job After.
Select the Build job created in the Configure SilkCentral Secondary Job section, a job pre-condition script, and click Insert Job.
If setting a trigger, see Triggers and Scheduled Builds.
Go to Dashboard and select the originating workflow to be tested.
On the Main page, select the appropriate Build Life.
On the BuildLife Main page, click the Run Secondary Process button.
From the drop-down box, choose the workflow created in the Configure SilkCentral Secondary Workflow section, and click Next.
Select the environment and click the Run button.
Once the workflow is complete, go to the Build Life page and select the Reports tab.
Select the test from the Publish Reports menu. A detail of each test run (not shown) is also available.
Once the workflow is complete, go to the Build Life page and select the Tests tab.
To drill down on each step on the Build Life Summary page, see Trace a Build Life to Source.