This document discusses test driven development using JUnit and FitNesse. It begins with describing the target audience as Java developers, programmers in other languages, team leaders, and testers. The agenda then outlines introducing TDD, a simple example project using JUnit, adding FitNesse, and advanced topics. The example project involves validating barcamp names. Benefits of unit testing are listed as ensuring foundations are solid, creating better design, and considering edge cases.

1. Test Driven Development
with JUnit and Fittness
Lukas Rypl
TTC MARCONI
Czech Republic
Twitter: @LukasRypl
for BarCamp Saigon
9/9/2012

2. Target Audience
Java developers
Programmers in any other language
Their team leaders
Testers
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 2 / 10

3. Target Audience
Java developers
Programmers in any other language
Their team leaders
Testers
Profesionals who
feel safer
sleep better
validate their work
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 2 / 10

4. Agenda
Intro - what and why
Simple project with JUnit
Adding Fitness
Advanced topics
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 3 / 10

5. Our simple project
Everybody is talking about BarCamp.
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 4 / 10

6. Our simple project
Everybody is talking about BarCamp.
Bar Camp Saigon
barcamp
BarCamp Saigon 2012
#barcampsaigon
. . .
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 4 / 10

7. Our simple project
Everybody is talking about BarCamp.
Bar Camp Saigon
barcamp
BarCamp Saigon 2012
#barcampsaigon
. . .
Task: is it a valid name?
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 4 / 10

8. Developers Work Algorithm
Test Driven Development
while (task.requiresWork())
{
1. Write a failing unit test
2. Write implementation
}
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 5 / 10

9. Why Unit Testing
make sure that foundations are OK
create better (extensible) design
think about edge cases
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 6 / 10

10. Tools
Eclipse (IDE) www.eclipse.org
JUnit (unit testing library) www.junit.org
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 7 / 10

11. Tools
Eclipse (IDE) www.eclipse.org
JUnit (unit testing library) www.junit.org
Fitness www.fitnesse.org
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 7 / 10

12. Time to play
JUnit
Fitness
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 8 / 10

13. Time to play
JUnit
Fitness
Why another tool?
acessibe to non-programers
examples can be created during analysis
may overlap with junit / preventing
duplication?
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 8 / 10

14. Unit Testing Books
Kent Beck:
Test Driven Development by Example (2002)
Martin Fowler:
Refactoring: Improving the Design of Existing
Code (1999)
Michael E. Faethers:
Working Effectively with Legacy Code (2004)
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 9 / 10

15. Advanced Topics
dealing with dependencies (mocks, stubs)
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 10 / 10

16. Advanced Topics
dealing with dependencies (mocks, stubs)
running tests automatically
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 10 / 10

17. Advanced Topics
dealing with dependencies (mocks, stubs)
running tests automatically
acceptance tests driven development (ATDD),
specification by example (cucumber)
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 10 / 10

18. Advanced Topics
dealing with dependencies (mocks, stubs)
running tests automatically
acceptance tests driven development (ATDD),
specification by example (cucumber)
when unit tests do not pay off?
Lukas Rypl (BarCamp Saigon) Test Driven Development 9/9/2012 10 / 10