Many teams in their development process tend to focus on answering the question “how” instead of “why”. This leads to many misunderstandings which in turn decrease productivity and pleasure of working.
In my presentation I waned to introduce Behavior Driven Development which is one of the ways to improve communication within a team. I will share my knowledge on how to start with BDD in your company and say a couple of words about things like StoryBDD, SpecBDD and living documentation. Taking my team as a use case I will also speak about how BDD helped us in understanding each other and making software that matters.
14. Feature: buying subscription
scenario
Workshops
BUILDING BEHAVIOR DRIVEN TEAMS
In order to use more minutes then on free subscription
As a customer
I need to be able to buy a subscription
Scenario: Successfully getting charged for subscription
Given I am a registered user
When I buy a subscription
Then I should be charged
15. Refine
EXAMPLES
BUILDING BEHAVIOR DRIVEN TEAMS
Given I am a registered user
When I buy a subscription
Then I should be charged
Given user “john@doe.com” exists
And “gold” subscription for “23.99” exists
When user “john@doe.com” buys “gold” subscription
Then user “john@doe.com” should be charged for “23.99”
17. SPECIFICATIONS
ARE NOT SCRIPTS
BUILDING BEHAVIOR DRIVEN TEAMS
Given user “John Doe” is registered
When I log in as “John Doe”
And I go to the contacts page
And I remove contact “Jane Doe”
Then I should have “0” contacts
And I should see “contact removed”