Your SlideShare is downloading. ×
0
TEST DRIVEN DEVELOPMENT                   At 10,000 feet                                Let’s begin→
WHY TDD?• We need a way to find defects earlier on in the development cycle..
TDD REDUCES DEBUG TIME
TESTS = CODE EXAMPLES
NO TDD = NO VELOCITY• The more complex our code becomes, the longer it takes to make  changes or add new features.        ...
TDD PROTECTS US FROM OURSELVES• Automated tests remind us when we inadvertently screw up part of  the code. No matter how ...
TDD EMPOWERS YOU
THE THREE RULES OF TDD
RULE # 1• You are not allowed to write any  production code unless it is to  make failing unit tests pass.
RULE #2• You are not allowed to write any  more of a unit test than is  sufficient to fail; and compilation  failures are ...
RULE #3• You are not allowed to write any  more production code than is  sufficient to pass the one failing  test.
TDD IN PRACTICE
SAY WHAT?
Let’sseesomecode
The Bowling Game1 4   4 5   6    5          0 1 7     6          2   65     14    29   49    60   61   77   97   117   133
• Test code is just as important  as production code and should  be shown the same level of  respect and professionalism.
THANK YOU!Any Questions?
Upcoming SlideShare
Loading in...5
×

Test Driven Development at 10,000 Feet

1,108

Published on

An introduction to Test Driven Development for those not familiar with it.

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

  • Be the first to like this

No Downloads
Views
Total Views
1,108
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Image source: http://25.media.tumblr.com/tumblr_l2690pvsbD1qa4lf5o1_r1_500.png
  • Image Source: http://iformattable.blogspot.com/2010/09/real-software-engineering-agile-value.html
  • With TDD, at any point in time, everything a programmer was working on within a few minutes executed and passed all of its tests.What would your life be like if everything always worked a minute or so ago? How much debugging would you need to do?With such little time invested in creating the defect, removing the defect will not be difficult.Image source: http://cdn.techi.com/wp-content/uploads/2010/06/smashedComputer-1024x799.jpg
  • As programmers, we are always looking to code examples to teach us how to use an API. What better example of how to use the system is there than the unit test suite?
  • Image source: http://michaelfeathers.typepad.com/michael_feathers_blog/2011/03/data-rich-development.html
  • TDD gives you as a developer the courage to clean up code by telling you if you screwed something up right away.If you see something wrong, FIX IT!
  • Content Source: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTddImage source: http://homepage.mac.com/jfstrain/blogpics/apr04/rules.jpg
  • Image source: http://www.morningstarcomm.com/wp-content/uploads/2011/08/apple-number-one-in-phone-sales2.jpg
  • Image Source: http://agileinaflash.blogspot.com/2009/02/red-green-refactor.html
  • Image source: http://wellington.pm.org/archive/200606/tdd/images/tdd_cycle.jpg
  • Code example.
  • Image source: http://blumonkey.org/weblog/pictures/large_PA191996-1.jpgContent Source: http://butunclebob.com/ArticleS.UncleBob.TheBowlingGameKata
  • http://agileinaflash.blogspot.com/2009/02/first.html
  • Transcript of "Test Driven Development at 10,000 Feet"

    1. 1. TEST DRIVEN DEVELOPMENT At 10,000 feet Let’s begin→
    2. 2. WHY TDD?• We need a way to find defects earlier on in the development cycle..
    3. 3. TDD REDUCES DEBUG TIME
    4. 4. TESTS = CODE EXAMPLES
    5. 5. NO TDD = NO VELOCITY• The more complex our code becomes, the longer it takes to make changes or add new features. Hard to change Complexity Time  Easy to change
    6. 6. TDD PROTECTS US FROM OURSELVES• Automated tests remind us when we inadvertently screw up part of the code. No matter how significant.
    7. 7. TDD EMPOWERS YOU
    8. 8. THE THREE RULES OF TDD
    9. 9. RULE # 1• You are not allowed to write any production code unless it is to make failing unit tests pass.
    10. 10. RULE #2• You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
    11. 11. RULE #3• You are not allowed to write any more production code than is sufficient to pass the one failing test.
    12. 12. TDD IN PRACTICE
    13. 13. SAY WHAT?
    14. 14. Let’sseesomecode
    15. 15. The Bowling Game1 4 4 5 6 5 0 1 7 6 2 65 14 29 49 60 61 77 97 117 133
    16. 16. • Test code is just as important as production code and should be shown the same level of respect and professionalism.
    17. 17. THANK YOU!Any Questions?
    1. A particular slide catching your eye?

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

    ×