Test Driven Development: A Short Introduction
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Test Driven Development: A Short Introduction

on

  • 1,310 views

A brief introduction to TDD given 8th April 2011 to a group of junior developers. Part of an agile development induction afternoon.

A brief introduction to TDD given 8th April 2011 to a group of junior developers. Part of an agile development induction afternoon.

Statistics

Views

Total Views
1,310
Views on SlideShare
1,308
Embed Views
2

Actions

Likes
0
Downloads
2
Comments
0

1 Embed 2

http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

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 Development: A Short Introduction Presentation Transcript

  • 1. Test Driven Development (a short introduction) (C) John Chandler 2011
  • 2. Perfect Code? First Time? Every Time? (yeah right)
  • 3. Confidence Through Tests Manual Tests = Error Prone Automated Tests = Repeatable
  • 4. Writing Tests After the Code Is Useful
  • 5. Writing Tests Before the Code Helps us...
  • 6. Think about What before we decide How
  • 7. Write code that is easy to test
  • 8. Write small units of code at a time
  • 9. Ensure all code has test coverage
  • 10. Know when to stop writing code
  • 11. First we write a test that fails
  • 12. Then we write code to make the test pass
  • 13. Did we break anything?
  • 14. Are we more confident?
  • 15. Refactor if necessary Refactor with confidence
  • 16. Then repeat until done
  • 17. What else?
  • 18. Fail Fast Early Feedback
  • 19. Easier to learn unfamiliar code
  • 20. Easier to change unfamiliar code
  • 21. Supplementary code documentation
  • 22. Give confidence to Others
  • 23. Continuous Integration
  • 24. Now go write tests!