BDD in Action: Building Software Right and Building the Right Software

1. BDD in Action Building Software Right Building the Right Software

2. Miyamoto Musashi Japan 1584 – 1645

3. Consultant Tr a i n e r Mentor Author Speaker Coder John Ferguson Smar t

4. Consultant Tr a i n e r Mentor Author Speaker Coder John Ferguson Smar t

6. What is BDD

7. What is BDD A typical BDD workflow

8. What is BDD A typical BDD workflow What tools should I use?

9. What is BDD A typical BDD workflow What tools should I use? Effec@ve BDD automa@on

10. What is BDD A typical BDD workflow What tools should I use? Effec@ve BDD automa@on BDD Gotchas

11. So what is this BDD thing?

12. So what is this BDD thing? Using examples

13. So what is this BDD thing? Using examples a shared understanding

14. So what is this BDD thing? Using examples a shared understanding software that matters

15. So what is this BDD thing? BDD

16. So what is this BDD thing? BDD Collaboration

17. So what is this BDD thing? BDD Hunting out value Collaboration

18. So what is this BDD thing? BDD Hunting out value Collaboration Building the right software

19. So what is this BDD thing? Hunting out value Automated Acceptance BDD Criteria Collaboration Building the right software

20. So what is this BDD thing? Hunting out value Automated Acceptance BDD Criteria API and code design Collaboration Building the right software

21. So what is this BDD thing? Building the right software Hunting out value Automated Acceptance BDD Criteria API and code design Collaboration Building the software right

22. So what is this BDD thing? Building the right software Hunting out value Automated Acceptance BDD Criteria API and code design Collaboration Living Documentation Building the software right

23. The business owner tells the business analyst what he wants 1 2 The business analyst writes a requirements document 3 The developer translates the requirements into software 4 The tester translates the requirements into test cases 5 The technical writer translates the software into functional and technical documentation BDD in a nutshell A traditional development process

34. The business owner and the business analyst have a conversation about what he needs. 1 2 3 BDD in a nutshell The business analyst, the developer and the tester elaborate the requirements together. 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The scenarios guide the developer and act as automated tests They define requirements as structured, English-language format "scenarios" A BDD development process

40. The business owner and the business analyst have a conversation about what he needs. 1 2 3 BDD in a nutshell The business analyst, the developer and the tester elaborate the requirements together. 4 The tester uses these scenarios as the basis for her tests 5 The automated tests provide feedback on progress and help document the application The scenarios guide the developer and act as automated tests They define requirements as structured, English-language format "scenarios" •Specifica)ons are elaborated collabora)vely •Specifica)ons use a common language •Executable specifica)ons provide fast feedback

41. A typical BDD workflow

42. A typical BDD workflow Frequent Flyer Application Goal: Encourage travellers to fly with Flying High airlines more often by allowing them to cumulate Frequent Flyer points that they can spend on cheaper flights. Goals

43. A typical BDD workflow Frequent Flyer Application Goal: Encourage travellers to fly with Flying High airlines more often by allowing them to cumulate Frequent Flyer points that they can spend on cheaper flights. Goals Earning points from flights Capabili9es Earning points from spending with partners Viewing points earned Spending points on bookings

44. A typical BDD workflow Frequent Flyer Application Goal: Encourage travellers to fly with Flying High airlines more often by allowing them to cumulate Frequent Flyer points that they can spend on cheaper flights. Goals Earning points from flights Capabili9es Earning points from spending with partners Viewing points earned Spending points on bookings Viewing current points balance Features View points needed to achieve the next status level Calculating points needed for a given destination

46. A typical BDD workflow Calculating points needed for a given destination As a traveller I want to know how many points I need to go to a given destination So that I can plan my next trip with Flying High Airlines Feature

47. A typical BDD workflow Calculating points needed for a given destination As a traveller I want to know how many points I need to go to a given destination So that I can plan my next trip with Flying High Airlines Feature Acceptance Criteria -Need 2 points per km -Members can calculate points needed on their account home page Acceptance Criteria

48. A typical BDD workflow Calculating points needed for a given destination As a traveller I want to know how many points I need to go to a given destination So that I can plan my next trip with Flying High Airlines Feature Acceptance Criteria -Need 2 points per km -Members can calculate points needed on their account home page Acceptance Criteria

49. A typical BDD workflow Calculating points needed for a given destination As a traveller I want to know how many points I need to go to a given destination So that I can plan my next trip with Flying High Airlines Feature Acceptance Criteria -Need 2 points per km -Members can calculate points needed on their account home page Acceptance Criteria Automated Acceptance Criteria

51. A typical BDD workflow Automated Acceptance Criteria

52. A typical BDD workflow Automated Acceptance Criteria Automated Acceptance Tests

53. A typical BDD workflow Automated Acceptance Tests

54. A typical BDD workflow Automated Acceptance Tests Applica9on Code

55. A typical BDD workflow Automated Acceptance Tests Applica9on Code

56. A typical BDD workflow Automated Acceptance Tests Applica9on Code Low level specifica9ons

58. A typical BDD workflow “But what are the deliverables?

59. A typical BDD workflow “But what are the deliverables? Meaningful feedback on what requirements have (and have not) been delivered

60. An incremental approach “But what are the deliverables?

61. An incremental approach “But what are the deliverables? Descrip9on of each feature with an example of how it behaves

63. An incremental approach “But what are the deliverables? …complete with illustra9ons

65. An incremental approach “But what are the deliverables? How was each feature tested?

67. An incremental approach “But what are the deliverables? Documenta9on about what you plan to deliver in each release

69. An incremental approach “But what are the deliverables? Useful low-‐level technical documenta9on with liRle overhead

71. An incremental approach “But what are the deliverables? …and targeted automated regression tests

72. What tool should I use?

73. Collaboration before Automation

74. Collaboration before Automation “Having the conversa/on is more important than recording the conversa/on is more important than automa/ng the conversa/on” -‐ Liz Keogh

75. Know your audience

76. High-level BDD …

77. High-level BDD Reporting for non-developers as well as developers …

78. High-level BDD Reporting for non-developers as well as developers Communicate about features that business owners will understand and find meaningful …

79. High-level BDD Reporting for non-developers as well as developers Communicate about features that business owners will understand and find meaningful Higher automation and maintenance costs …

84. ` + Groovy

85. ` + Groovy

86. Living documentation! Requirements reporting! Encourages good test architecture! Good WebDriver integration! Works with other BDD tools

97. A high-‐level BDD tool should Produce business-‐readable results Fit smoothly into your build pipeline Integrate with your development infrastructure Allow developers to collaborate with testers to implement and refactor the automa9on code

99. Tips for more effec)ve BDD Test Automa)on

100. Tip #1 - Use Layers Business Rules Business Flow Page/Component interac9ons Page/Component details

105. Tip #2 - Favour non-UI tests where possible

106. Tip #3 - Know when not to automate This slide is left intentionally blank

107. Low-level BDD spock RSpec

108. Low-level BDD Technical documentation for other developers spock RSpec

109. Low-level BDD Technical documentation for other developers spock RSpec

110. Low-level BDD Technical documentation for other developers Implementation details that business owners may not be interested in spock RSpec

111. Low-level BDD Technical documentation for other developers Implementation details that business owners may not be interested in spock RSpec

112. Low-level BDD Technical documentation for other developers Implementation details that business owners may not be interested in Faster to write and easier to maintain spock RSpec

113. Low-level BDD Good naming conven9ons are the first step towards BDD

114. Low-level BDD Good naming conven9ons are the first step towards BDD

116. Low-level BDD spock RSpec Readable executable specifica9ons in Groovy

118. Low-level BDD spock RSpec Great support for data-‐driven tests

119. Low-level BDD spock RSpec Great support for data-‐driven tests

121. Low-level BDD spock RSpec Powerful and light-‐weight stubbing and mocking

125. Low-level BDD spock RSpec Makes very readable specifica9ons

126. Low-level BDD spock RSpec Makes very readable specifica9ons

127. Low-level BDD Lambda-Behave

128. Low-level BDD Lambda-Behave Low-‐level BDD library for Java 8

130. Low-level BDD Lambda-Behave Data-‐driven specifica9ons

131. Low-level BDD Lambda-Behave Data-‐driven specifica9ons

133. Low-level BDD Lambda-Behave Generated test data

134. Low-level BDD Lambda-Behave Generated test data

136. A low-‐level BDD tool should Be highly readable Be developer-‐friendly Make it easy to think in terms of specifica9ons, not tests Encourage fast feedback cycles You may need several!

137. BDD Gotchas 1 2 3 4

138. BDD Gotchas 1 2 3 An)-‐paFern 1 4 The business analyst writes the scenarios and then gives them to the other team members.

139. 1 2 3 BDD Gotchas 4

140. 1 2 3 BDD Gotchas 4 An)-‐paFern 2 The tester writes the scenarios at the end to implement an automated test suite.

141. 1 2 3 4 5 BDD Gotchas

142. 1 2 3 4 5 BDD Gotchas An)-‐paFern 3 The “Three Amigos” sessions don’t result in usable scenarios, so the developer invents them a?erwards.

143. 1 2 3 4 5 BDD Gotchas An)-‐paFern 3 The “Three Amigos” sessions don’t result in usable scenarios, so the developer invents them a?erwards.

144. 1 2 3 4 5 BDD Gotchas

145. 1 2 3 4 5 BDD Gotchas An)-‐paFern 4 The scenarios are too UI-‐centric or detail-‐focused, and neglect to express the core business value.

146. Book signings! Digital Guru bookstore Hilton Hotel, 2nd Level lobby Thursday, 12:30-‐1:00pm

147. Thank You

BDD in Action: Building Software Right and Building the Right Software

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à BDD in Action: Building Software Right and Building the Right Software

Similaire à BDD in Action: Building Software Right and Building the Right Software (20)

Plus de John Ferguson Smart Limited

Plus de John Ferguson Smart Limited (16)

Dernier

Dernier (20)

BDD in Action: Building Software Right and Building the Right Software