Your SlideShare is downloading. ×
0
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
Why Test Driven Development?
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

Why Test Driven Development?

4,335

Published on

Why should developers learn and care of TDD as an important skill?

Why should developers learn and care of TDD as an important skill?

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

No Downloads
Views
Total Views
4,335
On Slideshare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
84
Comments
0
Likes
6
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 Why Should You Care about TDD And Automated (Unit) Testing? Naresh Jain Twitter: @nashjain Blog: http://blogs.agilefaqs.com Licensed Under Creative Commons by Naresh Jain 1
  • 2. Test Driven DevelopmentTDD Rhythm - Test, Code, Refactor 2
  • 3. Test Driven Development Add a TestTDD Rhythm - Test, Code, Refactor 2
  • 4. Test Driven Development Add a Test Run the TestTDD Rhythm - Test, Code, Refactor 2
  • 5. Test Driven Development Add a Test Pass Run the TestTDD Rhythm - Test, Code, Refactor 2
  • 6. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor 2
  • 7. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change 2
  • 8. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Run the Test 2
  • 9. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Fail Run the Test 2
  • 10. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Fail Run the Test Pass 2
  • 11. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Fail Run the Test Pass Refactor 2
  • 12. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Fail Run the Test Pass Refactor 2
  • 13. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Fail Run the Test Pass Refactor 2
  • 14. Test Driven Development Add a Test Pass Run the Test FailTDD Rhythm - Test, Code, Refactor Make a little change Fail Run the Test Pass Refactor 2
  • 15. Why Learn TDD? 3
  • 16. Manual (monkey) Checking by Developers and Tester 4
  • 17. Stay away from (time hungry) debugger 5
  • 18. Maintain Focus 6
  • 19. Confidence 7
  • 20. Reduce Wastage: Hand Overs 8
  • 21. Helps youSlow down and Think 9
  • 22. Communication 10
  • 23. 11
  • 24. Ultimate Goals 12
  • 25. Ultimate Goals• Bring JOY back to programming 12
  • 26. Ultimate Goals• Bring JOY back to programming• Understand Code Easily 12
  • 27. Ultimate Goals• Bring JOY back to programming• Understand Code Easily• Produce Simple, Testable, Loosely-Coupled Design 12
  • 28. Ultimate Goals• Bring JOY back to programming• Understand Code Easily• Produce Simple, Testable, Loosely-Coupled Design• Build Quality In 12
  • 29. Ultimate Goals• Bring JOY back to programming• Understand Code Easily• Produce Simple, Testable, Loosely-Coupled Design• Build Quality In• Reduce Maintenance Significantly 12
  • 30. Living, up-to-date specification 13
  • 31. Learning:Listen to your code 14
  • 32. Testable Code by Design + Safety Net 15
  • 33. Communicate Design Decisions 16
  • 34. Loosely-Coupled Design 17
  • 35. Refactoring 18
  • 36. Ultimate Goals• Bring JOY back to programming• Understand Code Easily• Produce Simple, Testable, Loosely-Coupled Design• Build Quality In• Reduce Maintenance Significantly 19
  • 37. Thank You! Naresh Jain naresh@agilefaqs.comLicensed Under Creative Commons by Naresh Jain 20

×