Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There's no issue with running bin/behat -di or bin/behat --dry-run on its own, but once it is affiliated with a Drupal directory, it's no longer possible to run these commands, which are independent of the Drupal instance. As a non-developer, it's a real pain to have to build the whole install if you want to add new scenarios or modify scenarios and ensure they're executable. Alternatively, commenting out the relevant lines behat.yml file to is only a makeshift solution.
Let me know if you need any further details!
Comment | File | Size | Author |
---|---|---|---|
Screen Shot 2013-08-12 at 10.46.45 AM.png | 15.52 KB | heyitspython |
Comments
Comment #1
Frank Ralf CreditAttribution: Frank Ralf commentedJust inserting the screenshot directly ;-)
And something for the search engines to read:
Comment #2
jhedstromIf you remove reference to the Drupal driver from
behat.yml
:and just leave
blackbox:~
, you can get a list of steps.That isn't ideal, but workable. Leaving open until this can be properly resolved.