Jenkins : Zephyr Enterprise Test Management Plugin

Creates test cases and publishes test results in Zephyr Enterprise for JUnit test cases

Plugin Information

View Zephyr Enterprise Test Management on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

About the Plugin

Zephyr Enterprise Test Management Plugin for Jenkins integrates Jenkins and Zephyr Enterprise Edition / Zephyr Community Edition. This plugin creates test cases and publishes test results in Zephyr Enterprise for JUnit test cases in Jenkins. It supports publishing maven surefire format test results (JUnit and TestNG).
This guide will cover how to create and execute test cases automatically in Zephyr Enterprise using this plugin; this includes

  1. Downloading and installing the plugin
  2. Adding Zephyr Severs in the Jenkins global settings.
  3. Configuring a standard Jenkins Job.
  4. Configuring Zephyr Enterprise Test Management Plugin as a post-build action.
  5. Triggering the job and publishing results in Zephyr


  1. Zephyr Enterprise 4.7.X, 4.8.X, 5.0.X, 6.1.X, 6.2.X
  2. Jenkins installation (Upto version 2.89.4)

Adding Zephyr Servers in Jenkins global settings

After installation configure Jenkins global settings to establish connection with Zephyr Server(s). Follow the below steps

  • Launch Jenkins and access via a web browser.
  • Click on "Manage Jenkins" from the Menu as illustrated in the below screenshot.

  • Click on "Configure System".

  • Locate the section "Zephyr Server Configuration" and click "Add". You can add more than one Zephyr Server by clicking on "Add" button.

  • Enter Zephyr Server URL and user credentials. Note that the user credentials must be that of Zephyr "Test Manager" or "Test Lead". Click on "Test Configuration" to validate connection to Zephyr Server.

  • Click on "Save" button to save the configuration changes.

Configuring a standard Jenkins job

A job in Jenkins defines a sequence of tasks for Jenkins to perform. When a job is triggered, Jenkins looks for an Ant script or Maven build file and runs it. It also provides options to define post-build tasks. Follow the example below to configure a standard job and add a post build action:

1. Create a new Jenkins job by clicking the "New Item" link found on the menu.

2. Give a name for your job, check the box "Freestyle project" and click on "OK" button.

3. To configure the job you just created, click the <job name> on the Jenkins home page.

4. Click the "Configure" link.

5. Choose "Subversion" option in the "Source Code Management" section.

6. Enter the subversion URL where the target project resides and press Tab.

Note: User credentials needs to be setup to access SVN server. Click on "enter credential" link to set it up if you see below error.

7. To add a build step, locate the "Build' section and select "Invoke top-level maven targets" from the "Add build step" dropdown.

8. Select "clean package" as your Goals.

9. The plugin requires JUnit test result. Locate the "Post-build Actions" section and select "Publish JUnit test result report" from "Add post-build Actions" dropdown.

10. Enter the path to the test report. In the example below the location is "Proj1\target\surefire-reports/*.xml" where Proj1 is the target project.

Configuring Zephyr Enterprise Test Management plugin as a post-build action

In order to publish results in Zephyr, define another post-build action.

1. Select "Publish test result to Zephyr Enterprise" from "Add post-build Actions" dropdown.

2. Configure Zephyr plugin job.

      1. Select the Zephyr URL from the dropdown. (Servers configured in the Jenkins global configuration are available here to select). This automatically pulls in Zephyr projects, releases and cycles.
      2. Select the Project Name from the dropdown. This re-populates the releases.
      3. Select the Release from the dropdown. Selecting a release fetches all its cycles.
      4. Select either an existing Cycle from the dropdown or create a new cycle.
      5. For existing Cycle the default Cycle Duration will be that of existing cycle in Zephyr and Cycle Name Prefix will be of the format "Automation_<Date><Time>" stamp.
      6. For new cycle you have option to select Cycle Duration from the dropdown and to edit default cycle prefix name "Automation". In the absence of a cycle prefix name "Automation" is used for new cycles.
      7. To create a package structure while creating and organizing the test cases, check the box "Create Package Structure".
      8. Click "Save".

Triggering the job and publishing results in Zephyr

To trigger a job manually, click "Build Now" link on the menu. This builds the project and publishes the JUnit result.

In Zephyr Enterprise Jenkins creates a phase named "Automation" along with package structure of the JUnit test cases found in the project.

Finally, Jenkins assigns this phase to the selected cycle and executes all the tests in Zephyr.


This plugin is open source. It follows the Apache License version 2.0 (<>). It means:
It allows you to:

  • freely download and use this software, in whole or in part, for personal, company internal, or commercial purposes;
  • use this software in packages or distributions that you create.

It forbids you to:

  • redistribute any piece of our originated software without proper attribution;
  • use any marks owned by us in any way that might state or imply that we endorse your distribution;
  • Use any marks owned by us in any way that might state or imply that you created this software in question.

It requires you to:

  • include a copy of the license in any redistribution you may make that includes this software;
  • provide clear attribution to us, for any distributions that include this software

It does not require you to:

  • include the source of this software itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it;
  • Submit changes that you make to the software back to this software (though such feedback is encouraged).

See License FAQ <> for more details.