cwd
1
I had a relatively flat layout and wanted to group like features
together so I made it more hierarchical:
features/
messaging/
main_screen.feature
message_page.feature
steps/
main_screen.rb
messaging_steps.rb
This may be just my boneheadedness, but when I do:
cucumber features/messaging -r features/support/env.rb
These run, but none of the steps are matched. It seems the step
matchers are not expected to be where I put them.
Questions:
- Is there a more sensible layout?
- Is there an easier way than -r features/support/env.rb to get the
machinist plugin to load?
Thanks
cwd
2
On Thu, Jan 22, 2009 at 4:51 PM, s.ross [email protected] wrote:
This may be just my boneheadedness, but when I do:
cucumber features/messaging -r features/support/env.rb
That ONLY loads features/support/env.rb and not any of the step
definition files. Try this:
cucumber features/messaging -r features
cwd
3
On Jan 22, 2009, at 3:38 PM, David C. wrote:
main_screen.rb
Thanks
Yup. That was it. Thanks!
cwd
4
On Fri, Jan 23, 2009 at 1:05 AM, s.ross [email protected] wrote:
main_screen.feature
That ONLY loads features/support/env.rb and not any of the step
- Is there a more sensible layout?
- Is there an easier way than -r features/support/env.rb to get the
machinist plugin to load?
Thanks
Yup. That was it. Thanks!
Just to clarify…
If you pass no --require switches to cucumber, it will guess where to
find
.rb files to load
If you pass one or more it will stop guessing
Aslak