Plugin Information

This plugin will let users use Borland's SilkCentral Test Manager 2008 R2 or later.

SCTMExecutor Plugin

This plugin is an integration of Borland's SilkCentral Test Manager 2008 R2 (SCTM). You can execute Execution Definitions (a kind of job description). SCTM is designed to execute tests and archive the results to enable some reports.

Settings

Global Settings

In the global settings the url of the execution service (provided by SCTM) and a valid user and password must be specified. The password is stored encrypted in the hudson plugin configuration!

Project Settings

To execute some execution definitions (or folders) you need to add the id(s) (in a coma separated list) and the project id. Execution definitions must be in the same project, otherwise you need to add another build step.

Results

The results of the tests executed on SCTM are collected and written in the same format as JUnit tests. You will find a folder (<workspace>/SCTMResults) where all results are stored. For each execution definition / folder on file. You can add these files to the JUnit Test Result Publisher by adding SCTMResults/TEST-*.xml to the configuration.

Changelog

Version	Comment
1.5.1	add additional option to allow execution with a preconfigured build number on SCTM add execution definition name to the logs documentation for build number usage options
1.5	BUGFIX: remove limit of 8 parallel executions BUGFIX: Changed Webservice in SCTM 2010 needs to extands the error handling if session is lost Options to execute a execution definition with a build number generated from a hudson job Tested with SCTM 2010
1.2	BUGFIX: ThreadPool is now transient add Option to ignore Setup/Cleanup TestDefinitions in the TestResults
1.1.1	BUGFIX: Collecting results fails since version 1.1, due to an serialization error
1.1	add optional parameter for a start delay. Starts the second and following executions with an delay to prevent resource problems on virtual machines. add option to ignore errors from SCTM, but log it add option to activate/deactivate result collection some internal refactorings to prepare code for future improvements
1.0	first complete major release; You are able to trigger one or more execution definitions and record there results to visualize it in the test results graph/table. Supported Test Manager: > 2008 R2 Tested with Test Manager 2008 R2 SP1
0.6	several improvements in collecting results, translation, tests
0.5	fix problems with dependencies to SAX (use sun implementation as a quick fix)
0.4	several improvements with test execution and result writing
0.3	First release candidate (after some problems with wagon-svn)
0.1	First try Execution of multiple Execution Definitions enabled.

Known Problems / TODOs

Please feel free to enter any issue to JIRA and set the component to 'sctmexecutor'.

• HUDSON-6619 NPE after saving a simple configuration (workaround: set an option for the build number usage in the advanced configuration)
• Use a new result view that shows a matrix of configurations and testcases/-suites running in these configurations
• new result parser (maybe using xUnit plugin)
• encoding for german translation
• documentation for build number usage options
• use hudson build number for SCTM execution (if build number does not exists create it)
• add option for not recording/waiting for test results (only trigger execution and finish)
• If more than one execution definition is started the results are lost.
• Some localization issues
• Find a way to handle very long SCTM executions
• Usability; Add some configuration check code to give the user an early preview about the configuration sets.

-> implemented but not included in the latest available release
-> in progress or just an idea/todo
-> done and available in the latest release