Download to read offline
Uploaded byBrendan Connolly
Test Driven Testing
This document discusses test-driven development (TDD) and testing. It provides guidance on practicing TDD through following three laws: 1) No production code without a failing test, 2) Tests can only be written to the point of failure, and 3) Only write production code to pass a single failing test. It also recommends practicing TDD in cycles, with cycles occurring at the seconds, minutes, and hours level following the red-green-refactor process. Finally, it suggests using testing katas to build skills through repetition of simple testing problems.
Test Driven Testing
- 1.
- 2. 2 What Is TDD? @theBConnolly WhyShould Testers Care?
- 3. Laws to GuideUs 3@theBConnolly
- 4. 1. 4 No production codeunless it is to make a failing unit test pass @theBConnolly
- 5. Software’s a Journey Nota Destination 5 Fastest to Write Fastest to Maintain @theBConnolly
- 6. How Do YouStart Testing? 6@theBConnolly
- 7.
- 8. 1. 8@theBConnolly No testing unlessyou have a defined objective
- 9. Let Testers Beexplorers, 9@theBConnolly But... Manage that exploration as a series of expeditions
- 10. 2. 10 You are notallowed to write any more of a unit test than is sufficient to fail. @theBConnolly
- 11. Directions Vs. AMap 11@theBConnolly
- 12. Narrowly Focused Intentions12@theBConnolly
- 13. 2. 13@theBConnolly Test only enoughto satisfy the objective
- 14. “ Joy comesin sips, not gulps - Sharon Draper 14@theBConnolly
- 15. Break down workinto chunks that that fit into distraction free time boxes.
- 16. 3. 16 Write only enoughproduction code to pass one failing unit test @theBConnolly
- 17. Hierarchy of Values 17 BuildingDiscipline @theBConnolly Test small to Develop small Prioritize for willpower
- 18. 3. 18@theBConnolly No activities outsidethe objective
- 19. Tester Merit Badges 19@theBConnolly You don’thave to justify the value of testers
- 20. Find A Bug? 20@theBConnolly Staywithin the boundaries of intent
- 21. Intent Driven Testing 21@theBConnolly DistractionsFriction Gain speed via Throughput Functionally focused
- 22. Hierarchy of Values 22 BuildDiscipline @theBConnolly Work small to test small The more you do, the more you have to unwind and unpack
- 23.
- 24.
- 25.
- 26. “Figure out whattest will best move your code towards completion. (Take as much time as you need. This is the hardest step for beginners.) -James Shore 26@theBConnolly Think:
- 27.
- 28. “Making a commitat this point will improve your process even more. You will have autonomous chunks of work that are small and easy to understand. -Cecil Williams 28@theBConnolly Commit:
- 29.
- 30.
- 31. Think: 31@theBConnolly Consider the highlevel testing strategy Decide what task to pursue
- 32. Red: 32@theBConnolly Establish clear intentionsand outcomes Decompose your goal
- 33. Green: 33@theBConnolly Stay true toyour charter Take mindful action
- 34. Refactor: 34@theBConnolly Shift from intuitionto data driven Unpack your observations
- 35. Commit: 35@theBConnolly Investigate, Log, Communicate SummarizeActions and Outcomes
- 36. This is hard 36@theBConnolly ChangingHabits Building Discipline
- 37.
- 38. “ A choreographedpattern of movements used to train yourself to the level of muscle memory 38@theBConnolly Kata:
- 39. “ Simple problemsnot production code Short (30-ish minutes) Focus on form not solutions 39@theBConnolly Code Kata’s
- 40.
- 41.
- 42.
- 43.
- 44. “ Apply DifferentHeuristics Different Personas Different Tools 44@theBConnolly Testing Kata’s: Changing it Up
- 45.
- 46. “ Seconds -Follow the 3 Laws 46@theBConnolly Cycles of TDD Minutes - Red, Green, Refactor 10 Minutes - Specific / Generic Cycle http://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfTDD.html
- 47. “As the testsget more specific, the code gets more generic -”Uncle” Bob Martin 47@theBConnolly Specific / Generic Cycle
- 48. “ Seconds -Follow the 3 Laws 48@theBConnolly Cycles of TDD Minutes - Red, Green, Refactor 10 Minutes - Specific / Generic Cycle Hours - Architectural Boundaries http://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfTDD.html
- 49. “ 49@theBConnolly Cycles of TestDriven Testing Minutes - Follow the 3 Laws 30 Minutes-ish - Think, Red, Green, Refactor, Commit Hours-ish - Specific / Generic Cycle
- 50. As testers intentionsget more specific The testers perspective becomes more holistic 50@theBConnolly
- 51. Be Well, Create,Share Connect With Me @theBConnolly brendanconnolly.net |
Editor's Notes
- #5 But there is nothing to test, Forces test first. Solutions tend to grow organically Requirements tell us what software has to do, but its often developer discretion on how those requirements are implemented.
- #6 Organic growth vs. explicit design Designers don’t always end up consumers of their designs. Existing code is read much more often that new code is written
- #8 Sometimes our efforts drift, navigating by gut feelings and intuituions. Its not bad but its good to have a lens to focus our efforts
- #9 TDD isn’t a magic bullet, good patterns can emerge Can have strategy without needing test plan written up front. It’s fine for the first mission to be a scouting mission, consider rules of engagement
- #10 Be free to gather information,
- #11 Clear intent doesn’t mean we aren’t overly ambitious. TDD is like a microcosm of an agile transition. We don’t want to drive decisions by just what we think. Instead force a feedback cycle to drive
- #12 New features are like being in a new place, knowing you need to get somewhere, but your only tool is a wrinkled map. All you really want is someone to give you directions, but thats a lot of trust and risk You are making decisions when yo uknow the least.
- #13 We made a plan, but now we feel compelled to follow that plan Replace the baggage of a plan, a series of distance intervals that result in arriving at the destination
- #14 Planning testing up front introduces the same baggage, sunk costs
- #17 We now treat test and production code as 2 sides of the same coin
- #18 Tests first puts the priority on process over destination The cycle has to feed itself a
- #19 Processing information is a difficult task, multi tasking is impossible.
- #20 We sometimes look for bugs to grant us team credibility. We are looking to justify contributions
- #21 We aren’t bug hunters thats just an artifact Wouldn’t you rather evaluate software on its merits not its flaws Bugs a
- #22 Many dimensions to testing, context shifting, persona bleeds Be active in present in testing rather than a passive
- #23 Put tester willpower requiring tasks first The more we do the more we have to un
- #24 A mantra for devs doing TDD
- #25 Super relatable but where does design step in? It can’t just
- #26 Super relatable but where does design step in? It can’t just