Bdd intro for Microsoft, 29 Nov 2012

Behavior Driven Development

by Aliaksandr Ikhelis, 2012
Friday, 30 November 12

Communication Issue
They are They do not know
slow!.. what they need!..


Building communication bridge



BDD is an evolution in the thinking
behind TDD & ATDP



BDD is an evolution in the thinking
behind TDD & ATDP

Focus on delivery of the
prioritized and verifiable business value
by providing a common vocabulary


Practices


Practices
• Establish goals


Practices
• Establish goals

• Draw out features using feature injection


Practices
• Establish goals


• Involve stakeholders in the implementation
process through outside-in software
development


Practices
• Establish goals


development

• Use examples to describe behavior


Practices
• Establish goals


development

• Use examples to describe behavior

• Automate examples to provide quick
feedback and regression testing


What BDD adds to TDD


• Test what an object does instead
of what it is


of what it is

• Design top-down, which is essential
for YAGNI – You Aren't Gonna Need It


of what it is

• Design top-down, which is essential
for YAGNI – You Aren't Gonna Need It

• Define acceptance criteria with the
customer and specify it in the
automated way, serve the living spec


The BDD “Outside-In” cycle


Gherkin: feature title and narrative
Feature: Adding movies to the queue


Describing Features with Cucumber


Describing Features with Cucumber
Cucumber is a BDD tool that reads plain
text descriptions of application features with
example scenarios, which can be converted
into automation. The text is written in a
business readable domain language,
known as Gherkin.


Describing code with RSpec


RSpec is a BDD framework, which is
used to write executable examples of
the expected behaviour of a small bit
of code in a controlled context.


RSpec is a BDD framework, which is
used to write executable examples of
the expected behaviour of a small bit
of code in a controlled context.

Code example: Output:


Example: story card


Example: process ﬂow


Testing quadrands


Get the testing pyramid (un)ﬁt
BEFORE AFTER


Communications in the business org



1. Translate business goals into prioritized list of features



2. Trace required behavior within the team - drive design by
behavior, build transparency, trust and confidence.



2. Trace required behavior within the team - drive design by
behavior, build transparency, trust and confidence.

3. Clarify business value and desired software behavior -
ask “5 Why”, provide feedback, if application logic appears
overcomplicated.


Speaking the same language =
building together

As an awesome team
We want to build such a great product
So that everyone loves it

Given the investment of 22M of bricks
When you place all the bricks properly
Then the Microsoft Tower of Babel
is visible to all people across the Globe


Recommended reading

by Aliaksandr Ikhelis, 2012

Bdd intro for Microsoft, 29 Nov 2012

Recommended

Recommended

More Related Content

Similar to Bdd intro for Microsoft, 29 Nov 2012

Similar to Bdd intro for Microsoft, 29 Nov 2012 (18)

Recently uploaded

Recently uploaded (20)

Bdd intro for Microsoft, 29 Nov 2012