TDD has been around since 2002 but today still too many people out there have little understanding of what it actually is. This slide deck tries to help to understand that TDD is not a method to create tests but a truly genuine way to do programming and that programmers like no other benefit from the technique. Hopefully, this will lead more people to embracing it.

1. More Development
Than Ever
Test Driven Development

2. Team Lead at EPAM
Agile practitioner (CSM)
Trainer
Public speaker

4. Writes perfect code with no bugs
Also saves the world during coffee breaks

5. I’m more like
this guy

6. Billions of years ago…
In the stone age of computer science…
© Mutatis mutandis

7. © Computer History Museum

8. 1994–95:
rediscovered by
Kent Beck
© Improve It

9. 2014 – 1995 = ?

10. 2014 – 1999 = 15

11. 2014 – 2002 = 12

12. I spend too
much time
writing tests.

13. TDD
Non-TDD
Think Test Code
Think Code

14. Think Test Code
Think Code
Debug!!!

15. In reality
Think Test Code

16. TDD vs. debugging only
Shorter feedback cycle
Reusable test suite
Code instead of pen and paper
Genuine feeling of completeness
Predictability

17. I spend too
much time
writing tests.
I would have
spent this time
anyway.

18. It doesn’t apply
exactly to my
case.

19. Legacy code

20. Front-end

21. Embedded
systems

22. It doesn’t apply
exactly to my
case.
There’s a fair
chance my case
is not unique.

23. I’m new to the
technology,
I can’t test what
I don’t know.

24. It’s OK to use a debugger
It’s OK to go back and forth

25. Test is a hypothesis
you can prove on the spot.

26. I’m new to the
technology,
I can’t test what
I don’t know.
TDD in fact
helps me learn.

27. I have to modify
the code too
often, my tests
become waste.

28. Think Test Code Refactor

29. Think Test Code Refactor

30. I have to modify
the code too
often, my tests
become waste.
Code without
tests is non-existing
to me.

31. My project is
too agile, don’t
have time for
tests!
Well…

33. Requirements Waterfall
Design
Implementation
Verification
Maintenance

35. Agile
Requirements
Design
Implementation
Verification
Maintenance
Requirements
Design
Implementation
Verification
Maintenance
Requirements
Design
Implementation
Verification
Maintenance

36. My project is
too agile, don’t
have time for
tests!
I use TDD to
build in quality
into my code.

37. Driven
Test Development

38. TDD is a way to
prepare your
workplace and
keep it safe
© johnjazz

39. There strategy
And there’s
execution
And execution is
hard

41. http://kirbarn.blogpost.com
kiryl.baranoshnik@gmail.com
@kirbarn

42. References
Ten Years Of Test Driven Development
Why does Kent Beck refer to the "rediscovery" of test-driven development? (Quora)
Waterfall model (Wikipedia)
JQuery

43. Books
"Extreme Programming Explained: Embrace Change" by Kent Beck, Cynthia Andres
"Test Driven Development: By Example" by Kent Beck
"Working Effectively with Legacy Code" by Michael C. Feathers
"Test Driven Development for Embedded C" by James W. Grenning

44. Image sources
http://commons.wikimedia.org/wiki/File:Kent_Beck_no_Workshop_Mapping_XP.jpg
http://www.freeimages.com/photo/903964
http://commons.wikimedia.org/wiki/File:Punched_card.jpg
http://www.computerhistory.org/revolution/punched-cards/2/4/40
http://wall.alphacoders.com/big.php?i=62375
http://m.pegitboard.com/pin/b0b39cd746fcdabcc1000acff560051b
https://ru.wikipedia.org/wiki/Keep_Calm_and_Carry_On#mediaviewer/File:Keep_Calm_and_
Carry_On_Poster.svg
http://www.belconsole.by/Tematicheskie_razdely/strategii/starcraft_ii_heart_of_the_swarm/
starcraft_ii_heart_of_the_swarm_dopolnenie_pc_jewel_/