First experiences with BDD

First-hand experiences of adopting and embracing BDD in a project.

Transcript

1. First experiences with BDD
3. New project
4. New project • Spend days thinking the perfect architecture
5. New project • Spend days thinking the perfect architecture • Write tons of documentation
6. Include a new feature into a project
7. Include a new feature into a project • Read tons of documentation
8. Include a new feature into a project • Read tons of documentation • Cross your fingers for an updated docs
9. Include a new feature into a project • Read tons of documentation • Cross your fingers for an updated docs • Feel afraid to modify the current code
10. Include a new feature into a project • Read tons of documentation • Cross your fingers for an updated docs • Feel afraid to modify the current code • Understand the current algorithms
11. During development
12. During development • Write the best algorithm ever
13. During development • Write the best algorithm ever • Objects are strongly coupled
14. During development • Write the best algorithm ever • Objects are strongly coupled • Rely on the QA to find your bugs
15. During development • Write the best algorithm ever • Objects are strongly coupled • Rely on the QA to find your bugs • Code very difficult to test
16. During development • Write the best algorithm ever • Objects are strongly coupled • Rely on the QA to find your bugs • Code very difficult to test • Automatic tests not always possible
17. During development • Write the best algorithm ever • Objects are strongly coupled • Rely on the QA to find your bugs • Code very difficult to test • Automatic tests not always possible • Write tests once you have the code
18. During development • Write the best algorithm ever • Objects are strongly coupled • Rely on the QA to find your bugs • Code very difficult to test • Automatic tests not always possible • Write tests once you have the code • Duplicated functionalities
19. Deliver the project
20. Deliver the project • Rarely deliver what it was expected
21. Deliver the project • Rarely deliver what it was expected • Perform a bunch of manual tests
22. Deliver the project • Rarely deliver what it was expected • Perform a bunch of manual tests • Expect user reports of crashes
23. Deliver the project • Rarely deliver what it was expected • Perform a bunch of manual tests • Expect user reports of crashes • Work hard to fix the crashes
24. Deliver the project • Rarely deliver what it was expected • Perform a bunch of manual tests • Expect user reports of crashes • Work hard to fix the crashes • Fix one bug and create two more
25. Let me show you an example
26. Let me show you an example
27. Let me show you an example
28. Let me show you an example
29. What is BDD?
30. What is BDD? • Tests first
31. What is BDD? • Tests first (TDD) • Examples first
32. What is BDD? • Tests first (TDD) • Examples first • They describe how your code should work
33. What is BDD? • Tests first (TDD) • Examples first • They describe how your code should work • BDD at any level
34. What is BDD? • Tests first (TDD) • Examples first • They describe how your code should work • BDD at any level • Spec, fix, refactor
35. BDD at object level (PHPSpec)
36. BDD at object level (PHPSpec)
37. BDD at object level (PHPSpec)
38. BDD at object level (PHPSpec)
39. BDD at object level (PHPSpec)
40. BDD at object level (PHPSpec)
41. BDD at object level (PHPSpec)
42. BDD at object level (PHPSpec)
43. BDD at object level (PHPSpec)
44. BDD at object level (PHPSpec)
45. BDD at object level (PHPSpec)
46. BDD at project level (Behat)
47. BDD at project level (Behat)
48. BDD at project level (Behat)
49. BDD at project level (Behat)
50. BDD at project level (Behat)
51. BDD at project level (Behat)
52. BDD at project level (Behat)
53. BDD at project level (Behat)
54. BDD at project level (Behat)
55. BDD at project level (Behat)
56. New project
57. New project • Apply BDD approach
58. New project • Apply BDD approach • Start to develop immediately
59. Include a new feature into a project
60. Include a new feature into a project • Feel confident to mess up the code
61. Include a new feature into a project • Feel confident to mess up the code • Code is self-explanatory
62. During development
63. During development • Develop just the required stuff
64. During development • Develop just the required stuff
65. During development • Develop just the required stuff • Write examples before modify your code
66. During development • Develop just the required stuff • Write examples before modify your code • Code is testable by default
67. During development • Develop just the required stuff • Write examples before modify your code • Code is testable by default • Only required edge cases are defined
68. During development • Develop just the required stuff • Write examples before modify your code • Code is testable by default • Only required edge cases are defined • Prevent regression bugs
69. During development • Develop just the required stuff • Write examples before modify your code • Code is testable by default • Only required edge cases are defined • Prevent regression bugs • Expect QA to thumbs up
70. During development • Develop just the required stuff • Write examples before modify your code • Code is testable by default • Only required edge cases are defined • Prevent regression bugs • Expect QA to thumbs up • Code as your documentation
71. Deliver the project
72. Deliver the project • Deliver what it was expected
73. Deliver the project • Deliver what it was expected • Deliver and go for a beer
75. Github example: https://github. com/carlosV2/BDD-Example Twitter: @genuineCarlosV2
76. Thank you :)