Let's test!

Scrivere codice pulito che funzioni.Pur sembrando un'apparente contraddizione che si cela nelle difficoltà della programmazione,lo sviluppo guidato dai test risponde a questa sfida con un paradosso:scrivere test prima dell'implementazione. Lo sviluppo software guidato dai test è una pratica della metodologia Agile che elimina le paure nella scrittura di codice e porta gli sviluppatori ad incrementare drasticamente la qualità delle loro applicazioni. Durante il talk verrà mostrato come l'approccio alla pratica cambi il proprio modo di programmare,rendendolo più divertente,affidabile e proficuo.

Transcript

1. David Funaro Let’s test! Andrea Giuliano #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! I manually test all my code’s functionalities write code features
4. Let’s test! How (most) developers write code today
5. my starting project Let’s test!
6. CHANGES Let’s test! internal external
7. be honest... Let’s test!
8. Contents... Let’s test! I’m looking forward to waste my code
9. Contents... Let’s test! What happens when something goes wrong
10. Contents... Let’s test! Where can I put my hands in?
11. Contents... Let’s test! one more patch I’ve got the solution!
12. Contents... Let’s test! I made some mistakes NO FEEDBACK
13. Let’s test! ? ? ? ? ? ? ? I’m hopeless
14. Contents... Let’s test! I want to be proud of my code
15. Contents... Let’s test! Automatic Test
16. Let’s test!
17. Why automatic tests? Let’s test! confidence in your code progressive input growth no fear tests as documentation easier to alter code understand HOW code works working software over comprehensive documentation easy to run don’t waste your time feedback
18. How many kinds of test exists? Unit Functional Integration more... Let’s test!
19. we want short feedback! Let’s test!
20. stress = 1 # tests Let’s test!
21. Ok, let’s try! I want to write a test for my code Let’s test!
22. Contents... Let’s test! Sounds good... ...but one day
23. Contents... Let’s test! How can I test this? coupling dependencies
24. Let’s test! I don’t now so I DON’T test
25. 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 Let’s test!
26. How do we get to clean code that works? Many forces drive us away from clean code and even from clean code that works Let’s test!
27. Test Driven Development Let’s test! 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. our tasks 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 feature #1 feature #2 feature #3 Let’s test!
29. Let’s test! write a test
30. Let’s test! write a test it fails!
31. Let’s test! write a test make it works it fails!
32. Let’s test! write a test make it works it fails! awesome it’s green!
33. Let’s test! write a test make it works do refactor it fails! awesome it’s green!
34. Let’s test! write a test make it works do refactor it fails! awesome it’s green!
35. what are the benefits? improve quality of your code behaviours’ verification coverage functionality test as documentation long term maintainability very short time feedback about bugs collaborative working QA from reactive to proactive Let’s test!
36. ok, it’s cool but my resources are limited I want to be cheap I want to be fast I want to be good Let’s test!
37. What about legacy code? Test new functionalities Test old functionalities starting from bugs Let’s test!
38. DEMO Let’s test!
39. Thanks! Andrea Giuliano @bit_shark andreagiuliano.it David Funaro @ingdavidino davidfunaro.com Questions? Let’s test!