Slides from conference session, given at STPCon & TestingGuild Modeling Testing after principles of TDD

1. Tes Driven
Testin
Brendan Connolly
@theBConnolly
http://brendanconnolly.net

2. 2
What Is TDD?
@theBConnolly
Why Should Testers Care?

3. Laws to Guide Us
3@theBConnolly

4. 1.
4
No production code unless it is to
make a failing unit test pass
@theBConnolly

5. Software’s a Journey
Not a Destination
5
Fastest to Write Fastest to Maintain
@theBConnolly

6. How Do You Start
Testing?
6@theBConnolly

7. Organic Testing?
7@theBConnolly

8. 1.
8@theBConnolly
No testing unless you have a defined
objective

9. Let Testers Be explorers,
9@theBConnolly
But...
Manage that exploration as a series
of expeditions

10. 2.
10
You are not allowed to write any
more of a unit test than is sufficient
to fail.
@theBConnolly

11. Directions Vs. A Map
11@theBConnolly

12. Narrowly Focused Intentions 12@theBConnolly

13. 2.
13@theBConnolly
Test only enough to satisfy the
objective

14. “ Joy comes in sips, not gulps
- Sharon Draper
14@theBConnolly

15. Break down work into chunks that
that fit into distraction free time
boxes.

16. 3.
16
Write only enough production code
to pass one failing unit test
@theBConnolly

17. Hierarchy of Values
17
Building Discipline
@theBConnolly
Test small to Develop small
Prioritize for willpower

18. 3.
18@theBConnolly
No activities outside the
objective

19. Tester Merit Badges
19@theBConnolly
You don’t have to justify the value
of testers

20. Find A Bug?
20@theBConnolly
Stay within
the boundaries of intent

21. Intent Driven Testing
21@theBConnolly
Distractions Friction
Gain speed via Throughput
Functionally focused

22. Hierarchy of Values
22
Build Discipline
@theBConnolly
Work small to test small
The more you do, the more you
have to unwind and unpack

23. 23
Red, Green, Refactor
@theBConnolly

24. 24@theBConnolly

25. 25@theBConnolly
...And Quality Emerges

26. “Figure out what test 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. “
27@theBConnolly

28. “Making a commit at 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. “
29@theBConnolly

30. 30
Test Driven
Testing Mantra
@theBConnolly

31. Think:
31@theBConnolly
Consider the high level testing strategy
Decide what task to pursue

32. Red:
32@theBConnolly
Establish clear intentions and outcomes
Decompose your goal

33. Green:
33@theBConnolly
Stay true to your charter
Take mindful action

34. Refactor:
34@theBConnolly
Shift from intuition to data driven
Unpack your observations

35. Commit:
35@theBConnolly
Investigate, Log, Communicate
Summarize Actions and Outcomes

36. This is hard
36@theBConnolly
Changing Habits
Building Discipline

37. Practice, Practice, Practice
37@theBConnolly

38. “ A choreographed pattern of
movements used to train
yourself to the level of
muscle memory
38@theBConnolly
Kata:

39. “ Simple problems not production code
Short (30-ish minutes)
Focus on form not solutions
39@theBConnolly
Code Kata’s

40. “
40@theBConnolly
Testing Kata’s

41. “
41@theBConnolly
Testing Kata’s: Stapler

42. “
42@theBConnolly
Testing Kata’s:
Pen

43. “
43@theBConnolly
Testing Kata’s:
Search Page

44. “ Apply Different Heuristics
Different Personas
Different Tools
44@theBConnolly
Testing Kata’s: Changing it Up

45. Cycles
45@theBConnolly

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 tests get 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 Test Driven Testing
Minutes - Follow the 3 Laws
30 Minutes-ish - Think, Red, Green,
Refactor, Commit
Hours-ish - Specific / Generic Cycle

50. As testers intentions get more
specific
The testers perspective becomes
more holistic
50@theBConnolly

51. Be Well, Create, Share
Connect With Me
@theBConnolly
brendanconnolly.net
|