Intro to BDD – CukeUp! AU 2016

Transcript

1. @tooky http://cucumber.io/st Steve Tooke Intro to BDD
2. project noun |ˈprɒdʒɛkt| 1 an individual or collaborative enterprise that is carefully planned to achieve a particular aim: a research project | a project to build a new power station. • a piece of research work undertaken by a school or college student: a history project. • a proposed or planned undertaking: the novel undermines its own stated project of telling a story. 2 (also housing project) North American a government-subsidized housing development with relatively low rents: her family still lives in the projects. Apple macOs Dictionary
3. project noun |ˈprɒdʒɛkt| 1 an individual or collaborative enterprise that is carefully planned to achieve a particular aim: a research project | a project to build a new power station. • a piece of research work undertaken by a school or college student: a history project. • a proposed or planned undertaking: the novel undermines its own stated project of telling a story. 2 (also housing project) North American a government-subsidized housing development with relatively low rents: her family still lives in the projects. Apple macOs Dictionary
4. project noun |ˈprɒdʒɛkt| 1 an individual or collaborative enterprise that is carefully planned to achieve a particular aim: a research project | a project to build a new power station. • a piece of research work undertaken by a school or college student: a history project. • a proposed or planned undertaking: the novel undermines its own stated project of telling a story. 2 (also housing project) North American a government-subsidized housing development with relatively low rents: her family still lives in the projects. Apple macOs Dictionary
5. “A software project is a place where different cultures come together. Some people face towards the business and its concerns; other people face toward the computer and its demands” Brian Marick
6. How Projects Really Work (version 1.5) Create your own cartoon at www.projectcartoon.com How the customer explained it How the project leader understood it How the analyst designed it How the programmer wrote it What the beta testers received How the business consultant described it How the project was documented What operations installed How the customer was billed How it was supported What marketing advertised What the customer really needed www.projectcartoon.com
7. Business needs are not well understood by the people who want the software
8. Business needs are not well understood by the people who want the software
9. Business needs are not well understood by the people who will deliver the software
10. Business needs are not well understood by the people who will deliver the software
11. Business needs are not well understood by the people who will deliver the software
12. The software is low quality with lots of bugs
13. The cost of change over time increases rapidly Cost of Change Time
14. Successful Projects
15. Successful Projects Shared understanding
16. Successful Projects Shared understanding Know when you are done
17. Successful Projects Shared understanding Know when you are done Know what to do next
18. Successful Projects Shared understanding Know when you are done Know what to do next The codebase supports the inevitable changes as the project evolves
19. Successful Projects Shared understanding Know when you are done Know what to do next The codebase supports the inevitable changes as the project evolves Know quickly when new changes break existing behaviour
20. “BDD practitioners explore, discover, define and then drive-out the desired behaviour of software using conversations, concrete examples and automated tests” Matt Wynne
21. desired behaviour of software
22. desired behaviour of software
23. desired behaviour of software
24. conversations can you give me an example? what would happen if…? is there something else that needs to happen…? is that always true? have you thought about?
25. desired behaviour
26. desired behaviour concrete examples illustrate
27. desired behaviour concrete examples illustrate automated tests becom e
28. desired behaviour concrete examples illustrate automated tests becom e verify
29. desired behaviour concrete examples illustrate automated tests becom e verify Shared understanding
30. http://www.growing-object-oriented-software.com/figures.html From Growing Object-Oriented Software by Nat Pryce and Steve Freeman
31. http://www.growing-object-oriented-software.com/figures.html From Growing Object-Oriented Software by Nat Pryce and Steve Freeman Know when you are done
32. http://www.growing-object-oriented-software.com/figures.html From Growing Object-Oriented Software by Nat Pryce and Steve Freeman Know when you are done Know what to do next
33. Improve the internal structure of the code without changing its externally observable behaviour Refactor
34. Improve the internal structure of the code without changing its externally observable behaviour Refactor The codebase supports the inevitable changes as the project evolves
42. Know quickly when new changes break existing behaviour
43. Behaviour Driven Design
44. Steve Tooke 
 Twitter: @tooky Blog: tooky.co.uk E-mail: tooky@cucumber.io