4. In the subsequent dialog, specify the following:

• The configuration name (an arbitrary label).

• The URL of your Zephyr Enterprise instance. Make sure to include https:// at the beginning.

• The API token previously generated in Zephyr.

Click Configure to save the information.

If the connection with Jira is not set up properly, the sections show a warning informing about the issue:

Import Jira issues as requirements and map them to test cases

Both admins and non-admin users can import requirements to Zephyr and map them to test cases. To import requirements, follow the steps described in Importing Requirements. Below is a sample list of imported requirements:

Once done, map the imported requirements to the test cases the links to which you want to have in your Jira issues. To learn how to do that, see Mapping Requirements to a Test Case. Below is a sample list of test cases with mapped requirements:

View test case traceability in Jira

After configuring the integration and mapping requirements to test cases, you can view test case traceability in your Jira instance. To do that, open your Jira issue and scroll down to the Zephyr Enterprise - Traceability section to view all the traceability details:

The table shows the name of the project, as well as the names of the release, cycle and phase the test case belongs to. The section also shows the status of the last execution of each release. Clicking the status will open the execution in Zephyr.

Create BDD scenarios

If you installed the Jira Integration: Zephyr Enterprise app into a Jira Server/Data Center instance, you can create BDD scenarios after configuring Jira integration. To do that:

1. Create a Jira issue you are going to work with.

2. Import that Jira issue as a requirement in the release folder using Jira sync or Move the Imported folder to the release folder to any existing requirement in Zephyr Enterprise.

3. If you don’t have a folder in Zephyr’s Test Repository, create one. Otherwise, you will get an error in Jira when trying to create a scenario.

4. Go back to Jira and add the BDD_Feature label in the context fields of your Jira issue.

5. The scenario editor will appear under Zephyr Enterprise – Feature Content. You can now create BDD scenarios:

   Image RemovedImage Added

If the Zephyr Enterprise section is not visible, you can open it by clicking the ellipsis button at the top and selecting Zephyr Enterprise from the dropdown:

Image Removed

Image Added

Scenario Outline (Beta Feature)

Support for Scenario Outline - Make ZBot compatible with Scenario Outlines

Scenario Outlines can be created from Feature Editor and use ZBot for their execution.
The property checkSteps=true in zbot.properties is mandatory to allow the new behavior.
More details regarding ZBot can be found in Zephyr Test Automation.

Example:

Step 1: Create a new Scenario in Feature Editor
The scenario can be named with a simple name e.g. Scenario 1 but it can be named also with parametrized name e.g. Scenario <num1>. This parameter should exist in the example table on the scenario outline.

Step 2: Add the content of the new scenario outline and save it.

Given <num1> + <num2>
Then result equals <result>

Example: 
   |num1|num2|result|
   | 1  | 2  |  3   |
   | 2  | 2  |  4   |

Step 3: On Zephyr Enterprise one test case was created per example row.

With the previous example, there would be two test cases created:

• Given 1 + 2
  Then result equals 3

• Given 2 + 2
  Then result equals 4

Step 4: The result file for ZBot should have all example results that will be matched with test case.

See Also

Jira Integration