The Behaviour-Driven Programmer
11 likes1,835 views
An introduction to Behaviour-Driven Development, the second-generation agile methodology that aims at delivering software that matters. Most of us know that BDD has something to do with tests and the way code is produced. But what is it exactly? How does it differ from Test-Driven Development? We'll discover the technical principles and practices lying at the heart of BDD, as experienced from a naive programmer perspective. But BDD is not only about writing better tests and code. It really holds higher purposes...
The Behaviour-Driven Programmer
- 1. v0 .1- al ph a !" B"#$v%&'r-Dr%v"( Pr&)r$**"r The 鍖rst steps of a Behaviour-Driven Developer
- 2. Julien Biezemans @jbpros
- 3. Who?
- 4. You happen to write code...
- 5. useless,
- 7. fragile,
- 11. BDD
- 13. BDD is a second-generation, outside- in, pull-based, multiple-stakeholder, multiple-scale, high-automation, agile methodology.
- 14. It describes a cycle of interactions with well-de鍖ned outputs, resulting in the delivery of working, tested software that matters.
- 17. Where to start?
- 18. What to test?
- 19. Behaviour
- 21. From Test to Behaviour
- 22. Most important missing behaviour today?
- 23. Business value
- 24. Story
- 25. As ... I want ... So that ...
- 26. Estimation
- 28. Scenario
- 29. Context Event Outcome
- 30. Given When Then
- 33. Stories + Scenarios = Cucumber features
- 36. Outside-in
- 40. Run feature
- 42. Missing step definition #fail
- 45. bin/app.rb
- 46. Run feature
- 48. Missing code #fail
- 50. Write spec
- 52. Run spec
- 54. Missing code #fail
- 55. Make it pass
- 58. Refactor
- 59. Repeat until the feature passes
- 61. Design
- 71. Stubs
- 80. Spec everything your step definitions need
- 95. Ruby on Rails
- 96. View Controller Model
- 97. From Programmer to Developer
- 98. program v. To provide (a machine) with a set of coded working instructions.
- 99. develop v. To bring out the capabilities of; bring to a more advanced or effective state.
- 100. Deliberate discovery
- 101. Know what you dont know
- 102. Know what you dont know you dont know
- 103. Learn the domains
- 104. Learn the tools
- 105. Know the people
- 106. Feedback
- 107. Real options
- 108. Practice
- 109. Your code is now...
- 110. useful,
- 111. delivered on time,
- 112. robust,
- 113. easily deployable,
- 114. intelligible,
- 115. maintainable,
- 116. A piece of software that matters.
- 118. Ship capabilities!