A guide to meeting user needs with Behaviour Driven Development in Jira
The pace of business is speeding up, and software release cycles are shortening.
At the same time, there's an increased expectation to deliver the best user experience possible. Behaviour Driven Development (BDD) is a great way to solve this challenge, and in this post we'll share how you can succeed with BDD in Jira.
What is Behaviour Driven Development?
Behaviour Driven Development (BDD) is a software development process which is written in a shared common language (syntax) such as English. Taking the BDD approach means there’s much less jargon to deal with, which improves communication between tech, non-tech and business stakeholders.
Using Jira to enable Behaviour Driven Development
Jira is an agile project management tool that helps improve team communication and streamline your entire testing lifecycle. When using BDD, you want maximum integration with your existing tools, so the ideal BDD setup would include integration with your current agile management tool, such as Jira. This minimises manual work and potential errors, and ensures a seamless transition from defining your requirements through to completion. The following section will explain how to do that in Jira using Test Management for Jira (TM4J).
Creating BDD test cases with TM4J
Test Management for Jira (TM4J) allows you to create a BDD test case from within your user story in Jira.
You can install and configure an automated testing tool such as Cucumber and a Continuous Integration (CI) tool such as Jenkins, to work with TM4J. You can then start using TM4J by creating BDD-Gherkin test cases. Once the test cases have been signed off, they can be exported manually which generates a feature file parsable by Cucumber or pulled automatically from a Jenkins' build task.
Automating the BDD workflow still requires the use of an external test automation tool which parses the standard BDD feature files and links it to an automated test code. You will need to implement the step definitions, which is the code that will execute according to the sequence of steps defined in the feature files.
Once the tests have been executed during the CI pipeline, the TM4J API, used, for example, by the Jenkins plugin post-build task, can send the test results back into Jira and publish them in the test cases.
Want to learn more?
This guide on Behaviour Driven Development (BDD) in Jira explains how to use BDD to streamline your testing lifecycle as part of your Agile development practices. The guide covers:
- How BDD compares to other testing methods
- How to plan and implement your BDD workflow
- How to avoid common pitfalls of BDD
Got more questions about BDD in Jira and visiting UKStar? Come by to our stand (Booth number 20), where our experts will be happy to help and offer a walkthrough of how to use BDD with Test Management For Jira (TM4J).
Start your free trial:
If you haven’t tried using Test Management for Jira yet, get a 30-day free trial here: