After setting up a test project using the drupal extension, issuing the command:

bin/behat -di

provides an easy to read extended description for the step definitions included from the Mink Extension (which the Drupal Extension extends) and for a few of the step definitions, but not all.

Better definitions in the doc blocks need to be added to improve the usability of this extension. For example, I would like to be able to hand off a listing of available step definitions to a project manager so that he/she can use those definitions in client meetings when user stories are being fleshed out and acceptance tests are being crafted with the client. Right now, I get pretty good definitions related to the Mink Extension steps, and not so good definitions related to the Drupal Extension steps.

This is a low hanging fruit improvement that can drastically improve the usability of project workflow by reducing unnecessary rewording of acceptance test criteria by the developer team, allowing us to focus on writing the tests for the acceptance criteria not otherwise covered by the Drupal Extension or the Mink Extension, rather than rewording the acceptance criteria and having to revisit those with the client.

I'm happy to take this on -- should I start with the 2.0-dev branch, or the 1.0-dev branch? I'm currently actively using the 1.0 branch since it's has the most recent stable release.

Comments

jhedstrom’s picture

The master branch should be targeted for such work. It is currently slated to be 2.0 (or I might jump it to 3.0 since it is Behat 3 compatible).

jhedstrom’s picture

Status: Active » Closed (works as designed)

Closing for now. The master branch has extended info added for most step definitions already.