Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Introducing Test Driven Development to an existing environment

380 views

Published on

How to introduce Test Driven Development to an existing environment? Check out this presentation by Alain Thoen.

Published in: Technology
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1lite.top/UIde5 ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Introducing Test Driven Development to an existing environment

  1. 1. Test Driven Development in an existing project Alain Thoen
  2. 2. How to define Test Driven Development 2
  3. 3. What kind of tests could we want to write?  Can we return the correct list of contracts?  Was the correct percentage applied?  Check if it copies the correct contracts and leave the others merely updated. 3
  4. 4. How to define Test Driven Development 4 A method that will help you improve your FUTURE code-design, resulting in a better architecture and cleaner code base Having a bunch of unit tests is just a happy side effect Sometimes referred to as Test Driven Design
  5. 5. The benefits of TDD and Unit Tests 5
  6. 6. The disadvantages of TDD and Unit Tests 6
  7. 7. Should I implement TDD in my existing project? 7 • How long will you remain on the project • How large is the project • What is the team situation and what is your own position within the team • Other potential problems that need to be resolved before addressing unit testing
  8. 8. Convincing your team 8
  9. 9. Convincing your team 9
  10. 10. Identifying clear obstacles that stand in the way of TDD 10
  11. 11. 11 Original Code
  12. 12. 12 Reworked with Dependency Injection and Repository Pattern
  13. 13. Real Repository
  14. 14. 14 Mock Repository
  15. 15. Practicing/Teaching TDD when starting out 15
  16. 16. 16 Assign/Act/Assert example
  17. 17. Summarize 17 • TDD is a method that will help you improve your FUTURE code-design, resulting in better architecture and cleaner code base • Benefits of TDD, faster development time, less bugs, better code design • We learned when to implement TDD. Nearly always! • We talked about some of the dangers around TDD and how best to avoid them • We talked about some common issues with implementing TDD in an existing problems and how to solve it with Dependency Injection • And last, I showed you an easy way to learn TDD and reap some of the benefits right away

×