O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Test Driven Development at 10,000 Feet

2.584 visualizações

Publicada em

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

Publicada em: Tecnologia, Negócios
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

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?

×