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

8. Examples – NameRetriever

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());
}
}

13. That’s all, thanks!