1. Andrea Giuliano
David Funaro
Let’s test!
#code10 #letstest

2. Let’s test!
“Come ho fatto fino ad ora a lavorare senza test?”
“Non tornerei mai più indietro!”

3. Let’s test!
write code features
I manually test all
my code’s functionalities

4. Let’s test!
How (most) developers
write code today

5. Let’s test!
my starting project

6. Let’s test!
CHANGES
internal external

7. Let’s test!
be honest...

8. Let’s test!
Contents...
I’m looking forward
to waste my code

9. Let’s test!
Contents...
What happens when
something goes wrong

10. Let’s test!
Contents...
Where can I put
my hands in?

11. Let’s test!
Contents... I’ve got the
solution!
one more patch

12. Let’s test!
I made
Contents...
some mistakes
NO FEEDBACK

13. Let’s test!
? ? ?
?
?
?
?
I’m hopeless

14. Let’s test!
Contents...
I want to be proud
of my code

15. Let’s test!
Contents...
Automatic Test

16. Let’s test!

17. Let’s test!
Why automatic tests?
progressive input growth
tests as documentation
easier to alter code
no fear
feedback understand HOW code works
easy to run confidence in your code
don’t waste your time
working software over comprehensive documentation

18. Let’s test!
How many kinds of test exists?
Unit
Functional
Integration
more...

19. Let’s test!
we want short feedback!

20. Let’s test!
1
stress =
# tests

21. Let’s test!
Ok, let’s try!
I want to write a test for my code

22. Let’s test!
Sounds good...
Contents...
...but one day

23. Let’s test!
Contents...
How can I test this?
coupling dependencies

24. Let’s test!
I don’t now so I DON’T test

25. Let’s test!
Clean code that works cit. Ron Jeffries
predictable way to develop
learn all of the lessons that the code has to teach you
improve the lives of the users of your software
let your teammates count on you, and you on them
feel good to write code

26. Let’s test!
How do we get to clean code that works?
Many forces drive us away from clean code
and even from clean code that works

27. Let’s test!
Test Driven Development
Test-driven development is less and more writing test
first...but TDD is about design
Test-driven development is a way of managing fear
during programming

28. Let’s test!
our tasks feature #1
feature #2
feature #3
Red: write a little test that doesn’t work
Green: make the test work quickly
Refactor: eliminate all the duplication created in merely getting the test to work

29. Let’s test!
write a test

30. Let’s test!
it fails! write a test

31. Let’s test!
it fails! write a test
make it works

32. Let’s test!
it fails! write a test
awesome
make it works
it’s green!

33. Let’s test!
it fails! write a test
awesome
make it works
it’s green!
do refactor

34. Let’s test!
it fails! write a test
awesome
make it works
it’s green!
do refactor

35. Let’s test!
what are the benefits?
improve quality of your code
behaviours’ verification
coverage functionality
test as documentation collaborative working
long term maintainability
very short time feedback about bugs
QA from reactive to proactive

36. Let’s test!
ok, it’s cool but my resources are limited
I want to be cheap
I want to be fast
I want to be good

37. Let’s test!
What about legacy code?
Test new functionalities
Test old functionalities starting from bugs

38. Let’s test!
DEMO

39. Let’s test!
Thanks!
Questions?
Andrea Giuliano David Funaro
@bit_shark @ingdavidino
andreagiuliano.it davidfunaro.com