Posted by eliza411 on September 6, 2013 at 10:58pm
As I prepare for the Behat + Contrib lab in Prague, I've been kicking around the idea of choosing a module each month that has tricky bits to test and working together in a sandbox to create and review some custom step definitions.
I'm thinking of Media module at the moment, but we could run a poll each month to choose the module for the next, or take turns choosing and managing the sandbox.
I'd love to know if anyone else is interested.

Comments
Sounds good.
You're welcome to attack any of the Examples modules.
It would be great if there were a more direct line of integration with Drupal for BDD, so that the features could be in the modules themselves in a way that would be clear to the uninitiated.
I suppose that's part of what you're addressing in the lab...
Thanks
The Drupal Extension has a mechanism to automatically discover subcontexts provided by modules and make them available to a site's behat tests. Whether a module maintainer would want to take advantage of that and/or be responsible for maintenance is a separate issue, of course.
See http://dspeak.com/drupalextension/subcontexts.html for the technical details.
I love the idea!
Sounds wonderful!
This is really a good idea.
This is really a good idea. I'd love to be involved:)
Start in October
I posted a note in the Media module issue queue to see if there's any interest from maintainers. We can still go forward with tests, of course, since there are still people who need them, but I thought it might be nice if we checked in first.
With Prague coming up, I'm thinking we'll kick this off in October. I'm certainly open to other modules, as well.
Behat tests for Field modules
I would like to introduce behat tests to Double field module. But I did not find any special step definitions to test field types, widget and formatters. Should I implement them myself?
Yes, I think
I think you should write them and contribute to the Drupal Extension project, so any other developer testing its module can use them.
But what you need may be achieved using existing steps, exactly what do you want to test?
I am asking for something
I am asking for something like this:
try and use the existing steps
@Chi I'd try and use the existing steps if you can and see where that takes you initially...
If its too long or bloated or repetitive you can always look to condense / refactor afterwards, where it will be easy to see if you have duplicate step definitions across the things you want to test.
I'm also cross-linking the issue from eliza411 on the media module here - https://drupal.org/node/1026562