Yay! Mocks!

Discussion about usage of test-doubles in driving design

Transcript

1. Tuesday, June 26, 2012
2. YAY! Mocks! @coreyhaines Nordicy RubyConf 2012 Tuesday, June 26, 2012
3. YAY! Test Doubles! @coreyhaines Nordicy RubyConf 2012 Tuesday, June 26, 2012
4. Zak! Tuesday, June 26, 2012
5. Test-Driven Development Tuesday, June 26, 2012
6. Object-Oriented is about messages Tuesday, June 26, 2012
7. Object-Oriented is about interactions Tuesday, June 26, 2012
8. Object-Oriented is about services Tuesday, June 26, 2012
9. Roles vs Things Tuesday, June 26, 2012
10. Test-Driven Development Tuesday, June 26, 2012
11. Test-First Development Tuesday, June 26, 2012
12. Test-Driven vs Test-First Tuesday, June 26, 2012
13. Reaction to pain Tuesday, June 26, 2012
14. Test-First -> Change Tests Tuesday, June 26, 2012
15. Test-Driven -> Change Design Tuesday, June 26, 2012
16. Test-Doubles Often Highlight Pain Tuesday, June 26, 2012
17. Zak! Tuesday, June 26, 2012
18. Examples Tuesday, June 26, 2012
19. Showing list of Coderetreats for today Tuesday, June 26, 2012
20. You have to change your test When you change this hash Tuesday, June 26, 2012
21. Feels Very Fragile Tuesday, June 26, 2012
22. PAIN! Tuesday, June 26, 2012
23. Discomfort! Tuesday, June 26, 2012
24. Tuesday, June 26, 2012
25. Why is this information relevant to the controller? Tuesday, June 26, 2012
26. Bypassing Layers Tuesday, June 26, 2012
27. This is odd Tuesday, June 26, 2012
28. Controller calling database? Tuesday, June 26, 2012
29. Controller should know ‘WHAT’ not ‘HOW’ Tuesday, June 26, 2012
30. Better to insert a layer Tuesday, June 26, 2012
31. Controller Business-Oriented Services DB Tuesday, June 26, 2012
32. What, not How Tuesday, June 26, 2012
33. Better to delegate the How Tuesday, June 26, 2012
34. TDD is about design Tuesday, June 26, 2012
35. Change design, not tests Tuesday, June 26, 2012
36. Focusing on usage Tuesday, June 26, 2012
37. I like Presenters! Tuesday, June 26, 2012
38. Tuesday, June 26, 2012
39. double depending on doubles?? Tuesday, June 26, 2012
40. UGH! Tuesday, June 26, 2012
41. Too much detail at this level? Jumping levels of abstraction? Tuesday, June 26, 2012
42. Change design to fix pain Tuesday, June 26, 2012
43. Simplify our example Tuesday, June 26, 2012
44. Simplify our example Tuesday, June 26, 2012
45. Much simpler, more focused on what the controller needs to know Tuesday, June 26, 2012
46. Tuesday, June 26, 2012
47. TDD is about refactoring Tuesday, June 26, 2012
48. TDD is about refactoring away from discomfort Tuesday, June 26, 2012
49. Changing your design, to fix pain Tuesday, June 26, 2012
50. Test doubles can help highlight and fix pain Tuesday, June 26, 2012
51. Take-Home Challenge Tuesday, June 26, 2012
52. Tuesday, June 26, 2012
53. Coupled Roles Tuesday, June 26, 2012
54. Unnecessary noise Tuesday, June 26, 2012
55. or false positive if yesterday’s or tomorrow’s are not created in database Tuesday, June 26, 2012
56. How to change design to fix this? Tuesday, June 26, 2012
57. Thanks! @coreyhaines Nordicy RubyConf 2012 font inspiration: bit.ly/corey-sans Tuesday, June 26, 2012