Stories? Scenarios? BDD? Are these just more words in the ever-growing list of jargon that developers have to know? Or are they something more important than new terms to memorise? In this session we'll look at how BDD fits into the software development work-flow, how to tell user stories through features, and what makes a good feature file. These techniques will help to ensure you're writing well designed and tested software that focuses on what the users really want from a system.

1. @Brunty
BEHAVIOUR DRIVEN
DEVELOPMENT & BEHAT
TELLING STORIES THROUGH CODE

2. @Brunty
Senior Software Engineer
Viva IT
@Brunty
@PHPem

3. @Brunty
BEFORE WE TALK
ABOUT BDD

4. @Brunty
TDD VS BDD

5. @Brunty
BDD IS TDD ‘DONE RIGHT’
IT’S OFTEN SAID THAT…

6. @Brunty
TDD IS BUILDING
THE THING RIGHT

7. @Brunty
BDD IS BUILDING
THE RIGHT THING

8. @Brunty
BEHAVIOUR DRIVEN
DEVELOPMENT

9. @Brunty
WE’LL BE LOOKING
AT SCENARIO BDD

10. @Brunty
BDD IS A SECOND-GENERATION, OUTSIDE-IN, PULL-
BASED, MULTIPLE-STAKEHOLDER, MULTIPLE-
SCALE, HIGH-AUTOMATION, AGILE METHODOLOGY.
DAN NORTH
http://dannorth.net/whats-in-a-story/

11. @Brunty
SECOND-GENERATION
BREAK DOWN

12. @Brunty
MULTIPLE-STAKEHOLDER
BREAK DOWN

13. @Brunty
AGILE METHODOLOGY
BREAK DOWN

14. @Brunty
MULTIPLE
STAKEHOLDERS

15. @Brunty
CONVERSATIONS
ARE KEY

16. @Brunty
HAVING
CONVERSATIONS >
CAPTURING
CONVERSATIONS
AUTOMATING
CONVERSATIONS>

17. @Brunty
HAVE CONVERSATIONS
BEFORE YOU START
WRITING CODE

18. @Brunty
CAPTURE THE CONVERSATIONS
SO YOU CAN USE THEM TO
DRIVE DEVELOPMENT

19. @Brunty
BDD IS THE ART OF USING EXAMPLES IN
CONVERSATIONS TO ILLUSTRATE BEHAVIOUR
LIZ KEOGH

20. @Brunty
EXAMPLES ARE
ESSENTIAL

21. @Brunty
SO, HOW DO WE
WORK WITH THIS?

22. @Bruntyhttps://github.com/cucumber/cucumber/wiki/Gherkin
GHERKIN DSL

23. @Brunty
HUMAN READABLE
GHERKIN IS…

24. @Brunty
MULTI-LINGUAL SUPPORT
TOOLS CAN INCLUDE…

25. @Brunty
EN-PIRATE
INCLUDING
https://github.com/Behat/Gherkin/blob/master/i18n.php#L313

26. @Brunty
KEYWORD BASED
GHERKIN IS…

27. @Brunty
LINE ORIENTED
GHERKIN IS…

28. @Brunty
DOCUMENTATION
GHERKIN IS…

29. @Brunty
AUTOMATION
GHERKIN ALLOWS…

30. @Brunty
DEVELOPERS LOVE
AUTOMATION

31. @Brunty
WRITING
STORIES

32. @Brunty
BE DESCRIPTIVE

33. @Brunty
FEATURES ARE
STORIES

34. @Brunty
SINGLE FEATURE
PER FILE

35. @Brunty
Feature:
As a [role]
I want [feature]
So that [benefit]

36. @Brunty
Feature:
In order to [achieve value]
As a [role]
I want [feature]
https://lizkeogh.com/2008/05/14/rip-as-a-i-want-so-that/

37. @Brunty
SCENARIOS

38. @Brunty
SCENARIOS ARE
EXAMPLES

39. @Brunty
EXAMPLES ARE
ESSENTIAL

40. @Brunty
MULTIPLE SCENARIOS
FEATURES CAN HAVE

41. @Brunty
STEPS

42. @Brunty
MULTIPLE STEPS
SCENARIOS HAVE…

43. @Brunty
KEYWORDS

44. @Brunty
GIVEN
PUTS THE SYSTEM IN A KNOWN STATE

45. @Brunty
WHEN
DESCRIBE A KEY ACTION

46. @Brunty
THEN
DESCRIBE AN OBSERVABLE OUTCOME

47. @Brunty
Given I have a “Large T-Shirt” product
When I add a “Large T-Shirt” to my basket
Then I should have a “Large T-Shirt” in my basket

48. @Brunty
AND
THERE’S ALSO…

49. @Brunty
BUT
THERE’S ALSO…

50. @Brunty
Given I have a “Large T-Shirt” product that costs £9.99
And I have an empty basket
And I am a tax-exempt customer
When I add a “Large T-Shirt” to my basket
Then I have a “Large T-Shirt” in my basket
And the basket total should be £9.99
But I do not have tax applied to my order

51. @Brunty
STORY STRUCTURE:
THE MAKEUP OF A FEATURE
FILE

52. @Brunty
Feature: As a customer
I want to be able to add products to my basket
So that I can have a gift for my partner
Scenario: I can add a product to the basket
Given I have a "Large T-Shirt" product
When I add a “Large T-Shirt” to my basket
Then I have a “Large T-Shirt” in my basket
FEATURE

53. @Brunty
SCENARIO
Feature: As a customer
I want to be able to add products to my basket
So that I can have a gift for my partner
Scenario: I can add a product to the basket
Given I have a "Large T-Shirt" product
When I add a “Large T-Shirt” to my basket
Then I have a “Large T-Shirt” in my basket

54. @Brunty
STEP
Feature: As a customer
I want to be able to add products to my basket
So that I can have a gift for my partner
Scenario: I can add a product to the basket
Given I have a "Large T-Shirt" product
When I add a “Large T-Shirt” to my basket
Then I have a “Large T-Shirt” in my basket

55. @Brunty
HOW DO DEVELOPERS
WORK WITH IT?

56. @Brunty
STEP DEFINITIONS

57. @Brunty
Given I have a "Large T-Shirt" product
When I add a “Large T-Shirt” to my basket
Then I have a “Large T-Shirt” in my basket

58. @Brunty
ARGUMENTS

59. @Brunty

60. @Brunty
TRANSFORMERS

61. @Brunty

62. @Brunty

63. @Brunty
TAGS

64. @Brunty

65. @Brunty
HOOKS

66. @Brunty
BEFORE & AFTER SUITES,
FEATURES, SCENARIOS, STEPS
HOOKS

67. @Brunty

68. @Brunty
SUITES &
PROFILES

69. @Brunty
TEST FEATURES WITH
DIFFERENT CONFIGURATIONS
SUITES ALLOW YOU TO…

70. @Brunty
SUITES CAN USE THE SAME FEATURE FILES.
OR SUITES CAN USE DIFFERENT FEATURE
FILES
FOR EXAMPLE:

71. @Brunty
YOU CAN USE THE SAME FEATURE FILE
TO TEST DIFFERENT IMPLEMENTATIONS
WITH SUITES AND TAGS…

72. @Brunty

73. @Brunty

74. @Brunty
YOU CAN HAVE A UI SUITE THAT USES
DIFFERENT STEP DEFINITIONS THAN A
SERVICE / DOMAIN / LOWER LEVEL SUITE
FOR EXAMPLE:

75. @Brunty

76. @Brunty

77. @Brunty
YOU CAN CHANGE IMPLEMENTATION
WITHOUT CHANGING YOUR
DOCUMENTED BUSINESS RULES
WITH SUITES AND TAGS…

78. @Brunty
THIS IS WHERE THE POWER
LIES
I FIND…

79. @Brunty
IMPLEMENTATION CHANGES
MORE FREQUENTLY THAN
BUSINESS RULES

80. @Brunty
WRITING A GOOD
STORY

81. @Brunty
Scenario: I can add a product to my basket
Given I am on the “/product/1” page
When I press “Add to basket”
Then I will see “Playstation 4”
And I will see £250

82. @Brunty
Scenario: I can add a single product to my basket
Given I have a “Playstation 4” that costs £250
When I add the “Playstation 4” to my basket
Then I will have 1 product in my basket
And the basket total will be £250
BETTER STORY

83. @Brunty
Scenario: I can add a product to my basket
Given I am on the “/product/1” page
When I press “Add to basket”
Then I will see “Playstation 4”
And I will see £250
WHAT HAPPENS WHEN THE UI CHANGES TO SAY “ADD TO CART”?

84. @Brunty
DON’T WRITE
IMPLEMENTATION IN
FEATURES

85. @Brunty
DEMO TIME!

86. @Brunty
IN SUMMARY

87. @Brunty
CONVERSATIONS.
CONVERSATIONS.
CONVERSATIONS.
CONVERSATIONS.
CONVERSATIONS.

88. @Brunty
STORIES TOLD BY REAL WORLD EXAMPLES.
USER STORIES AS REQUIREMENTS.
INVOLVE MULTIPLE STAKEHOLDERS.
WRITE FEATURES BEFORE CODE.
WRITE FEATURES WITHOUT IMPLEMENTATION.

89. @Brunty
BEGINNING:
HAVE A CONVERSATION, CAPTURE THAT
CONVERSATION
MIDDLE:
AUTOMATE AND IMPLEMENT THAT CONVERSATION
END:
HAPPY STAKEHOLDERS AND WELL BUILT
SOFTWARE

90. @Brunty
LINKS & READING
https://cucumber.io/docs
https://adamcod.es/2014/05/15/test-doubles-mock-vs-stub.html
https://github.com/cucumber/cucumber/wiki/Gherkin
http://dannorth.net/whats-in-a-story/
http://dannorth.net/introducing-bdd/
http://lizkeogh.com/category/bdd/
http://lizkeogh.com/2014/01/22/using-bdd-with-legacy-systems/
http://inviqa.com/insights/bdd-guide
https://cucumber.io/blog/2015/03/24/single-source-of-truth
https://github.com/Behat/Gherkin/blob/master/i18n.php#L313

91. @Brunty
THANKS FOR
LISTENING

92. @Brunty
@Brunty
@PHPem
matt@mfyu.co.uk
https://joind.in/talk/e7b59