Test Driven is Driving Me Insane!
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Test Driven is Driving Me Insane!

on

  • 477 views

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, ...

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.

Statistics

Views

Total Views
477
Views on SlideShare
477
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Test Driven is Driving Me Insane! Presentation Transcript

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