What is the purpose of BDD and how it fits into the Agile development? If you ever wondered what are the benefits of BDD or why should you care about tools like Behat or PhpSpec, this talk will try to guide you through the reasoning and goals of modern Agile practices and tools in PHP.

1. Enabling Agile
Through enabling BDD in PHP projects

2. Who?
BDD Evangelist
!
Creator of Behat, Mink, PhpSpec2,
Prophecy
!
Contributor to Symfony2, Composer
!
Host of the “Elephant in the Room”
podcast

5. BDD

6. – me, this month
BDD is a tool to bring structure
into the agile processes

7. Agile process
Out-of-the box

8. Agile process
Out-of-the box

9. BDD
In the Agile process

10. BDD is the
agile enabler

11. How does it
enable Agile?

12. Requirements
Analysis
Design
Development
Testing
9 months 3 m 2 m 12 m ...
[Royce 1970]

13. Most of the cost in
software development is
in the feedback delay

14. Lets reduce
feedback delay

15. Requirements
Acceptance
Testing
Coding
Refactoring
Weeks Minutes
[Beck & Cunningham 1996-99]

16. Requirements
Acceptance
Testing
?
Coding
Refactoring
[North 2003]
Weeks Minutes

17. Lets clarify
design intentions

18. Requirements
Acceptance
Specification
Implementation
Refactoring
[North 2003]
Weeks Minutes

19. Lets clarify
planning intentions

20. Adding value
What do you
mean?
Specification
Implementation
Refactoring
[North 2003]
Weeks Minutes

21. Adding value
What do you
mean?
Specification
Implementation
Refactoring
[North 2003]

22. Adding value
What do you
mean?
Specification
Implementation
Refactoring
[North 2003]

23. StoryBDD
SpecBDD
[North 2003]
Adding value
What do you
mean?
Specification
Implementation
Refactoring

24. Behat
PhpSpec
[North 2003]
Adding value
What do you
mean?
Specification
Implementation
Refactoring

25. StoryBDD

26. StoryBDD looks like a functional
TDD to the people from the outside
of the BDD community, but
it’s a simple confusion.

27. We are not testing that application
functions as we (developers) expect
it to, but instead we’re testing that
it fulfils our client business needs.

28. Some applications could easily fulfil
developers expectations and still not being
able to cover business needs.

29. You might think about StoryBDD as a
technique to teach your clients about
testing. In reality it's a tool to teach
you about your client business.

31. User-story
• Narrative
• Business rules
• Communication
• Acceptance criteria

32. User-story
• Narrative
• Business rules == AC
• Communication

33. User-story
• Narrative
• Business rules == AC
• Comm == Examples

34. User-story
• Narrative
• Business rules
• Comm == Examples == AC

35. StoryBDD splits every
feature in your project
into the 3 separate layers.

36. Each new layer adds
more information to the
table.

37. 1
2
3
narrative
possible scenarios
scenario details

38. 1
2
3
possible scenarios
scenario details
Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate

39. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate
1
2
3scenario details
Scenario: Successfully authenticating
with correct credentials

40. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate
1
2
3
Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!

41. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate
1
2
3
Example: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!

42. Structure
In the Agile process

43. StoryBDD forces you to
answer questions you did
not know you need to ask.

44. 1. Why?
aka: how to prioritise
my backlog

45. Feature: Authorisation
Why might your users
want this feature?

46. Feature: Authorisation
In order to get access to the shopping history

47. Feature: Authorisation
In order to get access to the shopping history
Who is mostly
interested in this
feature?

48. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer

49. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
How can you help
him get this value?

50. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate

51. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate
benefit
beneficiar

52. Feature: Authorisation
In order to get access to the shopping history
As a frequent buyer
I need to be able to authenticate
Feature: …
In order to …
As a …
I need to …
Feature: …
In order to …
As a …
I need to …
Feature: …
In order to …
As a …
I need to …
benefit
beneficiar

53. SELECT f.* as sprint
FROM ‘/features’ as f
ORDER BY f.role, f.benefit
LIMIT 10
PSEUDOAgileQL

54. 2. What do you
mean?
aka: defining done through examples

55. How much “done” is
“done”?

56. How much of the
feature should be
delivered?

57. Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!

58. Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!
Given defines initial context

59. Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!
When defines a user action (or state transition)

60. Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!
Then defines an expected outcome

61. Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!
And, But add more context, actions or outcomes

62. Scenario: Successfully authenticating
with correct credentials
Given there is a user “everzet” with password “123”
And I am on the login page
When I fill in “username” with “everzet”
And I fill in “password” with “123”
And I press “login”
Then I should see “Hello, everzet”
!

63. 3. When are we
done?
aka: closing feedback loop

65. assertEquals(Your Feature, Your App)

66. Setup
• Dump your sprint features into text files
• Put those text files into the `features/` folder inside
project
• Install behat (via composer or behat.phar)
• Initialize behat test suite by running `bin/behat —init`

67. Context
<?php
!
use BehatBehatContextClosuredContextInterface,
BehatBehatContextTranslatedContextInterface,
BehatBehatContextBehatContext,
BehatBehatExceptionPendingException;
use BehatGherkinNodePyStringNode,
BehatGherkinNodeTableNode;
!
class FeatureContext extends BehatContext
{
}

68. First run
$> bin/behat
...
You can implement step definitions for undefined steps with these snippets:
!
/**
* @Then I should see :arg1
*/
public function iShouldSee($arg1)
{
throw new PendingException();
}
...

69. Append snippets
$> bin/behat --append-snippets

70. Feedback loop
$> bin/behat
!
Feature: registration
in order to maintain my shopping history
as a site visitor
i need to be able to register on this site
!
Scenario: Successful registration when visitor provides all the required info
Given I am on the homepage
TODO: write pending definition
When I follow “sign up”
And I fill in registration form
And I submit it
Then I should be successfully registered
And I should be on the homepage again

71. Stories
Examples
Describe
Implement
Design

72. Stories
Examples
Describe
Implement
Design

73. Colour it red.

74. Making it fail
/**
* @Given /^I am on the homepage$/
*/
public function iAmOnTheHomepage()
{
$crawler = new SomeCrawlerLibCrawler();
$crawler->goto(“http://localhost:8080/”);
if (200 !== $crawler->getCurrentStatusCode())
{
throw new RuntimeException(‘Can not open homepage’);
}
}

75. Making it fail
$> bin/behat
!
Feature: registration
in order to maintain my shopping history
as a site visitor
i need to be able to register on this site
!
Scenario: Successful registration when visitor provides all the required info
Given I am on the homepage
Can not open homepage (RuntimeException)
When I follow “sign up”
And I fill in registration form
And I submit it
Then I should be successfully registered
And I should be on the homepage again

76. Stories
Examples
Describe
Implement
Design

77. Change the message
As quickly as you can

78. Change the message
$> bin/behat
!
Feature: registration
in order to maintain my shopping history
as a site visitor
i need to be able to register on this site
!
Scenario: Successful registration when visitor provides all the required info
Given I am on the homepage
Can not open homepage (RuntimeException)
When I follow “sign up”
And I fill in registration form
And I submit it
Then I should be successfully registered
And I should be on the homepage again

79. Change the message
$> bin/behat
!
Feature: registration
in order to maintain my shopping history
as a site visitor
i need to be able to register on this site
!
Scenario: Successful registration when visitor provides all the required info
Given I am on the homepage
Route … not found (FrameworkException)
When I follow “sign up”
And I fill in registration form
And I submit it
Then I should be successfully registered
And I should be on the homepage again

80. Change the message
$> bin/behat
!
Feature: registration
in order to maintain my shopping history
as a site visitor
i need to be able to register on this site
!
Scenario: Successful registration when visitor provides all the required info
Given I am on the homepage
Template … not found (FrameworkException)
When I follow “sign up”
And I fill in registration form
And I submit it
Then I should be successfully registered
And I should be on the homepage again

81. Change the message
$> bin/behat
!
Feature: registration
in order to maintain my shopping history
as a site visitor
i need to be able to register on this site
!
Scenario: Successful registration when visitor provides all the required info
Given I am on the homepage
When I follow “sign up”
TODO: write pending definition
And I fill in registration form
And I submit it
Then I should be successfully registered
And I should be on the homepage again

82. Read more at
behat.org

83. Stories
Examples
Describe
Implement
Design
Spec-BDD

84. Stories
Examples
Describe
Implement
Design
Spec-BDD

85. Stories
Examples
Describe
Implement
Design
Spec-BDD

86. Stories
Examples
Describe
Implement
Design

87. Read more at
phpspec.net

88. That’s all nice
theoretical stuff

90. http://inviqa.com/careers

91. Thank you!