BDD for developers
As a developer you want to confidently build what the business has asked for and reduce the amount of time you spend on rework. In practising BDD, you’ll address the type of rework that is caused by poor or misinterpreted requirements.
BDD goes beyond the well-known approaches of test-driven development (TDD) and acceptance test driven development (ATDD) and focuses more on collaboration with other stakeholders in the agile team. You’ll agree requirements by having conversations to develop user stories and examples together, using language that everyone understands. You’ll be able to use your skills and knowledge to raise questions and share information during these conversations, revealing information about what we plan to build. The agreed user stories and examples will be clearly related to business outcomes, and you’ll have confidence that your time is being used in the right way.
Choosing a BDD tool
Teams often look for a tool to support their BDD practice. For best results, look for one that securely integrates with your end-to-end toolchain, i.e. seamless integration with your agile project management tool, two-way real-time sync with your git repository and support for your favoured automated testing tools. A good BDD tool will become the team’s central resource and display the single source of truth for everyone involved in the project.
Behave Pro for developers
Considering Behave Pro for Jira as your BDD tool? Here are just some of the features that you’ll like the sound of:
Effortlessly create acceptance tests for automated testing in Cucumber, SpecFlow or Behat to make sure user stories have been correctly implemented
Filter which tests to develop against using tags on scenarios, or mark scenarios as manual to prevent them from being run as part of a automated test suite
As living documentation, it’s easy to track and test as the project progresses or, for example, if a new release is required or there are regulatory changes
Integrate specification by example into your development process and get clarity on the requirements, which are written in the Given, When, Then format and easily understood by all, so you can make sure implementation is right first time
Be confident that non-technical, business-focused stakeholders can use the familiar and intuitive interface
Sync scenarios in Jira with feature files in your git repository, in both directions, keeping that single source of truth perfectly up-to-date