Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Folding The Design Space @SoCraTes Germany 9 August 2014

This talk is about how you can use specification by example to write bottom-up TDD. I use TDD as if you meant it as the extreme classicist TDD aproach for showing how you can grow your systems bottom-up.

See here the flipchart pictures from during the presentation:

See here the codebase:

Picture from during the session:

Folding The Design Space @SoCraTes Germany 9 August 2014

  1. 1. Folding the Design Space Case Study: TDD with Specification by Example
  2. 2. Me Adi Bolboacă Programmer Organizational & Technical Trainer & Coach
  3. 3. TDD
  4. 4. TDD As if you Meant It 1) Write exactly one failing test 2) Make the test pass by writing implementation code in the test method 3) Create a new implementation method by: a) Extracting implementation code to a new method in the test class b) Moving implementation code into an existing implementation method from the test class 4) Create implementation classes to provide a destination for extracting a method in the test class 5) When necessary move implementation methods into implementation classes 6) Refactor as required
  5. 5. Classicist TDD Prefer writing state tests Usually start bottom-up Do not use test doubles unless necessary
  6. 6. Mockist TDD Prefer writing collaboration tests Usually start top-down Always test in isolation Use only one mock at a time for a test
  7. 7. Specification by Example [...]Defining requirements and business- oriented functional tests for software products based on capturing and illustrating requirements using realistic examples instead of abstract statements. []
  8. 8. Problem: Conway's Game of Life Having an infinite 2D orthogonal universe Being given an initial generation called a seed The following rules are applied simultaneously A live cell having less than 2 live neighbors dies A live cell having 2 or 3 live neighbors lives A live cell having more than 3 neighbors dies A dead cell having 3 neighbors becomes alive
  9. 9. Purposes of the session I care about specifications and I don't care about representation Have the cleanest design possible with highly cohesive structures Use real life examples as specifications
  10. 10. Incremental design I want to introduce one notion at a time.
  11. 11. The visible notions from Conway's Game of Life Cell Board Universe Life state Generation Set of rules Neighbourhood
  12. 12. Start with Incremental design Simplify the problem Introduce only one notion at a time Find the main functionality: Tick()
  13. 13. Question What would the simplest first step be?
  14. 14. Option: Slider Gun
  15. 15.
  16. 16. Requirements From real life examples “Specification by Example”
  17. 17. Conclusions When the solution is less known TDD as if you meant it is useful Bottom-up TDD is useful to grow a system You need to refactor more with TDD bottom-up The design increments are smaller bottom-up
  18. 18. Thank you!
  19. 19. References
  20. 20. Enterprise Agile Architect Role Contact me Unit testing workshop Remote pair-programming TDD workshop Refactoring workshop Legacy code workshop Legacy code retreat Code retreat
  21. 21. Enterprise Agile Architect Role Extend your mentoring & training capacity Accelerate learning through communities of practice Grow your functional leaders and top talents @adibolb