Software Architecture and Thinking. Raising TDD from the dead.

Does TDD make our code worse? When should we focus on quality and when on development speed? I would try to answer those questions base on my experience and examples from real life.

Transcript

1. Software Architecture and Thinking. Raising TDD from the dead.
2. Who am I ? @l3l0 http://github.com/l3l0
3. Agenda Basics about TDD. Mocking explanation. Software Architecture and TDD. How TDD impact the speed of development?
4. What is TDD?
5. Are we really testing?
6. TDD is about code specification and planning.
7. PHPSpec
8. PHPSpec
9. Few words about mocking.
10. Dummy, Stub, Mock.
11. Dummy
12. Production code
13. Stub
14. Production code
15. Mock
16. Production code
17. States vs Messages.
18. OOP is about messaging.
19. Mockist TDD is about planning communication, interfaces and message protocols.
20. Classic TDD is about planning expected state or just checking the result.
21. Mockist TDD example
22. Classic TDD example
23. Classic TDD example
24. Mock or not to mock?
25. Mocking drawbacks.
26. Classic approach drawbacks.
27. Let's find the balance!
28. TDD as a software design tool.
29. TDD is an enabler for thinking about communication and messages.
30. Revealing object dependencies.
31. Mocking allow to design base on abstraction, so finish with...
33. TDD and development time.
34. Do you spend more time writing code doing TDD?
35. I bet you DO! but...
36. What about time spent on fixing bugs ? What about time spent on creating upfront design ? What about time spent on manually testing our work ?
37. SO...
38. IS TDD DEAD ?
39. FU***NG NO!!!
40. Thanks!
41. http://cocoders.com @l3l0 l3l0 [at] cocoders.com https://github.com/l3l0/tdd-architecture-talk-exam ples