BDD Failures

When trying to make BDD working for you projects, there always can be some failures. Presentation from Women In Technology Silesia, Gliwice, 12.06.2014.

Transcript

1. BDD Failures Dariusz Drobisz WIT, Gliwice, 12.06.2014
2. About me • PHP developer • BDD practicioner • OpenSource fan • PHPers organizer
3. What is BDD?
4. Or what BDD is NOT?
5. What BDD is not? • tests (it’s just a part and great artifact)
6. What BDD is not? • tests (it’s just a part and great artifact) • Behat
7. What BDD is not? • tests (it’s just a part and great artifact) • Behat • RSpec
8. What BDD is not? • tests (it’s just a part and great artifact) • Behat • RSpec • Jasmine
9. What BDD is not? • tests (it’s just a part and great artifact) • Behat • RSpec • Jasmine (they are tools)
10. So what is?
11. What BDD is? METHODOLOGY
12. “Behaviour-driven development is about implementing an application by describing its behaviour from the perspective of its stakeholders” Dan North
13. What BDD is? TDD
14. What BDD is? TDD 2.0
15. What BDD is?
16. What BDD is? 2 levels
17. What BDD is? Story BDD Describing high level business application behaviour. Spec BDD Describing low level implementation behaviour.
18. For why BDD is? Developer Help understand BUSINESS and DESIGN Customer Help understand WHAT HE NEED
19. Why so failures?
20. Why so failures? Because it is not about changing code...
21. Why so failures? Because it is not about changing code... … it is about changing people.
22. And they thinking about programming.
23. So what could go wrong? Let’s see some examples.
24. B(a)DD way - example #1 Stakeholders (not)involvement
25. Stakeholders (not)involvement Customer: I’m not sure what I need. Developer: So what problem you wan’t to resolve? C: I don’t know exactly, maybe you can tell me what I should need.
26. Stakeholders (not)involvement • they are undecided • they don’t involve in process of user stories creation • the even don’t wan’t to look at it • let everything up to developer
27. Stakeholders (not)involvement For why I need you stakeholder?
28. Stakeholders (not)involvement Let me know your BUSINESS
29. B(a)DD way - example #2 I know your business so...
30. B(a)DD way - example #2 I know your business so let me write TECHNICAL scenarios for you.
31. Technical scenarios Feature: In order to buy product As a user I need to be able to add product to cart
32. Technical scenarios Scenario 1: Given I am on the homepage When I follow “Products” And I fill in “Count” by “2” beside “Product 1” And I click “Add to cart” beside “Product 1” And I follow “My cart” ….
33. Technical scenarios …. Then I should see “Product 1” And I should see “2”
34. Technical scenarios Where is the BUSINESS???
35. Technical scenarios Scenario 1: Given I am on the shop When I add “Product 1” to cart Then I should see “Product 1” in my cart
36. Technical scenarios Goal achieved Business can understand what is going on.
37. B(a)DD way - example #3 (Un)understanding
38. My only right way!!! A decisive person in project…
39. My only right way!!! A decisive person in project … … with technical knowledge ...
40. My only right way!!! A decisive person in project … … with technical knowledge … … without understanding of what BDD is for.
41. My only right way!!! I was doing that tests for years I was doing that in different way, other tools I liked it better, why are you doing this that way Don’t use that!
42. My only right way!!! CRASH Tool and methodology you were using to design system behaviour gone away :(
43. B(a)DD way - example #4 Stories/specs everywhere!!!
44. Stories/specs everywhere. New methodology - (To) huge enthusiasm
45. Stories/specs everywhere. • Trying to describing everything - including 3rd party libraries
46. Stories/specs everywhere. • Trying to describing everything - including 3rd party libraries • To huge amount of time for BDD
47. Stories/specs everywhere. • Trying to describing everything - including 3rd party libraries • To huge amount of time for BDD • Last adventure with BDD at work :(
48. B(a)DD way - example #5 Tools (un)knowledge
49. Tools (un)knowledge Domain Driven Design vs. Tool Tight Coupling
50. Tools (un)knowledge Tight Couple Tool which you are not great in can discourage you for BDD.
51. Summary • Need to change people thinking • Need pople involvement • Need good will • Need openness of mind • Need understanding
52. BDD It’s easy - It’s all about people.
53. Questions?
54. Thank you dariusz.drobisz@gmail.com, @daryush_d