Your SlideShare is downloading. ×
Test Driven Development: A Short Introduction
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

Test Driven Development: A Short Introduction

1,036
views

Published on

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.

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,036
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
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. 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!

×