BDD is not about test automation, it's about testing what you don't know
- 1. BDD is not about test automation, it’s about testing what you don’t know How to drive your product development with BDD Axel Wilhelm Berle axelberle@gmail.com LinkedIn: axel-berle-5a86651/ Global Scrum Gathering Austin 2019
- 2. 45 minutes ● Share a new way to conduct your refinement sessions ● Decide later if later if you want to go BDD all the way
- 3. 45 minutes Part 1: 10 minutes - some theory of course Part 2: 30 minutes - how to actually do it! Part 3: 5 minutes - questions?
- 4. Who are you?
- 5. Axel?
- 6. Axl Rose?
- 7. Axl Rose?
- 8. Axel - Why am I here today ● I have lived in Brazil since 1996
- 9. Axel - Why am I here today ● I have lived in Brazil since 1996 ● On the agile journey since 2011
- 10. Axel - Why am I here today ● I have lived in Brazil since 1996 ● On the agile journey since 2011 ● 2015 started working as a trainer and coach
- 11. Axel - Why am I here today ● I have lived in Brazil since 1996 ● On the agile journey since 2011 ● 2015 started working as a trainer and coach ● Focussing on “agile quality”
- 18. How many points in a 5-point star? http://gojko.net/2008/08/29/how-many-points-are-there-in-a-five-point-star/
- 19. How many points in a 5-point star? There is no right answer http://gojko.net/2008/08/29/how-many-points-are-there-in-a-five-point-star/
- 20. How many points in a 5-point star? the one that the business people thought of Gojko: Bridging the communication gap
- 21. Pitfalls of BDD
- 22. Pitfalls of BDD ● Developers!
- 23. GIVEN a customer named Astrid living in Frankfurt WHEN Astrid clicks on the menu item "SKIRTS" AND she clicks on "Cute Red Mini Skirt from D&G" AND she clicks on the "put into basket" button AND she clicks on "Checkout" THEN the message "no delivery charged" should appear in the right corner
- 25. What’s wrong here? ● Badly written UI-bound test
- 26. What’s wrong here? ● Badly written UI-bound test ● Bad documentation
- 27. Not Test-First! ● When you write test AFTER developing the feature, then you are doing it wrong!
- 28. Not Test-First! ● When you write test AFTER developing the feature, then you are doing it wrong! ● it is about discovering the right number of points in our star!
- 29. BDD is an approach for exploring and designing requirements
- 30. Test First ?
- 31. How did it all start?
- 34. eXtreme Programming ● Since testing is good, let’s push it to the extreme ● Let’s test even before actually programming
- 35. public int add(int a, int b) { return null; }
- 36. @Test public void should_return_sum_of_two_numbers() { int a = 2; int b = 3; int result = add(a, b); }
- 37. @Test public void should_return_sum_of_two_numbers() { int a = 2; int b = 3; int result = add(a, b); if (result == 5) { // it works as expected! } else { // not there yet! } }
- 38. public int add(int a, int b) { return a + b; }
- 39. Testing == Illustrate the desired behavior of a component with a concrete example
- 41. automated tests
- 43. Are we building the right product?
- 46. Dan’s vision: TDD on business level
- 48. specification
- 55. So how to make it happen?
- 56. Gojko Adzic
- 57. Specification By Example Gojko Adzic
- 58. Specification By Example 1. Focus on looking for examples
- 59. Specification By Example 1. Focus on looking for examples 2. Formalize key examples
- 60. Specification By Example 1. Focus on looking for examples 2. Formalize key examples 3. Write acceptance tests based on the examples
- 62. Unholy trinity of Backlog Refinement
- 71. You are doing it wrong!
- 72. Backlog Refinement is really about Learning
- 73. William Glasser
- 81. BDD patterns: 3 Amigos
- 82. Participatory Teaching Methods ● Learning 3.0 concepts ● World-Cafe format ● Less Cross-Team Refinements
- 83. BDD Technique: Example Mapping https://cucumber.io/blog/example-mapping-introduction/
- 91. In real life
- 92. Closing
- 94. Scaled Example Mapping ● No notebooks ● No Jira ● No cellphones
- 96. Template for an Examples
- 97. Template for an Examples Context
- 98. Template for an Examples Business Action or Event
- 99. Template for an Examples Outcome
- 100. Template for an Examples Title
- 101. Let’s have some examples!
- 102. TrucoSimulator
- 103. Truco-Business Rule ● If a player wins a round, he normally gets 1 point. ● But a player can challenge the opponent by calling “Truco”. In that case the stake rises to 3 points. ● If the opponent accepts the Truco and loses, the player get the 3 points. ● If the opponent “folds”, the one calling the Truco get 1 point, without even showing his cards! ● If the opponent accepts the Truco and wins, than the opponent gets the 3 points!
- 104. Boring!
- 110. Title
- 113. Workshop at Agile Trends 2019
- 114. Workshop at Agile Trends 2019
- 115. Workshop at Agile Trends 2019
- 116. Some interesting results ● Truco != Truco ● Gato == Zap == Zorro
- 118. Formalize with Gherkin Title
- 123. Glue-Code looks like this...
- 124. Benefits of BDD refinement workshops ● Learning through real engagement ● More fun refinements ● Works with larger crowds ● Leverages diversity and perspectives ● Ownership of solution ● PO delegating work to development teams
- 125. References: