Best ways to write BDD for long stories

Question

We have recently started using BDD to write our requirements. It\'s been really helpful, it made the communication between analysts and developers a lot easier. (Combined wi

Answer 1

The best way to handle long stories, as in long scenarios, using BDD is not to do it.

What you would like to do is to focus on the busniess value that should be implemented. The rest, authorizations, warnings and similar, should be handled in the implementation of the steps and not explicit in the feature file. That the user is authorized is probably not something the business representatives really cares about. They just assume that it will be the case when performing a specific task.

You are describing using BDD as a testing tool. BDD was never meant to be a testing tool and is therefore a bad fit if it is autiomated testing that you really are looking for.

There are a few blog post you might be interested in reading that talks more about this:

• https://cucumber.io/blog/2016/07/20/where_should_you_use_bdd
• http://www.thinkcode.se/blog/2016/07/25/the-right-tool-for-the-job
• http://www.thinkcode.se/blog/2016/06/22/cucumber-antipatterns