My session on BDD at Agile Conference China 2012

1. BEHAVIOR
DRIVEN
DEVELOPMENT
Adding value with less work

2. GIUSEPPE DE SIMONE
› Agile/Lean coach, Trainer, Lecturer, Change catalyst,
Visionary, Scout leader. Passionate to help people grow.
› mail: giuseppe.desimone@ericsson.com
› Twitter: @giusdesimone
› web:
– Agile Coaching Network
– http://it.linkedin.com/in/giuseppedesimone
Page 2

3. MANIFESTO OF SW
CRAFTSMANSHIP
Page 3

4. nt
m ou
h ea
g t ial.
izin ent
xim ess
m a - is
of e -
art on
th e o t d
t y -- rk n
lici f wo
S imp o
DELIVER AS FAST AS
POSSIBLE
Page 4 Learn as fast as possible

5. BDD IN A NUTSHELL
Page 5

6. BDD IS NOT ABOUT TESTING...
…IT’S ABOUT DEVELOPMENT!
Page 6

7. USER STORY
As a Returning Customer I want the
system to remember my details so I
can purchase goods more quickly.
Acceptance criteria:
Scenario: Review Details Before Purchase
Given I’m on the Amazon website
And I’m logged in as a returning customer
When I click the “1-Click” button
Then I should see my order details
Page 7

8. Acceptance Criteria
Page 8
Acceptance Tests

9. Acceptance Criteria
Page 9
Acceptance Tests

10. Acceptance Criteria
Page 10
Acceptance Tests

11. Acceptance Criteria
Page 11
Acceptance Tests

12. Acceptance Criteria
Page 12
Acceptance Tests

13. Acceptance Criteria
Page 13
Acceptance Tests

14. Acceptance Criteria
Page 14
Acceptance Tests

15. Acceptance Criteria
Page 15
Acceptance Tests

16. Acceptance Criteria
Page 16
Acceptance Tests

17. Acceptance Criteria
Page 17
Acceptance Tests

18. Acceptance Criteria
Page 18
Acceptance Tests

19. Acceptance Criteria
Page 19
Acceptance Tests

20. Acceptance Criteria
Page 20
D
O
N
E
Acceptance Tests

21. TEST DRIVEN DEVELOPMENT
start with a failing Quickly write the refactoring
test simplest code needed
to pass the test
Repeat as needed to meet requirements
Test everything that could possibly break
Page 21

22. TESTING QUADRANTS
Business-facing
D
BD
Critique the product
Exploratory Tests
Support the team
Acceptance
Usability Tests
Tests
UAT
Q2 Q3
Q1 Q4
D
TD Unit Tests
Performance,
Security,
Component Tests
Load Tests
Technology-facing
Page 22

23. DESIGN, IMPLEMENT,
TEST ALL IN ONE...
Traditional Development
Analyze Implement Test
Deliverable
Agile Development
Deliverable
Page 23

24. Given <context>
When <action>
Then <expected result>
Page 24

25. Page 25

26. BDD INSTANT WORKSHOP
› What could be for you (your team, your context) the
benefits of using BDD?
› What do you miss to start tomorrow?
lk
ta
Page 26

27. OUR EXPERIENCE

28. Page 28

29. Page 29

30. Page 30

31. SM
ScrumMaster
…
...
PO TM
Product Owner
Development Team
Sprint Review Meeting
Page 31

32. REFLECTIONS
› BDD is NOT a tool
› Always challenge the desired behaviour
› Fast feedback is essential
› Communicate and collaborate
› Risk-first!
Page 32

33. COACHING BDD
› No special secret!
› Teaching and mentoring
› “Ha-ha” moments need to happen for lasting effects
› Grow agilists
› Stimulate curiosity and enthusiasm
– Throw questions and challenges
Page 33

34. GAMIFYING BDD
Page 34

35. USEFUL LINKS
› Cucumber site
– cukes.info
› Liz Keogh’s blog
– lizkeogh.com
› Gojko Adzic web site
– gojko.net
Page 35

36. Page 36