Bug in behat 3.4.0 - No specifications found at path(s), This might be because of incorrect paths configuration in your `suites`.

in #behat7 years ago (edited)

If anyone comes across this bug https://github.com/Behat/Behat/issues/1076

                                                                                                                                            
  [Behat\Testwork\Tester\Exception\WrongPathsException]                                                                                     
  No specifications found at path(s) someFeatureTest.feature. This might be because of incorrect paths configuration in your `suites`.  

(I couldn't run a single behat test - turns out it happens only on PhpStorm), then the solution to that is:

1

"On a side note, I was able to run tests again from PhpStorm after in the Run/Debug configuration 
I set the *Custom working directory* option (in the default configuration for Behat) to the directory in which
behat.yml lives (it needs to align with whatever in Behat is %paths.base%)."

2

Make sure that the test that you're running is not filtered by

      filters:
        tags: '~@skipped'

in the behat.yml (directly under a suite definition)

Remove @skipped from your test annotations

3
Some also suggested to:

Remove Gherkin cache contents : /tmp/behat_gherkin_cache/
And set gherking cache to default : ~

default:
  gherkin:
    cache: ~

This happens on behat 3.4.x, which we have now, previously we had 3.3.0 where this problem did not occur for me (I have PhpStorm 2016.2.2)