Unit tests are great, they help a developer gain control over his code and catch bugs and regression issues. Test Driven Development is a methodology that uses unit tests but it's not about writing unit tests - in fact the tests are only a design tool. TDD is a methodology that solves problems in an iterative way, it's about emergent design that creates a maintainable solution. In this session I'll talk about common mistakes and misconceptions, how to benefit from TDD and show how to design your code using unit tests. The code for this talk can be found on GitHub: https://github.com/dhelper/DesignWIthTests

2. http://blog.drorhelper.com

3. Red
Green
Refactor

4. Red
Green
Refactor

5. Test
Test
Test
Tests

6. is not

7. TDD is not about the tests
It’s about Emergent Design

8. Phone rings
User Accepts
call
User connects
to call

9. And now for something completely different

10. underwater?

11. Sounds familiar?

13. Phone rings
User Rejects
call
Call ends
UserAccept
Call
Do Nothing

15. Phone rings User Accepts call
Receive acknowledge
from caller
User connects to call

16. annoy

19. Phone rings User Accepts call
Receive acknowledge
from caller
User connects to call

21. And most importantly

22. architect

23. Architecture is still needed
functional requirements
quality
constraints
principles
http://www.codingthearchitecture.com/2014/02/19/software_architecture_provides_boundaries_for_tdd_bdd_ddd_rdd_and_clean_code.html

24. “
”
framework
boundaries
vision and guidance

25. Drives design – emergent design
Help you stay on track
Reduce distractions cost
Enable change
architecture

26. drorh@codevalue.net http://blog.drorhelper.com