Documenting BDD Scenario's

Clare Butcher
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 7, 2020

Hi All, 

I'm a Test Manager working on a project that is following BDD. Currently we document our BDD scenario's in Description field in Jira however this is making it difficult to report on so I was just wondering if you have any advice on how we could structure it better so that I know how many scenario's we have and how many have been tested. 

Also does anyone know the best way to tag a story as functional? We have over 1000 user stories however not all are functional so need to find a way of tagging.

 

Thanks in advance 

3 answers

0 votes
Dmytro Stasyuk October 17, 2024

If anyone is looking to solve this type of problem "BDD for Jira" app could be useful to you. Its built-in Gherkin Editor offers IDE like features for working with the Feature files and it has the capability to search inside Feature files using JQL.

You can access a Live Demo here

Disclosure - I'm part of the vendor team behind this tool. 

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 17, 2024

Hi @Dmytro Stasyuk 

What is your relationship to the vendor of the product you are recommending?

As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see:

Atlassian Community online guidelines | Marketplace + Solution Partners | App Central

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Atlassian-Community-online-guidelines-for-Marketplace-and/ba-p/689723

Kind regards,
Bill

Dmytro Stasyuk October 17, 2024

Hi @Bill Sheboy ,

Thank you for pointing this out, I'll review the guidelines more thoroughly and post with disclosure in the future. I've updated my answer above now.

Best regards,

Dmytro 

Like Bill Sheboy likes this
0 votes
Nick Iles _AssertThat_
Contributor
December 7, 2020

Hi @Clare Butcher 

Writing BDD scenarios in description field is where we started a few years ago.  Since then we developed the AssertThat plugin for hosting all your BDD scenarios. 

The plugin allows you to have a central place to manage your features and scenarios, and also link / view them against each of your user stories.  It also has the reporting and traceability functionality you have eluded to in your message.

If you would like a demo then please get in contact 

Many Thanks

Nick

support@assertthat.com

AssertThat Marketplace Vendor

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 7, 2020

Hi @Clare Butcher 

How you capture your Behavior Driven Development (BDD) scenarios may depend upon how your team is defining the scenarios.  If they are all stand-alone, customer facing, you could split each into a task/story.  If not, please consider one of the testing addon tools to better manage the scenarios and the traceability you are asking about.

Regarding tagging issues as functional, have you considered using Labels, Components, or a custom field to do so?  I would suggest starting with Labels to help you learn if there is finer granularity than just "functional" that you want to manage.

Best regards,

Bill

Suggest an answer

Log in or Sign up to answer