Download as PDF, PPTX
Uploaded byDavid Paluy
Tdd - Test Driven Development
TDD involves writing tests before writing code to ensure code works as intended and allows for refactoring. The TDD process involves writing specifications, tests, and then code. Tests provide confidence that code works, help design better code, and act as documentation. Tests should be written even for code that currently works perfectly since requirements and needs change over time. The benefits of TDD include producing modular code that is easy to change and refactor.
More Related Content
Similar to Tdd - Test Driven Development
Tdd - Test Driven Development
- 1. TDD Test Driven Development DavidPaluy Jul 2015
- 2. Agenda 1. When dowe need to write tests 2. The TDD process 3. Glossary
- 3. Test Driven Development Youdon’t have to do TDD, You should do TDD.
- 4. When do weneed to write tests? If my code works perfectly, why should I write tests for it?
- 5. Realization 1 Testing breedsconfidence
- 6. Confidence ● Modular code ●Many changes ● Refactoring If there are NO TESTS, you should be worried making changes!
- 7. “Write a failingautomated test before changing any code” - Kent Beck Remember
- 8. When do weneed to write tests? So, if the code works perfectly, and I’m never going to change it, then why should I write tests?
- 9. Realization 2 If youwrite tests before you write your code, you end up writing a better code
- 10. If I writethe test first, ● It forces me think before I code ● Code is more focused and clear ● I know when I’m finished, because all the tests pass
- 11. When do weneed to write tests? So, if the code works perfectly, and I’m never going to change it and the design is already flawless, then why should I write tests?
- 12. Realization 3 Well writtentests are just as good, if not better than documentation
- 13. Yoga Instructions 1. Kneeldown 2. Put your hands flat in the ground 3. Lift your feet off the ground and balance on your hands 4. Put your knees ahead of your hands 5. Stretch out your back so your body is perpendicular to the ground
- 14.
- 15. Yoga Instructions Examples >Comments
- 16. When do weneed to write tests? So, if the code works perfectly, and I’m never going to change it and the design is already flawless and it is totally readable and understandable, then why should I write tests?
- 17.
- 18. Learning Test DrivenDevelopment
- 19. The TDD process ●Write specifications ● Write tests ● Write code
- 20.
- 21.
- 22. Glossary ● Unit Tests ●Integration Tests ● Acceptance Tests ● Mocks, Stubs
- 23. Unit Test -Method to verify isolated units of code ● Checks a single assumption about the behavior of the unit ● Fast running tests ● Quick to debug ● Is hitting DB - is OK?
- 24. Integration Tests ● Testssoftware modules as a group ● Tests integration points ● Slower than Unit tests
- 25. Acceptance tests ● End-to-endtest cases of: happy user journeys and critical failure scenarios ● Production like environment ● Manual or Automated
- 26. Mocks vs Stubs MockObjects are special case objects that mimic real objects for testing. Stubs provide canned answers to calls made during the test
- 27.
- 28.
- 29. Test Driven Development Apply Inspect Adapt Ifyou haven’t done it first, you don’t know what you are talking about!
- 31. “Any fool canwrite code that a computer can understand. Good programmers write code that humans can understand.” Martin Fowler, 2008.