This document discusses the benefits of automated testing and provides an introduction to Behat, an automated testing framework for PHP. It notes that automated tests can catch bugs before they hit production, improve team morale, and allow for faster code iterations. The document then demonstrates how to install and run Behat tests on a Drupal site using Gherkin syntax and scenarios. Resources for learning more about Behat, Mink, and test-driven development are also provided.

1. Do you need automated
testing?
Technology Stylings by @greggles

2. @greggles
● Drupalero for too many years
● Founded this group
● Father of a 4 year old and 1 year old
● I work at CARD.com
● curl -I https://www.card.com
● CARD.com/careers

4. You need tests.
(this is not good marketing)

5. You need to floss.
(this is not good marketing)

6. Only floss the teeth you
want to keep.

7. Only floss the teeth you
want to keep.

8. Only test the code you
want to keep.

9. If you liked it then you
should have put a test on it
Do you like it?

10. Raise your hand if...

12. Why you should write tests:
● Catch bugs before they hit the live site
● Can be a tool for customer acceptance
● Be confident your code covers all cases
● More confidence you can deploy code
○ Faster iterations
● Spend less on manual QA
● Team morale improves
● Wizards will give you their magic wands

13. Why don’t you write tests?

14. Why don’t you write tests?
● It takes too long compared to benefits

15. Why don’t you write tests?
● It takes too long
● Other reasons that don’t matter

16. Bug report:
I went to CARD.com.
I look for the login link.
I should see it.

17. What if….?
Bug report:
I went to CARD.com.
I look for the login link.
I should see it.

18. What if….?
Bug report:
I went to CARD.com.
I look for the login link.
I should see it.
Behat test
Given I go to "https://www.card.com"
When I click "login"
Then I should see "Log in"

19. What if….?
Behat test:
Given I go to "https://www.card.com"
And I click "login"
Then I should see "Log in"

20. A behat “feature”
● Written in Gherkin syntax
● Starts with Benefit, Role, Feature:
○ In order to log in
○ As an anonymous user
○ I need to use the login link from the header

21. A Behat “feature”
● Written in Gherkin syntax
● Starts with Benefit, Role, Feature:
○ In order to log in
○ As an anonymous user
○ I need to use the login link from the header
● Contains Scenarios
● Which have Context, Events, Outcome

22. DEMO TIME

23. What got demoed
● One way to install behat
● One way to run behat
● Running some
● Using goutte driver
● Using drush blackbox driver

24. Anyone can write behat tests

25. Lots of ways to do Behat
● Drupalextension
● composer install
● bin/behat --init
● bin/behat

26. More fun features
Tags!
bin/behat -dl
selenium
junit output and graphing!
travis-ci
etc.!

27. debugging
selenium
printing
editing context

28. Resources
http://behat.org/ http://docs.behat.org
http://www.slideshare.net/jmikola1/pratical-bdd-
with-behat-and-mink
https://drupal.org/project/drupalextension
http://dspeak.com/drupalextension/
https://groups.drupal.org/behat
http://mink.behat.org/

29. http://www.velocitypartners.net/blog/2014/01/28/agile-testing-
the-agile-test-automation-pyramid/
Doing:
Should do:

30. “You Cannot Manage What You Cannot Measure” - Bill Hewlett

31. Remember: Only test the code you want to keep.