Klaros-Testmanagement Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID klaros-testmanagement Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.5.1 (archives)
May 31, 2015
1.388
Source Code
Issue Tracking
Maintainer(s)
Subversion
Open Issues
Torsten Stolpmann (id: stolp)
Usage Installations 2014-Jul 28
2014-Aug 27
2014-Sep 26
2014-Oct 29
2014-Nov 26
2014-Dec 27
2015-Jan 23
2015-Feb 26
2015-Mar 28
2015-Apr 26
2015-May 25
2015-Jun 24

Integrates Jenkins with Klaros-Testmanagement by publishing the test results of a build to the Klaros-Testmanagement application.
The test results will be stored in the Klaros-Testmanagement database for further evaluation and reporting purposes.

How to install this plugin

Using the interface

The simplest way is by going to your installation's management screen and clicking there "Manage Plugins". (http://yourhost/jenkins/pluginManager). The web interface will then download *.hpi files from here, you will just need to restart your Jenkins instance to pick up the changes.

Manual Installation

Download Site

Save the downloaded *.hpi file into the $JENKINS_HOME/plugins directory. You will need then to restart Jenkins (many containers let you do this without restarting the container).

Configuration

In the Jenkins system configuration you are able to specify one or more Klaros-Testmanagement installations which you may publish test results to. The only configuration option is the URL of the application.

In the Jenkins project configuration (under Post-build Actions) you can define the following parameters:

  • Username: Specify this if Klaros is configured to require authentication for test results imports
  • Password: Specify this if Klaros is configured to require authentication for test results imports
  • Project ID: The ID of the Klaros Project to store to
  • Iteration ID: The optional ID of the Klaros project iteration to which the test results should belong.
  • Test Environment ID: The ID of the Klaros test environment (OS etc.)
  • System Under Test ID: The ID of the Klaros system under test (Software version etc.)
  • Create a test suite per result file: If enabled, there will be a test suite and corresponding
    test suite result created in Klaros for each result file imported
  • Test Report files: Multiple Ant FileSet includes to the result files to be published

Notes

If the exported test cases are not yet present in Klaros-Testmanagement they are created automatically for the given project.

This plugin requires Klaros-Testmanagement version 2.2.1 or later. User authentication is supported starting from Klaros version 2.6.

The only currently supported format for test results is JUnit XML.

Version History

Version 1.5.1 (May 31, 2015)

  • Add proper migration of test result path settings for existing projects (JENKINS-28659)

Version 1.5 (May 30, 2015)

  • Add support for iteration assignment of imported test runs (JENKINS-28296)
  • Support the creation of test suites on test result import (JENKINS-27596)
  • Do not try to export test results for canceled or broken builds (JENKINS-27593)
  • Support multiple test result set specifications for uploading (JENKINS-27592)
  • Whitespace at the end of input fields leads to bogus file upload (JENKINS-15744)

Version 1.4 (Apr 15, 2011)

  • No longer tries to authenticate with an empty username when no name was specified
  • Remote Slave execution finally works

Version 1.3 (Apr 08, 2011)

  • Fixes a problem when executed on a slave node

Version 1.2 (Feb 14, 2011)

  • Update link in help

Version 1.1 (Mar 19, 2010)

  • Support for the user authentication introduced in version 2.6

Version 1.0 (Oct 6, 2009)

  • Initial Release

Labels

Edit
plugin-external plugin-external Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.