Introduzione al TDD @ Milano XPUG 21/9/2016

Le slide usate durante l'incontro

Transcript

1. Introduzione al TDD XPUG Milano 21 settembre 2016 Andrea Francia http://andreafrancia.it
2. Perché ci interessa il TDD? chiedere al pubblico
3. Royce, Winston (1970), "Managing the Development of Large Software Systems" (PDF), Proceedings of IEEE WESCON, 26 (August): 1–9
4. Kent Beck. 1999. Extreme Programming Explained: Embrace Change
5. What if? Kent Beck. 1999. Extreme Programming Explained: Embrace Change
9. Come si fa? chiedere al pubblico
10. http://ronjeffries.com/xprog/what-is-extreme-programming/
11. Alla base del TDD 1.write a test 2.watch it fail 3.make it pass 4.repeat
12. Example: calculator
22. Example: file name extension
27. Alla base del TDD 1.write a test 2.watch it fail 3.make it pass 4.repeat
28. Three Rules of TDD 1.You can’t write any production code unless is to make green a red test 2.You can’t add more code to a test than is sufficient to make it red 3.You can’t write more production code than is sufficient to make the test green http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
29. C’è altro?
32. http://agileinaflash.blogspot.com/2009/02/red-green-refactor.html Refactoring (def): improving design without changing its observable behavior. Esiste anche il Refactor!
33. Simple Design 1. Runs all the tests 2. It’s not redundant (no duplication) 3. Expresses every idea that we need to express 4. It’s small in this order http://c2.com/cgi/wiki?XpSimplicityRules
34. Altro? • Architettura esagonale • Strategie di Testing • Testare codice legacy • …
35. Esercizi
36. Leap year https://github.com/garora/TDD-Katas
37. The FizzBuzz Game 1, 2, Fizz!, 4, Buzz!, Fizz!, 7, 8, Fizz!, Buzz!, 11, Fizz!, 13, 14, FizzBuzz!, 16, 17, Fizz!... If the number is a multiple of 3, say “Fizz” If it is a multiple of 5, say “Buzz” If it is a multiple of 3 and 5, say “FizzBuzz” Otherwise, just say the number. Matteo Vaccari Open/Closed Principle Dojo
 http://www.slideshare.net/xpmatteo/20101125-ocpxpday
38. Grazie! Se siete interessati ad approfondire l’argomento o se volete farmi domande potete scrivermi a:
39. Extra
40. What is a good
    unit test?
41. A good unit test… •should run fast •should help localize problems Working Effectively with Legacy Code - Michael Feathers
42. What is not unit test? A test is not a unit test if: 1.It talks to a database. 2.It communicates across a network. 3.It touches the file system. 4.Requires some manual set-up Working Effectively with Legacy Code - Michael Feathers
43. What is not unit test? A test is not a unit test if: 1.It talks to a database. 2.It communicates across a network. 3.It touches the file system. 4.Requires some manual set-up Working Effectively with Legacy Code - Michael Feathers