Behat Tests: Automated Acceptance Testing for Drupal

Behat implements the Gherkin syntax: tests are written as scenarios in Given-When-Then form. "Given I am logged in as an editor, When I create a new article, Then I see the success message."

These scenarios are readable for all project stakeholders — not just developers. Product owners, project managers, and editors immediately understand what is being tested.

The Drupal Extension for Behat comes with pre-built step definitions: create users, log in, create content, check regions, and fill out forms.

Login and permissions. Test whether different roles see the right pages and can perform the right actions. An administrator sees different options than an editor.

Content workflows. Creating, editing, approving, and deleting content — automatically verified after each deployment.

Forms. Contact forms, application forms, and other input masks are tested for correct validation and processing.

Multilingual. Test whether language switching, URL aliases, and translated content work correctly.

Behat tests deliver their full value when they run automatically on every code push. In the CI/CD pipeline, a Drupal test instance is built, the Behat suite is executed, and the result is reported. Failed tests prevent deployment — errors do not reach production.

arocom implements Behat tests as part of the development methodology. The Future Check evaluates the quality assurance of your platform. From 2,500 EUR plus VAT, creditable toward the follow-up project.