Test Driven Development (a short introduction) (C) John Chandler 2011
Perfect Code? First Time? Every Time? (yeah right)
Confidence Through Tests Manual Tests = Error Prone Automated Tests = Repeatable
Writing Tests After the Code Is Useful
Writing Tests Before the Code Helps us...
Think about  What before we decide  How
Write code that is easy to test
Write small units of code at a time
Ensure all code has test coverage
Know when to stop writing code
First we write a test that fails
Then we write code to make the test pass
Did we break anything?
Are we more confident?
Refactor if necessary Refactor with confidence
Then repeat until done
What else?
Fail Fast Early Feedback
Easier to learn unfamiliar code
Easier to change unfamiliar code
Supplementary code documentation
Give confidence to Others
Continuous Integration
Now go write tests!
Upcoming SlideShare
Loading in...5
×

Test Driven Development: A Short Introduction

1,051

Published on

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,051
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Test Driven Development: A Short Introduction

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

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

×