Your SlideShare is downloading. ×
0
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
My Road To Test Driven Development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

My Road To Test Driven Development

937

Published on

In which I give a short introduction to unit testing, and then outline the story that finally turned on the light bulb about real test-driven development and test first for me. The third part of the …

In which I give a short introduction to unit testing, and then outline the story that finally turned on the light bulb about real test-driven development and test first for me. The third part of the talk gives an introduction to Dependency Injection (DI), an integral part to unit testing.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
937
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
39
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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. <ul><li>Business Requirements: </li></ul><ul><li>If two events have the same name AND same location, they are the same event. Merge. </li></ul><ul><li>Else, if two events have the same location, AND they occur within 1 hour of each other, they are the same event. Merge. </li></ul>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. <ul><li>Business Requirements: </li></ul><ul><li>3. To merge two events, for each field, keep the longer of the two fields. For DateTimes, keep the earlier occurrence. </li></ul>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. <ul><li>Business Requirements: </li></ul><ul><li>4. Profit! </li></ul>Dependency Injection FTW! 3.
  • 42. Thanks! Questions! Comments! @hellogerard straylightrun.net © 2009. Some rights reserved.

×