• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Let's test! @ codemotion 23/03/2013
 

Let's test! @ codemotion 23/03/2013

on

  • 1,687 views

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 ...

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 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.

Statistics

Views

Total Views
1,687
Views on SlideShare
1,340
Embed Views
347

Actions

Likes
2
Downloads
3
Comments
0

6 Embeds 347

http://davidfunaro.com 313
http://ideas.dnsee.com 24
http://flavors.me 5
http://www.linkedin.com 2
https://www.google.com 2
https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Let's test! @ codemotion 23/03/2013 Let's test! @ codemotion 23/03/2013 Presentation Transcript

    • Andrea GiulianoDavid FunaroLet’s test! #code10 #letstest
    • Let’s test!“Come ho fatto fino ad ora a lavorare senza test?” “Non tornerei mai più indietro!”
    • Let’s test! write code features I manually test allmy code’s functionalities
    • Let’s test!How (most) developers write code today
    • Let’s test! my starting project
    • Let’s test! CHANGESinternal external
    • Let’s test! be honest...
    • Let’s test!Contents... I’m looking forward to waste my code
    • Let’s test!Contents... What happens when something goes wrong
    • Let’s test!Contents...Where can I putmy hands in?
    • Let’s test!Contents... I’ve got the solution! one more patch
    • Let’s test! I madeContents... some mistakes NO FEEDBACK
    • Let’s test! ? ? ?? ? ? ?I’m hopeless
    • Let’s test!Contents... I want to be proud of my code
    • Let’s test!Contents... Automatic Test
    • Let’s test!
    • 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 codedon’t waste your timeworking software over comprehensive documentation
    • Let’s test!How many kinds of test exists? Unit Functional Integration more...
    • Let’s test!we want short feedback!
    • Let’s test! 1 stress = # tests
    • Let’s test!Ok, let’s try!I want to write a test for my code
    • Let’s test! Sounds good...Contents... ...but one day
    • Let’s test!Contents... How can I test this? coupling dependencies
    • Let’s test! I don’t now so I DON’T test
    • 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
    • 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
    • Let’s test!Test Driven DevelopmentTest-driven development is less and more writing testfirst...but TDD is about designTest-driven development is a way of managing fearduring programming
    • 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
    • Let’s test! write a test
    • Let’s test!it fails! write a test
    • Let’s test!it fails! write a test make it works
    • Let’s test!it fails! write a test awesome make it works it’s green!
    • Let’s test!it fails! write a test awesome make it works it’s green! do refactor
    • Let’s test!it fails! write a test awesome make it works it’s green! do refactor
    • 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
    • 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
    • Let’s test! What about legacy code?Test new functionalitiesTest old functionalities starting from bugs
    • Let’s test!DEMO
    • Let’s test! Thanks! Questions?Andrea Giuliano David Funaro@bit_shark @ingdavidinoandreagiuliano.it davidfunaro.com