Open sserdyuk opened 13 years ago
Thanks a lot for the tip, sserdyuk. I had the same annoying issue but not any more :)
We saw this problem as well -- we had --require features and spork was not loading the features directories -- switching to -rfeatures solved our issue.
cucumber (0.10.2) cucumber-rails (0.3.2) spork (0.9.0.rc7)
Hi,
I've started with a single cuke feature taking too long to start to be feasible for any TDD. I am using spork to reduce the start time. One problem discovered: if I want to run one feature or a group of features from a subdirectory, I need to tell cucumber to load step definitions from the main feature directory.
cucumber -r features features/clearance
This works good without spork, but with spork the "feature" part seems to go missing:
Spork is ready and listening on 8990! Running tests with args ["-r", "features/clearance", "--format", "pretty", "--strict", "--tags", "~@wip", "--no-profile"]... Done.
I had to get rid of the space between -r and features to make it one word.
cucumber -rfeatures features/clearance
And it works this way
Running tests with args ["-rfeatures", "features/clearance", "--format", "pretty", "--strict", "--tags", "~@wip", "--no-profile"]... Done.
So, generically speaking, it seems that handling of binary (two part) parameters is not right.
My versions: ruby 1.9.2p136 (2010-12-25 revision 30365), Rails 3.0.5, spork (0.9.0.rc4), cucumber (0.10.2) and cucumber-rails (0.4.0).