...
This tutorial explains how to leverage BDD in Jira Cloud with Cucumber for Jira and Zephyr for Jira.
Create a new
...
project
...
| Table of Contents | ||
|---|---|---|
|
...
On the projects page, create a new Classic Jira project.
...
Select the Scrum template (for example, ) and enter the name of this the project and then click on Create.
...
Project configuration
To use Zephyr for Jira and Cucumber for Jira you need to add :
Add the Test type to your project
...
Enable BDD
...
on the project settings.
Add the Test issue type to your project
To be able to use Zephyr, you need to add the Test type to this project. To do that, go
Go to Project settings:
...
Select the Issue types menu:
...
Drag and drop the Test issue type to Issue Types for Current Scheme:
...
Don’t forget to save. That’s it!
...
Enable BDD
...
on the project
In Project Settings, select Cucumber for Jira to display the Cucumber for Jira settings, and active enable the both options. The first option allows option.
It allows us to enable the Cucumber for Jira features and the second option allows to activate Zephyr dedicated BDD featurein your project.
...
That’s it! Your project is ready for BDD ready.
In the next section, we you will add your first features in your project.
...
Feature design
In this section, we will see how to design your features and your scenarios.
Back Go back to the project, and select Zephyr in from the menu.
...
Feature issue creation
...
The Create issue box appears. By default, a Feature issue is a story with the BDD_Feature label feature.
Put the name of the feature in the Summary field, and the description of the feature in the Description field.
...
Click on the Create button
You can create many feature issues in the same manner.
Once the feature issues are issue is created, go navigate to the first oneit.
On this the issue page, the Test detail Details panel allows will allow you to create many scenario issuesyour scenarios.
...
To create a scenario, just put its enter a name in the Enter name of the Scenario field and click on the Create button.
...
This creates will create a scenario test issue.
You can add here many scenarios or a background.
...
To go the a scenario test page, just click on its key to navigate to it. The scenario test issue page allows to add adding the content in Gherkin format in the Test Details panel.
...
You can use scenario tests like other Zephyr tests. So you can create a test cycle and add them into to it.
In the project menu, select Zephyr and Cycle Summary and click on the Create New Test Cycle button to create a new test cycle.
...
Add the name of the test cycle to create it. In this test cycle, click on the Add Tests button to add your tests in this test cycle.
...
Select the tests you need and validateindividually or by applying a filter and click add.
...
That’s it, your BDD scenarios are added to a test cycle. If you need, yo you can update the status of these scenarios directly in this interface:
...
To share the features you designed in Jira with the developers of your team, you can download the feature files directly from the test cycle.
...
You will obtain a zip file containing all the feature files of this test cycle. Unzip this file and add, commit and push the features files in the Cucumber project of your Git repository.
| Info |
|---|
If you don’t have yet a Cucumber project in your repository, begin by creating an empty Cucumber project according to your langagelanguage. |
Create the living documentation
| Info |
|---|
...
allows you to synchronize Jira with your |
...
Git repository |
...
. |
Click on the Living Documentation menu.
...
Select your Git provider, your repository, the right branch and create click on Create the living documentation.
...
You can configure your continuous integration server so that it can push test results directly into the living documentation. Here are the steps: automate test results push.
...
Traceability matrix
To see traceability, this is critical because it allows to quickly dive into the traceability of your features through testing and defects. Here I can see Feature1 is being validated by two tests and has multiple failures along with multiple defects. This is a great report because it allows project managers or those involved in the project to quickly see what is the status of the testing activities for this particular feature
| Filter by label (Content by label) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|