Readable, Executable Requirements: Hands-On

Transcription

1 Readable, Executable Requirements: Hands-On Emily Bache, Bache Consulting & Pagero Insert speaker picture here, no more than 150x150 #esconfs

2

3 Agile Requirements User Story + Conversation + Example = Requirement From Agile Testing by Crispin, Gregory 3

4 ATDD vs BDD vs Spec by Example? Where we choose to call it BDD or ATDD or Specification by Example, we want the same result a shared common understanding of what is to be built to try to build the thing right the first time. -- Janet Gregory /08/atdd-vs-bdd-vsspecification-by-example.html 4

5 Thought Leaders ATDD: Janet Gregory, Lisa Crispin, Markus Gärtner Specification by Example: Gojko Adzic, David Evans BDD: Liz Keogh, Dan North, Chris Matts 5

6 TDD inner & outer loops Write a failing acceptance test Write a failing unit test refactor make the test pass from Growing Object Oriented Software, Guided by Tests by Freeman, Pryce 6

7 TDD won t help you if... You don t know what problem to solve Write a failing unit test refactor make the test pass 7

8 TDD is less useful if... you tend to have a lot of integration errors Write a failing unit test refactor make the test pass 8

9 TDD inner & outer loops Write a failing acceptance test Write a failing unit test Where does this come from? refactor make the test pass from Growing Object Oriented Software, Guided by Tests by Freeman, Pryce 9

10 Agile Requirements Example => Acceptance Test + + User Story Conversation Example = Requirement From Agile Testing by Crispin, Gregory 10

11 Features + User Stories Business Analyst Feature As a <stakeholder> I want <feature> So that <benefit> User Story: A slice through a feature that can be built in 1-2 days 11

12 Agile Requirements + + User Story Conversation Coaching Test = Requirement From Agile Testing by Crispin, Gregory 12

13 Conversation: combine perspectives Developer + other stakeholders Tester Business Analyst The Three Amigos 13

14 A Feature has many Scenarios Feature As a <stakeholder> I want <feature> So that <benefit> Scenario Given <assumption> When <event> Then <outcome> Scenario Given <assumption> When <event> Then <outcome> 14

15 Discovering Scenarios Scenarios are concrete examples discovered through conversation + other stakeholders Developer Tester Business Analyst The Three Amigos 15

16 Feature & Scenario Feature: Free Delivery As an online retailer I want to offer free delivery to customers who place larger orders So that customers spend more money on our site Scenario: Customer qualifies for Free Delivery Given my shopping basket contains 550:- of goods When I place an order Then I am offered free delivery 16

17 Discover Scenarios in Conversation Feature: Free Delivery Scenario: Order is large enough Scenario: Order total is too low Scenario: VIP Customer Scenario: Customer chooses express delivery instead Scenario: Customer has bad payment history Scenario: Customer lives overseas

18 Table format As an online retailer I want to offer free delivery to customers who place larger orders So that customers spend more money on our site Order total Destination Free delivery? 500:- Sweden yes 499:- Sweden no 500:- Norway yes 500:- France no

19 Deliberate Discovery Is there another context in which this event will create a different outcome? Developer Is this the only outcome that matters? Tester Business Analyst Bugs often come from missed scenarios 19

20 Agile Requirements + + User Story Conversation Examples = Requirement From Agile Testing by Crispin, Gregory 20

21 A comprehensive regression test suite? Developer Having the conversation is the most important thing write down the scenarios you need to remember automate the important ones Tester Business Analyst Automation should make things easier to change, not harder! 21

22 Write Code Code & unit tests Scenarios automated as functional tests Collaborate Testers Developers 22

23 Scenario -> Regression test BEFORE code is written, it s a requirement specification AFTER code is written it s a regression test Living Documentation Important to preserve the language & format 23

24 When the code works + other stakeholders Close the feedback loop Check scenarios, do manual testing Continue to run automated regression tests Developer Tester Business Analyst The Three Amigos 24

25 Using Cucumber Feature Step Definitions System Under Test (SUT)

26 Exercise: FizzBuzz Press Start Note your animal 26

27 FizzBuzz - solution 27

28 Exercise: Gilded Rose Existing System Complicated existing Requirements New Requirement

29 GildedRose - solution 29

30 Exercise: Gilded Rose Press Start Note your animal 30