Test Driven is Driving me Insane!<br />Practical Test Patterns<br />
Who?<br />Dennis Burton<br />SRT Solutions<br />DevelopUsing.net || DennisBurton.com<br />@dburton<br />Feedback:<br />htt...
Life before tests<br />
User Group / Article / Blog Post<br />
Build Proof of Concept<br />
Present Concept<br />
Double the code are you kidding?<br />
Adopting testing take 2<br />
The Primer<br />
All 10 of my tests rock<br />
Code changes seem to take longer<br />
Long running tests<br />
Tests take longer to set up<br />
Test are fragile<br />
Tests depend on specific (often production) data<br />
Maybe tests are not worth it<br />
Upcoming SlideShare
Loading in...5
×

Test Driven is Driving Me Insane!

237

Published on

Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage.

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

  • Be the first to like this

No Downloads
Views
Total Views
237
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Test Driven is Driving Me Insane!

  1. 1. Test Driven is Driving me Insane!<br />Practical Test Patterns<br />
  2. 2. Who?<br />Dennis Burton<br />SRT Solutions<br />DevelopUsing.net || DennisBurton.com<br />@dburton<br />Feedback:<br />http://speakerrate.com/dennisburton<br />http://speakerrate.com/events/131-codestock<br />
  3. 3. Life before tests<br />
  4. 4. User Group / Article / Blog Post<br />
  5. 5. Build Proof of Concept<br />
  6. 6. Present Concept<br />
  7. 7. Double the code are you kidding?<br />
  8. 8. Adopting testing take 2<br />
  9. 9. The Primer<br />
  10. 10. All 10 of my tests rock<br />
  11. 11. Code changes seem to take longer<br />
  12. 12. Long running tests<br />
  13. 13. Tests take longer to set up<br />
  14. 14. Test are fragile<br />
  15. 15. Tests depend on specific (often production) data<br />
  16. 16. Maybe tests are not worth it<br />
  17. 17. Position Statement - Uncle Bob Martin<br />…it has become my position that TDD is a necessary discipline for professional developers. I consider it rather like sterile procedure for doctors. It&apos;s simply what you have to do to write professional code. (At least it&apos;s what I have to do.)<br />-ButUncleBob.com<br />
  18. 18.
  19. 19. What am I missing?<br />
  20. 20. But, I already have some legacy code not under test<br />
  21. 21. References<br />xUnit Test Patterns<br />Working Effectively<br />with <br />Legacy Code<br />
  22. 22. Dummy – An object is required that shouldn’t be<br />Spy – Add the validation an object should have had<br />Stub – The state of an object is important to the test<br />Mock – behavior is what is really under test<br />Use Rhino or Moq<br />Don’t tolerate test pain<br />
  23. 23.
  24. 24. Dummy Pattern<br />
  25. 25. Stub Pattern<br />
  26. 26. Mock Pattern<br />
  27. 27. Spy Pattern<br />
  28. 28. Questions<br />Dennis Burton<br />SRT Solutions<br />DevelopUsing.net || DennisBurton.com<br />@dburton<br />Feedback:<br />http://speakerrate.com/dennisburton<br />http://speakerrate.com/events/131-codestock<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×