Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tdd 2 : opinions, alternatives et compléments

opinions, alternatives et compléments au Test Driven Development

  • Be the first to comment

  • Be the first to like this

Tdd 2 : opinions, alternatives et compléments

  1. 1. Test Driven Development part II opinions, alternatives et compléments
  2. 2. Test Driven Development Test |> Code |> Refactor |> Recommence
  3. 3. Introduction : Opinions
  4. 4. Test-first fundamentalism is like abstinence-only sex ed: An unrealistic, ineffective morality campaign for self-loathing and shaming. - DHH, Tdd is dead, 2014
  5. 5. After all, I may be dead wrong. TDD may not be the equivalent of hand- washing, no matter how much I think it is. - Robert C. Martin, Professionalism and TDD (Reprise) 2014
  6. 6. ...if it doesn't help don't do it... if its help do it. how complicated is this conversation ? - Kent Beck, RailsConf, 2015
  7. 7. Alternatives et technique complémentaires - Responsibility Driven Development - Domain Driven Design - Hammock Driven Development - Acceptance Test Driven Development - Behaviour Driven Development - Readme Driven Development - Pull request Driven Development - Design Driven Development
  8. 8. Agenda 1. Analyse 2. Documente 3. Collabore 4. Code
  9. 9. Théorie : Collaboration
  10. 10. Agenda 1. Analyse 2. Documente 3. Collabore 4. Code
  11. 11. Who drives their car around, banging against the guard rails? - Rich Hickey, Simple made easy, RailsConf 2012
  12. 12. Step Away from the Computer or Hammock-driven Development - Rich Hickey, clojure conj 2010
  13. 13. Business Hammocks
  14. 14. R-mode : non-linear
  15. 15. Hammock Driven Development Analyse [et Documente] |> Dors |> Analyse [et/ou code] |> Recommence
  16. 16. Agenda 1. Analyse 2. Documente 3. Collabore 4. Code
  17. 17. A perfect implementation of the wrong specification is worthless[...] Write your Readme first. - Tom Preston-Werner, 2010 Readme Driven Development
  18. 18. Readme Driven Development Documente |> Code |> Recommence
  19. 19. Pull Request Driven Development Documente |> Ouvre un PR |> Code |> Recommence
  20. 20. A paper sketch is cheap and easy to change. html designs are still relatively simple to modify (or throw out). That's not true of programming. - 37 signals, Getting Real
  21. 21. Interface first Dessine |> Implémente l’interface |> Code |> Recommence
  22. 22. Documentation Driven Development Documente L'API |> Code |> Recommence
  23. 23. Des logiciels opérationnels plus qu’une documentation exhaustive - Manifeste agile 2001
  24. 24. Agenda 1. Analyse 2. Documente 3. Collabore 4. Code
  25. 25. Acceptance test Driven Development + Domain Driven Development = Behaviour Driven Development
  26. 26. Acceptance Test Driven Development : TDD for The Tree Amigos
  27. 27. Domain Driven Design : Ubiquitous Language
  28. 28. Executable Specification
  29. 29. Behaviour Driven Development Collabore |> Automatise |> Code |> Recommence
  30. 30. gherkin la syntaxe du BDD - (Given) some context - (When) some action is carried out - (Then) a particular set of observable consequences should obtain
  31. 31. gherkin la syntaxe du BDD (français) - (Attendu que) Context - (Quand) Une action - (Alors) Le résultat observable
  32. 32. Exemple de scenario en gherkin - attendu que je suis un utilisateur connecté - quand je clique sur le boutton commander - alors je suis redirigé sur la page de commande
  33. 33. Agenda 1. Analyse 2. Documente 3. Collabore 4. Code
  34. 34. Pair Programming
  35. 35. Pair Programming Deux Développeur, un ordinateur
  36. 36. Conducteur
  37. 37. Navigateur
  38. 38. Code review X 10
  39. 39. paired programmers are only 15% slower than two independent individual programmers, but produce 15% fewer bugs - Laurie Williams of the University of Utah in Salt Lake City http://wiki.c2.com/?PairProgramming
  40. 40. Mob Programming
  41. 41. 5 Développeurs, 1 Ordinateur, 10X la productivité
  42. 42. Conversation
  43. 43. Conclusion
  44. 44. Agenda 1. Analyse 2. Documente 3. Collabore 4. Code
  45. 45. Théorie : Collaboration
  46. 46. Collaboration Driven Development Analyse |> Documente |> Collabore |> Code |> Recommence

    Be the first to comment

    Login to see the comments

opinions, alternatives et compléments au Test Driven Development

Views

Total views

376

On Slideshare

0

From embeds

0

Number of embeds

101

Actions

Downloads

0

Shares

0

Comments

0

Likes

0

×