Passing a directory, file or file:line_number to behat fails about behat HOT 10 CLOSED

This seems to be related to the relative path. If the argument passed is a full path, behat works as expected:

$ behat `pwd`/features/sales_pages.feature:9
[...]
1 scenario (1 failed)
3 steps (1 passed, 1 skipped, 1 failed)
0m0.31s

from behat.

That's strange!

everzet@evermac: ~/Devel/github/php/Behat/Behat
⚡ behat --version
Behat version 1.1.4

everzet@evermac: ~/Devel/github/php/Behat/Behat
⚡ behat features/result_types.feature          
..................................

6 scenarios (6 passed)
34 steps (34 passed)
0m2.244s

everzet@evermac: ~/Devel/github/php/Behat/Behat
⚡ behat features/result_types.feature:193          
.....

1 scenario (1 passed)
5 steps (5 passed)
0m0.436s

from behat.

Show me your behat.yml if you have one.

from behat.

$ cat behat.yml 
default:
    environment:
        parameters:
            start_url: http://www.example.com/
imports:
    - mink/behat.yml

from behat.

Adding some debug statement in the locateFeaturesPaths function shows that the current working directory changes:

           $featuresPath   = $matches[1];                                  
            $lineFilter     = ':' . $matches[2];                            
+          var_dump(getcwd()) . "\n";

The current working directory is changed to:

string(23) "/tmp/pharextract/goutte"

from behat.

Ok. Cool. you've found a bug!
Something changing path in your configuration.

from behat.

Given that the current working directory is related to goutte, I'd guess it's related to mink.

from behat.

Does it helped?

from behat.

Yes. The patch fixes the issue. Thanks!

from behat.

After further testing it seems that the commit fixes the use cases where a relative directory and relative file are given as arguments. The use case where a specific scenario is given still fails. See issue #26 for more information.

from behat.