The document is a personal narrative by Gerard Sychay detailing his journey toward adopting test-driven development (TDD) in software engineering. It discusses the importance of unit testing, dependency injection, and the specific business requirements that influenced his approach to event merging. The author emphasizes the practical applications of TDD and concludes with an invitation for questions and comments.

1. My Road To Test Driven Development: A Story Gerard Sychay @oinkpug 08/19/2009

2. My name is Gerard Sychay.

3. Zipscene.com

4. Cincinnati Coworks

5. Are you unit testing?

6. Are you developing unit tests first?

7. (Very) Short introduction to unit testing 1. “ Discovering” Test Driven Development 2. 2. Dependency Injection FTW! 3.

8. PHPUnit (Very) Short introduction to unit testing 1.

9. (Very) Short introduction to unit testing 1.

10. (Very) Short introduction to unit testing 1.

11. “ Red , green , refactor.” Discovering Test Driven Development 2.

12. That’s nice, but… Discovering Test Driven Development 2. Discovering Test Driven Development 2.

13. Discovering Test Driven Development 2.

14. Then, one day… Discovering Test Driven Development 2.

15. Problem: Does this event “exist?” Discovering Test Driven Development 2.

16. Business Requirements: If two events have the same name AND same location, they are the same event. Merge. Else, if two events have the same location, AND they occur within 1 hour of each other, they are the same event. Merge. Discovering Test Driven Development 2.

17. Discovering Test Driven Development 2.

18. Discovering Test Driven Development 2.

19. Discovering Test Driven Development 2.

20. Discovering Test Driven Development 2.

21. Discovering Test Driven Development 2.

22. Discovering Test Driven Development 2.

23. Discovering Test Driven Development 2. Discovering Test Driven Development 2.

24. Business Requirements: 3. To merge two events, for each field, keep the longer of the two fields. For DateTimes, keep the earlier occurrence. Discovering Test Driven Development 2.

25. Discovering Test Driven Development 2.

26. Discovering Test Driven Development 2. Discovering Test Driven Development 2.

27. Discovering Test Driven Development 2. Discovering Test Driven Development 2.

28. “ Is that bug really fixed?” Discovering Test Driven Development 2.

29. “ Hey, I thought that bug was fixed.” Discovering Test Driven Development 2.

30. Discovering Test Driven Development 2. Discovering Test Driven Development 2. Discovering Test Driven Development 2.

31. Discovering Test Driven Development 2. Discovering Test Driven Development 2.

32. Requirements Driven Development Discovering Test Driven Development 2.

33. That’s nice, but… Discovering Test Driven Development 2.

34. Dependency Injection FTW! 3.

35. Dependency Injection FTW! 3.

36. MVC, n’est pas? Dependency Injection FTW! 3.

37. Dependency Injection FTW! 3.

38. Dependency Injection FTW! Dependency Injection FTW! 3.

39. Dependency Injection FTW! 3. Dependency Injection FTW! 3.

40. Dependency Injection FTW! 3. Dependency Injection FTW! 3.

41. Business Requirements: 4. Profit! Dependency Injection FTW! 3.

42. Thanks! Questions! Comments! @hellogerard straylightrun.net © 2009. Some rights reserved.