Help running existing extension features [#2621426]

What is the correct way to run features contained already in Drupal Extension directories?
I was looking for examples in readthedocs but couldn't find exactly what I want .... intend to add when I sus I'm doing the right thing.

$ bin/behat /Users/iainhouston/Documents/web/BABuild/vendor/drupal/drupal-extension/features/
No scenarios
No steps
0m0.06s (13.75Mb)


                                                                                                                           
  [Behat\Testwork\Tester\Exception\WrongPathsException]                                                                    
  No specifications found at path(s) `/Users/iainhouston/Documents/web/BABuild/vendor/drupal/drupal-extension/features/`.  
                                                                                                                           


behat [-s|--suite SUITE] [-f|--format FORMAT] [-o|--out OUT] [--format-settings FORMAT-SETTINGS] [--init] [--lang LANG] [--name NAME] [--tags TAGS] [--role ROLE] [--story-syntax] [-d|--definitions DEFINITIONS] [--append-snippets] [--no-snippets] [--strict] [--rerun] [--stop-on-failure] [--dry-run] [--] [<paths>]

Comments

Comment #1

23 November 2015 at 15:44

iainH created an issue. See original summary.

Comment #2

jhedstrom

English

Portland, OR

CreditAttribution: jhedstrom at Phase2 commented 23 November 2015 at 17:58

features contained already in Drupal Extension directories

The features contained in the Drupal Extension's features directory are for testing the extension itself. They can be used as an example, but aren't intended to run against real sites. If you do want to run them, the .travis.yml file shows how they are run on Travis CI.

Comment #3

iainH CreditAttribution: iainH as a volunteer commented 24 November 2015 at 09:59

I've been meaning to move my project to Travis CI for some time since it's hosted on GitHub; now that I can see how drupalextension is using it I shall give it proper attention. Many thanks @jhedstrom.