Behat è nato per semplificare il processo di accettazione da parte del cliente: per evitare ambiguità si realizza un test automatico (leggibile anche da chi non ha competenze tecniche) la cui esecuzione con successo garantisce che le specifiche siano rispettate. L'integrazione di Behat nel processo di sviluppo Drupal permette tuttavia di andare ben oltre: si può usare Behat per condividere le specifiche con il cliente, per guidare lo sviluppo (scrivendo il test prima del codice), per assistere il debug (usando uno scenario per popolare una situazione di errore ripetibile) e persino per migrare un sito da Drupal 7 a Drupal 8 (codificando il comportamento del sito in una serie di test che vengono poi usati come base per lo sviluppo del nuovo sito). Per tutti gli scenari descritti vedremo esempi basati sull'esperienza di Nuvole. di Andrea Pescetti

1. Behat for Drupal
Automated tests and much more
Andrea Pescetti
andrea@nuvole.org
Fabian Bircher
fabian@nuvole.org
Antonio De Marco
antonio@nuvole.org
web: nuvole.org twitter: @nuvoleweb

3. 🎯
Our experience
Nuvole is a 100% Drupal company.
Projects: Drupal 8 websites, mostly in the high-profile range.
Clients: International organizations in the US and Europe.
Team: Distributed in 4 European countries - small and agile.

4. 
Behat: an overview
A generic tool for PHP (not just Drupal).
Focus: behavior-driven development (BDD).
In plain English: a way for developers and business to agree on
project specifications that can be validated automatically.
Or, in other words, a way to use machine-readable user stories.

5. 🔍
Behat: basic example
Feature: Users
Scenario: Visitors can access the login form
Given I am not logged in
When I visit "/user"
Then I should see "Username"
And I should see "Password"

6. 📚
Gherkin: Scenario Background
Feature: Users
Background:
Given users:
| name | mail | pass |
| testing | testing@example.com | pass |
Scenario: Users can login
Given I am not logged in
When I visit "/user"
Then I should see "Username"
When I enter "testing" for "Username"
And I enter "pass" for "Password"
And I press the "Log in" button
Then I should see the link "View"
And I should see the link "Edit"

7. 📚
Gherkin: Scenario Outline
Scenario Outline: Ordinary users cannot create content
Given I am logged in as "testing"
And I visit "/node/add/<type>"
Then I should not see "Create"
Examples:
| type |
| document |
| news |

8. 
Drupal Behat: Built-in steps
Compact format (list):
$ behat --definitions l
Extended format (info):
$ behat --definitions i

9. 
Custom steps
New steps for Behat can easily be added when needed by
providing custom Behat Contexts.
Just write the test in Gherkin as if the custom step existed.
Behat will give you a stub for the step code!

10. 👑
Behat: best practices
Behat will clean up added users/content after use.
But the database after a Behat run should be considered "dirty".
Backup first if needed.
Never run in production.

11. 👑
Behat: clean-room or real-life?
Maintain a set of tests that are supposed to run on a freshly
installed site.
Maintain a set of tests that are supposed to run on any site state,
including a snapshot of the current production database.
Tags can help to discriminate such tests.

12. 👑
Behat for speci cations
Gherkin is readable (and almost writable) by the business -
localized variants available too.
Well-written Behat tests give you a way for encoding and testing
site specifications.
This can be reused for a site manual/documentation later.
You get to decide the level of coverage!

13. 👑
Behat for development
Write the test first and run it.
It will fail due to missing steps or code (or it doesn't, and you know
the test is incomplete!).
Develop missing steps and code, run until green.
Bonus: you know that the test is actually good.

14. 👑
Behat for regression testing
Update core and modules.
Site still working? Security patch brough a new permission to be
configured?
Run the full test suite and ensure everything is OK.
If not, you can even git bisect until you find the problematic
commit.

15. 👑
Site migration
Example: convert a Drupal 7 site to a (new) Drupal 8 site.
We want to test proper implementation of functionality (not
content migration).
Encode the current functionality in Behat tests that run
successfully on the D7 site.
Use them (the same files) as a basis for the D8 development.
End of the "It used to work like this" headaches!

16. nuvole.org @nuvoleweb