Cucumber

An Automated Functional Acceptance Testing Management system.

Helps in speeding up the work of having Automated Functional Acceptance Testing for products to ship websites in a swift way.

We LOVE to help with:

• Setup of Automated Functional Testing configurations for projects.
• Writing Cucumber descriptions, Gherkin scripts for web apps.
• Development of webship-js using Playwright and Cucumber-js, with custom and advanced general step definitions.
• Tests run headless in GitLab CI, and locally with DDEV. Playwright ships its own browsers, so there is no Selenium server or web-driver setup involved.

Automated Tests, Executable specifications.

Source of Truth

For many teams, they become the definitive source of truth as to what the system does. Having a single place to go for this information saves a lot of time that is often wasted trying to keep requirements documents, tests, and code all in sync. It also helps to build trust within the team, because different parts of the team no longer have their own personal versions of the truth.

Living Documentation

Cucumber tests share the benefit of traditional specification documents in that they can be written and read by business stakeholders. Still, they have a distinct advantage in that you can give them to a computer at any time to tell you how accurate they are. In practice, this means that your documentation, rather than being something that’s written once and then gradually becomes outdated, becomes a living document that reflects the true state of the project.

To install Cucumber 12.0.x run these commands:

mkdir my-site && cd my-site
ddev config --project-type=drupal --docroot=web
ddev start
ddev composer create-project drupal/cucumber_project:~12.0
ddev drush site:install cucumber -y
ddev launch

Running drush directly outside DDEV works too, at bin/drush, since the profile sets bin-dir.

Cucumber 12.0.x supports Drupal ^11.4 || ^12, and is built and tested on Drupal 11.4 with PHP 8.4.