Behavior Driven Development (BDD) is an evolution of test-driven development (TDD) that focuses on delivering business value through automated examples. It establishes goals, draws out features, and involves stakeholders to provide a common language. BDD tools like Cucumber use a business-readable language to describe features in plain text scenarios that can be converted to automated tests. These tests define acceptance criteria and serve as living documentation.

1. Behavior Driven Development
by Aliaksandr Ikhelis, 2013 @Expedia.com
Sunday, 10 March 13

2. Agenda
• BDD
• Development workflow
• Testing quadrants (types of tests)
• Testing Pyramid
• Stubbing in Functional Tests
• Continuous Integration
Sunday, 10 March 13

3. Communication Issue
They are They do not know
slow!.. what they need!..
Sunday, 10 March 13

4. Communication Issue
They are They do not know
slow!.. what they need!..
Sunday, 10 March 13

5. Building communication bridge
Sunday, 10 March 13

6. Building communication bridge
Sunday, 10 March 13

7. Behavior Driven Development
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
Sunday, 10 March 13

8. Behavior Driven Development
Practices
Sunday, 10 March 13

9. Behavior Driven Development
Practices
• Establish goals
Sunday, 10 March 13

10. Behavior Driven Development
Practices
• Establish goals
• Draw out features using feature injection
Sunday, 10 March 13

11. Behavior Driven Development
Practices
• Establish goals
• Draw out features using feature injection
• Involve stakeholders in the implementation
process through outside-in software
development
Sunday, 10 March 13

12. Behavior Driven Development
Practices
• Establish goals
• Draw out features using feature injection
• Involve stakeholders in the implementation
process through outside-in software
development
• Use examples to describe behavior
Sunday, 10 March 13

13. Behavior Driven Development
Practices
• Establish goals
• Draw out features using feature injection
• Involve stakeholders in the implementation
process through outside-in software
development
• Use examples to describe behavior
• Automate examples to provide quick
feedback and regression testing
Sunday, 10 March 13

14. What BDD adds to TDD
Sunday, 10 March 13

15. What BDD adds to TDD
• Test what an object does instead
of what it is
Sunday, 10 March 13

16. What BDD adds to TDD
• Test what an object does instead
of what it is
• Design top-down, which is essential
for YAGNI – You Aren't Gonna Need It
Sunday, 10 March 13

17. What BDD adds to TDD
• Test what an object does instead
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
Sunday, 10 March 13

18. The BDD “Outside-In” cycle
Sunday, 10 March 13

19. The BDD “Outside-In” cycle
Sunday, 10 March 13

20. Gherkin: feature title and narrative
Feature: Adding movies to the queue
Sunday, 10 March 13

21. Gherkin: feature title and narrative
Feature: Adding movies to the queue
Sunday, 10 March 13

22. Gherkin: feature title and narrative
Feature: Adding movies to the queue
Sunday, 10 March 13

23. Gherkin: feature title and narrative
Feature: Adding movies to the queue
Sunday, 10 March 13

24. 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.
Sunday, 10 March 13

25. Cucumber step definitions
© 2012 Expedia, Inc..
Sunday, 10 March 13

26. 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.
Code example: Output:
Sunday, 10 March 13

27. Describing code with RSpec
Sunday, 10 March 13

28. Example: process flow
Sunday, 10 March 13

29. Example: story card
Sunday, 10 March 13

30. Describing code with RSpec
Sunday, 10 March 13

31. Benefits
• Communication
• Living Documentation
• Traceability
• Focus on behavior
Sunday, 10 March 13

32. Sunday, 10 March 13

33. Testing quadrands
Sunday, 10 March 13

34. Get the testing pyramid (un)fit
BEFORE AFTER
Sunday, 10 March 13

35. Stubbing services/back-ends
© 2012 Expedia, Inc..
Sunday, 10 March 13

36. Stubbing services/back-ends
• Spoofing the service (replicate behavior with mocked
backend + store data)
• Prepared canned responses
• Stubbing per browser session
© 2012 Expedia, Inc..
Sunday, 10 March 13

37. Jenkins: trunk pipeline
Stage 1 Stage 2 Stage 3
- Compile - Deploy - Stub
- Package - isWorking acceptance
- Unit tests - Stub
- PMD (static analysis) integration
© 2012 Expedia, Inc..
Sunday, 10 March 13

38. Jenkins: trunk pipeline
© 2012 Expedia, Inc..
Sunday, 10 March 13

39. CI tips
• Start small
• Keep it fast – set a limit
• Fail Fast
• Keep it green
• Everyone is responsible for Quality
• Pre-checkin Ant Targets
© 2012 Expedia, Inc..
Sunday, 10 March 13

40. 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 Solit Conference Tower
is visible to all people across the Globe
Sunday, 10 March 13

41. Do not forget to Have Fun!
Sunday, 10 March 13

42. • alex.ikhelis@gmail.com
• www.linkedin.com/in/aikhelis/
Sunday, 10 March 13

43. Recommended reading
by Aliaksandr Ikhelis, 2013
Sunday, 10 March 13