Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

BDD by example

666 views

Published on

Slides used for internal training at myTaste

Published in: Technology
  • Be the first to comment

BDD by example

  1. 1. BDD by example
  2. 2. IT'S ABOUT LANGUAGE MONEY
  3. 3. –Eric Evans, Domain-Driven Design “A project faces serious problems when its language is fractured. Domain experts use their jargon while technical team members have their own.”
  4. 4. Incorrect translations are the primary cause of features that damage business instead of helping them. COST OFTRANSLATION
  5. 5. BDD & DDD
  6. 6. BDD focuses on eliminating translation costs on conversations
  7. 7. BDD uses scenarios
  8. 8. –Eric Evans, Domain-Driven Design “To cross-check all these decisions, we have to constantly step through scenarios to confirm that we can solve application problems effectively.”
  9. 9. DDD focuses on eliminating translation costs in the code
  10. 10. DDD uses domain models
  11. 11. –Eric Evans, Domain-Driven Design “A domain model is not a particular diagram; it is the idea that the diagram is intended to convey.A diagram can represent and communicate a model, as can carefully written code, as can an English sentence.”
  12. 12. BDD & DDD help you to reduce the cost of translations
  13. 13. UBIQUITOUS LANGUAGE
  14. 14. Helps you to facilitate conversations
  15. 15. Model your core domain in a language both business and developers can understand.
  16. 16. END-TO-ENDTESTING PROBLEMS
  17. 17. Scenarios can be used to: • drive the core domain • drive the user interface
  18. 18. With BDD you can use your scenarios to test your application at multiple leves using the same behavioural examples
  19. 19. DRIVINGTHE CORE DOMAIN
  20. 20. Embed Ubiquitous language into scenarios
  21. 21. Your scenarios become your domain model
  22. 22. These scenarios can be used to develop the core domain
  23. 23. DEMO
  24. 24. –Konstantin Kudryashov (@everzet) “Focus on discussing business problems and the architecture will emerge naturally.”
  25. 25. THANKS

×