Test driven development
Download as PPTX, PDF0 likes476 views
This document discusses test driven development (TDD), including that it was created by Kent Beck in 2003 based on concepts from extreme programming. TDD focuses on writing tests before code using cycles of writing a failing test, making it pass, and refactoring. Benefits include more tests and less bugs, higher code quality, and a more modular system, while limitations include needing management support and potential for fake tests. The document provides an example of TDD using JUnit tests for a NameRetriever class.
Test driven development
- 1. Test Driven Development Marcelo Cure
- 2. Where did it come from? • Kent Beck in 2003 • Concepts related to Extreme Programming
- 3. What’s TDD? • Development technique • Focus on quality • First test then code • Requirements before code • Based on cycles
- 4. How does TDD work? • Developer must have the feature knowledge • Think baby steps • Write a failing test • Make it pass • Make sure it didn’t break any other test • Refactor • Loop
- 5. Benefits • More tests, less bugs • Code quality • Rare necessity to debug • Leads to modularize your system • Big coverage
- 6. Limitations • Management support is required • Fake tests • Are we really doing TDD?
- 7. Environment (talking about Java) • Java • Eclipse • JUnit
- 9. NameRetrieverTest public class NameRetrieverTest { private NameRetriever nameRetriever; @Test public void testRetrieveName() { String name = nameRetriever.retrieveName(); Assert.assertEquals("cure", name); } }
- 10. NameRetriever public class NameRetriever { public String retrieveName() { return ""; } }
- 11. NameRetriever public class NameRetriever { public String retrieveName() { return "cure"; } }
- 12. NameRetrieverTest public class NameRetrieverTest { private NameRetriever nameRetriever; @Test public void testRetrieveName () { Assert.assertEquals("cure", nameRetriever.retrieveName()); } }