behat

Here's what i'd like to do:

• Include one or more .feature Behat tests in a contributed module
• Have automated tests run with just this module and its dependencies installed
• Optionally include these .feature Behat tests from the module when it is included in my site or installation profile automated tests, this time running with the full site installed

As part of my Drupal 8 self-learning, I created a module called BeEdit which is a Behat editor suitable for non-technical users. It allows someone to create, edit and run Behat tests from the Drupal web application. You can get it here: https://www.drupal.org/sandbox/jchin1968/2829843

We had some trouble using the Drupal Extension for Behat as scenarios aren't isolated from each other/what's already there, leading to sporadic failures. To counter this, we've put together an extension which causes each scenario to be run on a fresh install, leading to consistent (but slightly slower) builds. We've released it at https://github.com/elifesciences/isolated-drupal-behat-extension.

I need to find a way to create a list of all tests available for non technical gherkin test writers.

What are others using for this?

Hi everyone,
I just wanted to share the slides from the workshop I gave during the European Drupal Days 2015 in Milan(Italy) with this group as I hope someone might find them interesting or useful :)

Here's the link: https://speakerdeck.com/omissis/drupal-7-continuous-integration-workshop....

Feedbacks and/questions are of course welcome!

Hi, I have set up a drupal structure using composer in git to kickstart our drupal development.
In the setup, behat and the DrupalExtension is integrated.

Our team will soon start writing tests for our websites. The generic tests (administrator permissions, Check if homepage works ...) will be put in our main git repo. I was wondering if there are other who have generic tests that are used on every drupal site, and if we could create a main repository ?

Drupal Extension and Contrib

• Jonathan Hedstrom et al worked on bug fixes and several feature additions to version 3 of the Drupal Extension. The Drush driver now allows global options to be passed through for all commands (such as --strict=0 for remote testing on Pantheon).

Hi guys!
I wanted to share something I published today: http://drupalignite.com.
Basically it's a tool and a set of practices to setup a Drupal environment under a full Continuous Integration cycle using some well-known tools as drush, phing, composer and jenkins for the build phase, phpunit and behat for the testing and features and migrate for keeping everything (structure and data) in a code driven development shape.
I published the introduction, the following chapters will be published in the next months!
You can find the code on github: https://github.com/omissis/drupal-ignite

Hello everyone,

I want to introduce you a new project I worked on : Merlin.

https://drupal.org/sandbox/churel/2160815
The global goal is to build automatically drupal components (content type, taxonomy, field etc...) and their BDD tests.