TDD All the Things!
Download as PPTX, PDF12 likes2,973 views
The document outlines an approach to Test-Driven Development (TDD) that applies not only to software but also to personal and organizational processes. It emphasizes writing failing tests to ensure behavior changes, using feedback mechanisms, and implementing agile methodologies to manage complexity. Key concepts include focusing on strengths, separating concerns, and optimizing for discovery while maintaining a safe-to-fail environment.
![public void ShouldWaitForEventsToOccur()
{
// Given an automation element
_window = LaunchPetShopWindow();
var combo = _window.Find<ComboBox>("petFoodInput");
// When we cause a slow event on that element
new Thread(() =>
{
Thread.Sleep(200);
combo.Select("PetFood[Carnivorous]");
}).Start();
// And we wait for the event
var eventOccurred = false;
new Waiter().WaitFor(
combo, (src, e) => {
eventOccurred = true;
return combo.Selection.Equals("PetFood[Carnivorous]");
},
new TimeSpan(0, 0, 1),
(ex) => Assert.Fail(),
new List<AutomationEventWrapper> {
new StructureChangeEvent(TreeScope.Element)});
// Then we should be notified when the event occurs
Assert.IsTrue(eventOccurred);
}](https://image.slidesharecdn.com/tddallthethings-bddlondon-150722124132-lva1-app6892/85/TDD-All-the-Things-6-320.jpg)
![// When we cause a slow event on that element
new Thread(() =>
{
Thread.Sleep(200);
combo.Select("PetFood[Carnivorous]");
}).Start();](https://image.slidesharecdn.com/tddallthethings-bddlondon-150722124132-lva1-app6892/85/TDD-All-the-Things-9-320.jpg)
![// And we wait for the event
var eventOccurred = false;
new Waiter().WaitFor(combo, (src, e) =>
{
eventOccurred = true;
return combo.Selection.Equals(
"PetFood[Carnivorous]");
}, new TimeSpan(0, 0, 1),
(ex) => Assert.Fail(),
new List<AutomationEventWrapper> {
new StructureChangeEvent(
TreeScope.Element)});](https://image.slidesharecdn.com/tddallthethings-bddlondon-150722124132-lva1-app6892/85/TDD-All-the-Things-10-320.jpg)
TDD All the Things!
- 2. An Introduction to TDD How to TDD People! An Introduction to Cynefin Refactoring People and Life Test-Driven Experiments
- 5. public bool WaitFor(AutomationElementWrapper element, SomethingToWaitFor check, TimeSpan timeout, FailureToHappenHandler failureHandler, IEnumerable<AutomationEventWrapper> events) { Monitor.Enter(_waitingRoom); _triggeringEvent = null; DateTime started = DateTime.Now; var handlerRemovers = AddPulsingHandlers(events, element); bool checkPassed = true; while (!check(element, _triggeringEvent) && DateTime.Now.Subtract(started).CompareTo(timeout) < 0) { checkPassed = false; Monitor.Wait(_waitingRoom, timeout); } Monitor.Exit(_waitingRoom); ClearPulsingHandlers(handlerRemovers); if (!checkPassed && !check(element, null)) { failureHandler(element); return false; } return true; }
- 6. public void ShouldWaitForEventsToOccur() { // Given an automation element _window = LaunchPetShopWindow(); var combo = _window.Find<ComboBox>("petFoodInput"); // When we cause a slow event on that element new Thread(() => { Thread.Sleep(200); combo.Select("PetFood[Carnivorous]"); }).Start(); // And we wait for the event var eventOccurred = false; new Waiter().WaitFor( combo, (src, e) => { eventOccurred = true; return combo.Selection.Equals("PetFood[Carnivorous]"); }, new TimeSpan(0, 0, 1), (ex) => Assert.Fail(), new List<AutomationEventWrapper> { new StructureChangeEvent(TreeScope.Element)}); // Then we should be notified when the event occurs Assert.IsTrue(eventOccurred); }
- 8. // Given an automation element _window = LaunchPetShopWindow(); var combo = _window.Find<ComboBox>("petFoodInput");
- 9. // When we cause a slow event on that element new Thread(() => { Thread.Sleep(200); combo.Select("PetFood[Carnivorous]"); }).Start();
- 10. // And we wait for the event var eventOccurred = false; new Waiter().WaitFor(combo, (src, e) => { eventOccurred = true; return combo.Selection.Equals( "PetFood[Carnivorous]"); }, new TimeSpan(0, 0, 1), (ex) => Assert.Fail(), new List<AutomationEventWrapper> { new StructureChangeEvent( TreeScope.Element)});
- 11. // Then we should be notified // when the event occurs Assert.IsTrue(eventOccurred);
- 12. }
- 13. ShouldWaitForEventsToOccur Given an automation element When we cause a slow event on that element And we wait for the event Then we should be notified when the event occurs.
- 14. Examples Given a context When an event happens Then an outcome should occur
- 16. Given a context When an event happens Then an outcome should occur Arrange
- 17. Given a context When an event happens Then an outcome should occur Act
- 18. Given a context When an event happens Then an outcome should occur Assert
- 19. An Example of an Example Given Fred has bought a microwave And the microwave cost £100 When we refund the microwave Then Fred should be refunded £100.
- 20. With Pixies! Given Fred has bought a microwave And the microwave cost £100 When we refund the microwave Then Fred should be refunded £100.
- 21. Let’s TDD a non-software process!
- 23. Let’s TDD a person!
- 25. Feedback Given a context When an event happens Then an outcome should occur Context in which they act
- 26. Feedback Given a context When an event happens Then an outcome should occur Action they take
- 27. Feedback Given a context When an event happens Then an outcome should occur Outcomes
- 29. Number 1 rule of feedback: Anchor what you value!
- 30. Write a failing test Refactor Existing behaviour and anchor what you value! New behaviour
- 31. Write a failing test Refactor Existing behaviour and anchor what you value! Make it pass New behaviour Describe desired behaviour Change the behaviour
- 32. The sandwich model Start with something good Say something bad Finish with something good
- 33. The sandwich model done right Anchor what you value Describe desired behaviour THEN change the behaviour (People can do this bit themselves!)
- 36. Cynefin Obvious ComplicatedComplex Chaotic With thanks to David Snowden and Cognitive Edge
- 37. Cynefin With thanks to David Snowden and Cognitive Edge Disorder
- 38. Cynefin ObviousChaotic With thanks to David Snowden and Cognitive Edge
- 39. Estimating Complexity 5. Nobody has ever done it before 4. Someone outside the org has done it before (probably a competitor) 3. Someone in the company has done it before 2. Someone in the team has done it before 1. We all know how to do it.
- 40. Estimating Complexity 5 4 3 2 1
- 42. Refactoring code Make it run Get the thing that’s new working Make it right Make it fast Separate concerns so you can do more!
- 43. Good code Focus on responsibilities and strengths Is generous on input, strict on output Is easy to understand and work with You can trust clean code.
- 44. Dan North’s “Three Ages” Explore Optimise for Discovery Stabilize Optimize for Repeatability Commoditize Optimize for Efficiency
- 46. Refactoring at scale Horizon 3 Horizon 2 Horizon 1
- 47. Refactoring people Try it out Get the thing that’s new working Focus on strengths Use others for the boring stuff! Separate concerns so you can do more!
- 49. Good people Focus on responsibilities and strengths Are generous in listening, honest in speaking Are easy to understand and work with You can trust good people.
- 50. Horizon 2 fights for budget with Horizon 1. Focusing on strengths fights for time with the boring stuff.
- 51. Trust other people’s code. Trust other people.
- 52. Let’s TDD a people process!
- 53. Let’s TDD a people process (Thanks Tobias!) Given my son’s room is a mess When I ask him to clean it up Then the room should be clean.
- 56. Well-formed outcomes Given my son’s room is a mess When I ask him to clean it up Then the room should be clean.
- 58. GROW Given a context When an event happens Then an outcome should occur Goal
- 59. GROW Given a context When an event happens Then an outcome should occur Reality
- 60. GROW Given a context When an event happens Then an outcome should occur Options / Way Forward
- 62. Real Options Options have value Options expire Never commit early unless you know why
- 65. A Naïve Scenario CONTEXT EVENT OUTCOME Well-formed outcome Event which leads to the outcome Reality. It’s all good, right?
- 66. A Naïve Scenario Given my son’s room is a mess When I ask him to clean it up Then the room should be clean.
- 67. Tom Gilb’s “Mafia Offer” Given my son’s room is a mess When I ask him to clean it up Then the room should be clean And he looks really miserable and hates you?
- 68. Reality. It’s all good, right? Unwanted context CONTEXT EVENT OUTCOME Well-formed outcome Event which leads to the outcome Unwanted Context Unwanted Outcome!
- 69. Unwanted Context Subgoals CONTEXT EVENT OUTCOME Well-formed outcome Event which leads to the outcome Replacement context Unwanted Outcome!
- 70. Given Scenario CONTEXT EVENT OUTCOME Well-formed outcome Event which leads to the outcome Unwanted Context Replacement context EVENT OUTCOME Event which leads to replacement
- 71. Replacing the “Mafia Offer” Given my son knows what “clean” looks like And that it will make me say “Wow!” And be impressed with him Given my son’s room is a mess When I ask him to clean it up Then the room should be clean And he should be happy!
- 72. Changing reality CONTEXT EVENT OUTCOME Well-formed outcome Event which leads to the outcome Unwanted Context Replacement context EVENT Event which leads to the replacement CONTEXT
- 79. Cynefin Obvious ComplicatedComplex Chaotic With thanks to David Snowden and Cognitive Edge Sense Categorize Respond Sense Analyze Respond Probe Sense Respond Act Sense Respond
- 80. Whenever we do anything new we will make discoveries
- 82. How to use scenarios… …in this space.
- 83. Deliberate Discovery Assume ignorance Assume second order ignorance Optimize for discovery
- 84. Real Options Options have value Options expire Never commit early unless you know why
- 87. A Safe-To-Fail Probe has… A way of knowing it’s succeeding A way of knowing it’s failing A way of dampening it A way of amplifying it Coherence
- 88. Coherence A reason for thinking that the probe might have a positive impact Can you think of a scenario in which this experiment succeeds?
- 89. Success Scenarios Given my client has a problem When I suggest a practice to help Then they should be able to deliver software.
- 90. Success Scenarios Given Fred has signed up for Appytastic When we sync to Facebook by default Then Fred’s friends should see how awesome Appytastic is!
- 91. Complementary Success Scenarios Given Fred has signed up for Appytastic When we sync to Facebook by default Then Fred should realise that Appytastic is a really easy way to get content onto Facebook!
- 92. Conflicting Success Scenarios! Given my client has a problem When I suggest a practice to help Then it should help them to think of different practices that really are helpful!
- 93. Failure Scenarios Given my client has a problem And context I don’t know about When I suggest a practice to help Then they’ll think I’m an idiot.
- 94. Failure Scenarios Given Fred has signed up for Appytastic When we sync to Facebook by default Then Fred and Fred’s friends might see that Appytastic has massive privacy issues.
- 95. A way of knowing it’s succeeding My client delivers software. Fred’s friends see how awesome Appytastic is (and sign up).
- 96. Success Metrics! Software is delivered – how quickly? Sign-up rate increases – how much does it increase by?
- 97. A way of knowing it’s failing My client thinks I’m an idiot. Fred and Fred’s friends might see that Appytastic has massive privacy issues.
- 98. Failure metrics! Frowning faces! (but you get what you measure, so measure smiles) Sign-up rate decreases; proportion of positive tweets decreases
- 99. What if a meteor hits our data centre?
- 100. A Safe-To-Fail Probe has… A way of knowing it’s succeeding A way of knowing it’s failing A way of dampening it A way of amplifying it Coherence A way of avoiding failure completely
- 101. Success is guaranteed… …when you’ve done it before …in the same context …with the same requirements …and the same people …and the same technology …and the same market …and you own a time machine.
- 102. Make it cheap to fail. Given my client has a problem And context I don’t know about When I suggest a practice to help Then they’ll think I’m an idiot. (Tell them it’s a way of getting context quickly.)
- 103. Make it cheap to fail Given Fred has signed up for Appytastic When we sync to Facebook by default Then Fred and Fred’s friends might see that Appytastic has massive privacy issues! (Put the flag on the server.)
- 104. Estimating Complexity 5. Nobody has ever done it before 4. Someone outside the org has done it before (probably a competitor) 3. Someone in the company has done it before 2. Someone in the team has done it before 1. We all know how to do it.
- 105. Estimating Complexity 5 4 3 2 1 ComplicatedComplex Obvious
- 106. Familiarity 5 4 3 2 1 Experts familiar with scenariosUnfamiliar scenarios Familiar scenarios Disaster movies!
- 107. Context Questioning Is there a context which, for some event, will give us more options?
- 108. Context Questioning Is there a context which, for some event, will give outcomes that are cheaper to change?
- 109. Warning! Be careful when you’re opening up options that you’re not signalling intent
- 110. The Shallow Dive into Chaos
- 111. Scenarios Anchor the behaviour you value. In unfamiliar scenarios, create options – make it safe-to-fail. Change code; help people change themselves. Some experiments should fail.