Introduces some agile concepts about work breakdown and vertical slicing. Spends some time talking about Acceptance Test Driven Design.

1. An Introduction to
Behavior Driven Design
Shawn Wallace
National Service Offering Lead
Application Development and Application Lifecycle Management
Senior Architect
Centric Consulting

2. I’m Shawn

3. I’m Shawn
Favorite Movie

4. I’m Shawn
Favorite Movie
My dog

5. I’m Shawn
Favorite Movie
My dog
My Son

6. I’m Shawn
Favorite Movie
My dog
My Son
My Daughter

7. I’m Shawn
Favorite Movie
My dog
My Son
My Daughter
My Family

8. I’m Shawn
Favorite Movie
My dog
My Son
My Daughter
My Family
I live here

9. I’m Shawn
Favorite Movie
My dog
My Son
My Daughter
My Family
I live here
I a Marine Vet

10. I’m Shawn
Favorite Movie
My dog
My Son
My Daughter
My Family
I live here
I a Marine Vet
My Favorite Team

11. I’m Shawn
Favorite Movie
My dog
My Son
My Daughter
My Family
I live here
I a Marine Vet
My Favorite Team
Where I work

12. I’m not a BA

13. A programmer is going out for a stroll one
evening. His wife asks him to swing by the
store and pick up a gallon of milk, and if they
had eggs, to get a dozen. He returned with
twelve gallons of milk and said "They had
eggs."
4

14. 5

15. Our existences are
about precise
communication

16. The Problem with Agility

18. We are trying to “productize”
our approaches...again.

19. We are trying to “productize”
our approaches...again.

20. Fundamentally agile
is about
approaching the
work in a different
way.
11

21. 12

22. We need thinking
business analysts

23. 14

24. 15

25. We’re not building a
house...

26. We’re cleaning the
house...

27. It’s NOT easy
• It is MUCH easier to slice up a backlog
horizontally
• Developers want to work horizontally
(efficiency argument)
http://simpleprogrammer.com/2011/11/21/understanding-the-vertical-slice/

28. http://www.deltamatrix.com/2012-04-17-04-37-50/horizontal-and-vertical-user-stories-slicing-the-cake

29. Why vertical slices?
It is about delivering working functionality as
soon as possible.
Feedback.

30. http://www.deltamatrix.com/2012-04-17-04-37-50/horizontal-and-vertical-user-stories-slicing-the-cake

31. Behavior Driven
Development

32. Why Behavior Driven Design
• Work is done from the perspective of the
user
• Can slice vertically but narrowly
• Tests behavior of the system
• Executable requirements
• Need to move as fast
as business
• Appropriate feedback loop
• Manual regression is
EXPENSIVE

33. Acceptance Tests vs. Unit and
Integration Tests

34. Acceptance Tests vs. Unit and
Integration Tests
• Unit Tests confirm that you built it
right (INSIDE OUT)
• Acceptance Tests confirm that you
build the right thing (OUTSIDE IN)
25

35. Benefits
• Implementing changes more efficiently
• Quick feedback
• Higher product quality
• Less rework
• Better work alignment to priority
(not just for agile teams)
26

36. • Describes how software should behave in plain text
• Gherkin
– Usable in many different human languages
– Features can be written and understood by both non/
technical project members
• Not a replacement for unit testing; it’s not a low
level testing/spec framework
• Easy to execute in Continuous Integration
environment (except MS TFS)

37. Technology Stack
• Cucumber - Domain Specification
• Ruby, JRuby or .NET - map cukes to
application
• UI testing framework - Watir, Watin,
Selenium, Capybara (headless),
anything that supports WebDriver
• Open source
• STRONG community support
28

38. Features

39. Who’s Using the System
Features

40. Who’s Using the System
What are they doing?
Features

41. Who’s Using the System
What are they doing?
Why do they care?
Features

42. Scenarios
• Features are defined by one or more
scenarios
• Sequence of steps thru the feature that
exercises on path
• Use BDD style – given-when-then
Scenario: <description>
<step 1>
…

43. Scenarios

44. • Given - Sets up preconditions, or context, for the
scenario
Scenarios

45. • Given - Sets up preconditions, or context, for the
scenario
• When - The action, or behavior, that we’re focused on
Scenarios

46. • Given - Sets up preconditions, or context, for the
scenario
• When - The action, or behavior, that we’re focused on
• Then - Checks post-conditions and verifies that the
right thing happened in the When stage
Scenarios

47. Demonstration
32

48. Q&A
For more information...
• This Presentation on GitHub - https://github.com/shawnewallace/intro-to-atdd.git
• cukes.info
• Gojko Adzic
– cuke4ninja.com
– Specification by Example
• https://github.com/aslakhellesoy/cucumber/wiki
• http://groups.google.com/group/cukes
• http://www.cheezyworld.com
• The Cucumber Book, Matt Wayne, Aslak Hellesøy: http://pragprog.com/book/
hwcuc/the-cucumber-book
• The Rspec Book, David Chelimsky: http://www.pragprog.com/titles/achbd/the-
rspec-book
• http://simpleprogrammer.com/2011/11/21/understanding-the-vertical-
slice/
• http://www.deltamatrix.com/2012-04-17-04-37-50/horizontal-and-
vertical-user-stories-slicing-the-cake

49. Shawn Wallace
Work: shawn.wallace@centricconsulting.com
Personal: shawn@the-wallaces.net
Twitter: @ShawnWallace
Blog: blog.shawnewallace.com
http://www.about.me/shawnwallace
Shirt size: XXL
Shoe Size: 11.5