Deprecated Since 9.0.0, please use xUnit Uploader Plugin instead.

codeBeamer xUnit Importer Plugin

• This plugin publishes xUnit Results into codeBeamer Test-Cases, Test-Sets and Test-Runs thus results and coverage of automized tests are available for Work Items (such as Requirements, Tasks, User-Stories etc.).
• The plugin is available through the jenkins plugin manager.

Creating an example Maven Jenkins Job

• Create a new Maven project

• Add a name and repository URL: https://github.com/jenkinsci/jacoco-plugin.git

• Add install jacoco:report to Goals and options

• click on Add post-build action and select codeBeamer xUnit Results Publisher Plugin.
• Enter the codeBeamer specific data

• Click on Save button and on Build Now link on the next screen.

Configuration

This plugin is a post build plugin meaning that it can be used in the "Post-build Actions" section.

The plugin needs mandatory parameters to function:

• URI: URI of an existing codeBeamer server either a local or hosted instance (example: https://codebeamer.com/cb/)
• username: username of the account with sufficient privileges to update the wiki page
• password: password of the account with sufficient privileges to update the wiki page
• Tracker Configuration Item ID: We can set a specific tracker for Tracker configurations. Generated Test Runs are going to refere to the given Tracker configuration
• Test Set Tracker ID: Generated Test Sets are going to take place in the specified tracker
• Test Case Tracker ID: Generated Test Cases based on the unit test packages are going to take place in the given tracker (optionally as children of the given predefined Test Case)
• Test Run Tracker ID: Generated Test Runs are going to take place in the given Test Run tracker. Every Test Run will be filled in with the give user and Jenkins Test Result data. If the test is failed the Test Run Result will also be failed.

Optional parameters

• Test Case Top Node ID: The ID of a tracker Item on a Test Case Tracker. If provided then the created Test Cases will have this node/folder as parent. Warning this setting will override Test Case Tracker ID.
• Bug Tracker ID: This is the Tracker where Bug reports will be submitted.
• Number of Bugs to report: If the Bug Tracker is also provided limits the number of bugs submitted to codeBeamer, default value 10.
• Requirement Tracker ID: This is the Tracker where Jenkins will submit Requirements.
• Requirement Top Node ID: The ID of a tracker Item on a Requirement tracker. If provided then the created Requirements will have this node/folder as parent. Warning this setting will override Requirement Tracker ID.
• Requirement Depth: If the Requirement Tracker ID is also provided limits the depth of the requirements created.
• Include Packages: You can include one or multiple packages (separator ; ) in the upload to codeBeamer. If not provided all packages are included by default. example: com.exaple;com.otherpackage
• Exclude Packages: You can exclude one or multiple test packages (separator ; ) from the upload to codeBeamer. example: com.exaple;com.otherpackage
• Truncate Package Tree: If provided both the uploaded Tests into both the Test Cases and Requirements tracker will have a truncated tree. example: the test has a structure of com.example.package.mytests the provided value is com.example the test to upload will have a package of package.mytests.

Test Run Example

The screenshot below shows an example of a Test Run instance published by the plugin: