登录查看更多内容

How do you manage BDD features and scenarios in Jira across multiple projects and sprints?

由人工智能和领英社区提供技术支持

Behavior-Driven Development (BDD) is a collaborative approach to software development that focuses on defining the expected behavior of a system from the perspective of its users. BDD uses a common language, often based on the Gherkin syntax, to write features and scenarios that describe how the system should work in different situations. These features and scenarios can then be used as the basis for testing, documentation, and communication among the development team and the stakeholders.

But how do you manage BDD features and scenarios in Jira, a popular project management tool, across multiple projects and sprints? Jira is not designed specifically for BDD, but it does offer some features and plugins that can help you integrate BDD into your workflow. In this article, we will show you how to use BDD in Jira in six steps.

此文章中的业界达人

由社区从 6 条内容中精选。了解更多

1 1. Create a BDD project

The first step is to create a new project in Jira that will contain your BDD features and scenarios. You can use any project template that suits your needs, but we recommend using the Scrum or Kanban template, as they are more agile and flexible. You can also customize your project settings, such as the issue types, workflows, and screens, to fit your BDD process.

添加您的观点

2 2. Install a BDD plugin

The next step is to install a BDD plugin that will enable you to write and manage your features and scenarios in Jira. There are several options available, such as Behave Pro, Cucumber for Jira, or Xray. These plugins allow you to create and edit features and scenarios using the Gherkin syntax, link them to other issues, such as user stories or tasks, and generate reports and metrics on your test coverage and results.

添加您的观点

Nick Iles

Director at AssertThat
举报内容
BDD & Cucumber plugin's for Jira can be found on this link to Atlassian Marketplace: https://marketplace.atlassian.com/search?query=BDD%20%26%20Cucumber

已翻译

赞

3 3. Write your features and scenarios

The third step is to write your features and scenarios using the BDD plugin of your choice. You can create a new issue of type Feature or Scenario, depending on the plugin, and use the editor to write your Gherkin statements. You can also add tags, attachments, comments, and other details to your features and scenarios. You should follow the best practices of BDD, such as using clear and concise language, focusing on the user's needs and goals, and avoiding technical details.

添加您的观点

Leslie Brooks, CSPO, CSM

Specification by Example/BDD Trainer and Coach, Process Transformation Guru, Automated Testing Advisor
举报内容
Kenny is absolutely correct when he says "Focus on *what* the user/business requirements are, not on how they are achieved." Focusing on *how* they are achieved is probably the most common mistake people make when they begin using Specification by Example/BDD. The only change I would make to Kenny's example would be this: GIVEN I am a registered customer And I have a book in my shopping basket When I check out The 'Given' should talk about preconditions - things that happened in the past, or conditions that exist now. Having a book in my shopping basket is a precondition to checking out; it should be in the Given. The 'When' should be *one* action that is happening now. Having a single 'When' forces us to write requirements, not scripts.

已翻译

赞
Nick Iles

Director at AssertThat
举报内容
Although this article is specific to BDD and Jira there are typically 3 stages Discovery, Formulation and Automation. The discovery stage of BDD involves collaborative discussions to understand the desired behaviour of the software. It includes workshops, brainstorming sessions, and examples to define features and acceptance criteria. The goal is to ensure a shared understanding among the team. When you've got a shared understanding the features and scenarios the scenarios can be written up in a human-readable language, such as Gherkin syntax (Given-When-Then) into a BDD plugin.

已翻译

赞
Kenny Vo

Senior QA Engineer at Sky
(已编辑)
举报内容
Focus on *what* the user/business requirements are, not on how they are achieved. A good example of BDD using declarative language: GIVEN I am a registered customer WHEN I add a book to my shopping basket AND I check out THEN I should have successfully purchased my book This is good because if the *implementation* changes, the specification is still valid, because there are always multiple ways to solve a problem. I would give a bad example and explain it too, but this has a 750-character limit, so I've added it to the 'What else' section at the end. But to keep it short, avoid writing *how* to achieve something, otherwise known as test scripts! Check out John Ferguson Smart or Dave Farley's content on the topic! Happy testing! ??

已翻译

赞

4 4. Organize your features and scenarios

The fourth step is to organize your features and scenarios into logical groups and categories. You can use the Jira features, such as labels, components, epics, or versions, to group your features and scenarios by theme, functionality, priority, or release. You can also use the Jira boards, such as the backlog, the active sprint, or the kanban board, to manage your features and scenarios by status, assignee, or due date.

添加您的观点

Nick Iles

Director at AssertThat
举报内容
The Jira plugins will typically allow you to use feature and scenario tags. I would also suggest you develop a strategy up front for how you want to organise your scenarios using tags to minimise rework. A mind map can be quite useful to help organise your tags.

已翻译

赞

5 5. Execute your features and scenarios

The fifth step is to execute your features and scenarios using a test automation tool that supports BDD, such as Cucumber, SpecFlow, or Behat. You can use the BDD plugin to link your features and scenarios to your test scripts, run them manually or automatically, and update their status and results in Jira. You can also use the BDD plugin to sync your features and scenarios with your test automation tool, so that any changes are reflected in both sides.

添加您的观点

6 6. Review and refine your features and scenarios

The sixth and final step is to review and refine your features and scenarios based on the feedback and results of your test execution. You can use the BDD plugin to generate reports and dashboards that show you the quality and progress of your BDD features and scenarios. You can also use the Jira features, such as comments, notifications, or reviews, to collaborate with your team and stakeholders on improving your features and scenarios. You should aim to keep your features and scenarios up to date, relevant, and consistent with your user's expectations and needs.

添加您的观点

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Kenny Vo

Senior QA Engineer at Sky
举报内容
A bad example of BDD: GIVEN I'm on the Login page WHEN I enter 'Test' into the username AND I enter 'password' into the password THEN I should be logged in WHEN I click on 'Add to basket' on a book AND I click on 'Checkout' AND I enter 1234567890123456 card number AND I enter 'Test' card name AND I enter '12/23' expiry date AND I enter '123' CVV number AND I click on Submit button THEN I'm on the Payment Success page This is bad because we've locked ourselves into a test script which: 1. loses the purpose, so the team struggles to find out the actual requirements 2. is coupled to the UI which invalidates the test script for any changes. E.g. 'Add to basket' becomes '1-click purchase' 3. is too long to read for such a short user journey

已翻译

赞

Behavior-Driven Development (BDD)

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you manage BDD features and scenarios in Jira across multiple projects and sprints?

1

2

3

4

5

6

7

1 1. Create a BDD project

2 2. Install a BDD plugin

3 3. Write your features and scenarios

4 4. Organize your features and scenarios

5 5. Execute your features and scenarios

6 6. Review and refine your features and scenarios

7 Here’s what else to consider

Behavior-Driven Development (BDD)

给文章评分

感谢您的反馈

更多Behavior-Driven Development (BDD)相关文章

更多相关阅读内容