This document discusses test-driven development (TDD) and provides examples of TDD code katas. It begins with introductions and then provides guidelines for a TDD workshop focusing on interactions, working software, collaboration and responding to change. It explains that TDD is about having a short feedback loop and should focus on design and contracts before implementation. Examples then demonstrate TDD for tasks like replacing variables and the FizzBuzz problem. Tests are provided and requirements are expanded on for one of the katas. In closing, the author thanks participants and offers to answer questions.

1. The TDD game
that you never played
Lior Israel
http://blogs.microsoft.co.il/lior_israel/
https://www.linkedin.com/in/liorisrael

2. Who are
you ?

3. Who are you really?
Developer
Traveler
Product
experts
Manager
Scrum
master
QA

4. Who
am I ?

5. Who
am I ?
Hardware
developer
Developer
Chief
Architect
“Chef”
Geek of
Code
Blogger
Husband
&
Father

6. Workshop guideline
We are going to use
interactions ,
Working software,
participants
collaboration and
Responding to
change
First open your
mind
This is not only
for a developers
– this is for ALL
players in the
AGILE game
We will run 2-3
katas – we can
play andor you
can watch
Any case try to
enjoy

7. It’s all about
A short
feedback loop

8. TDD as a way of working
• TDD is not a UNIT TEST
• TDD is part of the Software craftsmanship
• TDD must be adjusted to US/DoD and not to
Implementation
• If someone can understand your test
You are on the right way
• If the BA can understand your test
You are in a perfect way

9. TDD – Test Driven Design
Design High Level system
Build the contracts
"Fake it 'til you make it“ – make it clear
The system must be green
Now we can implement it

10. The first kata

11. • As an interviewer
• I want that the candidate to write
a code that will replace the two
variables (INT)
• So I can figure out whether he is
the right person for the job

12. The FizzBuzz kata

13. FizzBuzz code KATA
• Write a program that prints the
numbers from 1 to 100. But for
multiples of three print "Fizz" instead
of the number and for the multiples
of five print "Buzz". For numbers
which are multiples of both three
and five print "FizzBuzz"

14. Here are the new requirements
• A number is fizz if it is divisible by 3
or if it has a 3 in it
• A number is buzz if it is divisible by 5
or if it has a 5 in it

15. The Potter kata
http://www.codingdojo.org/cgi-bin/index.pl?KataPotter

16. Problem Description
• For example, how much does this basket of
books cost?
– 2 copies of the first book
– 2 copies of the second book
– 2 copies of the third book
– 1 copy of the fourth book
– 1 copy of the fifth book
– 2* (8*4*0.8) ,answer: 51.20 EUR

17. Few tests for a starting
def testSeveralDiscounts
assert_equal(8 + (8 * 2 * 0.95), price([0, 0, 1]))
assert_equal(2 * (8 * 2 * 0.95), price([0, 0, 1, 1]))
assert_equal((8 * 4 * 0.8) + (8 * 2 * 0.95), price([0, 0, 1, 2, 2, 3]))
assert_equal(8 + (8 * 5 * 0.75), price([0, 1, 1, 2, 3, 4]))
end
def testEdgeCases
assert_equal(2 * (8 * 4 * 0.8), price([0, 0, 1, 1, 2, 2, 3, 4]))
assert_equal(3 * (8 * 5 * 0.75) + 2 * (8 * 4 * 0.8),
price([0, 0, 0, 0, 0,
1, 1, 1, 1, 1,
2, 2, 2, 2,
3, 3, 3, 3, 3,
4, 4, 4, 4]))
end

18. Thank
you :-9
I'm
available
for
Questions
Any time,
any place,
anywhere