On Wed, Nov 26, 2008 at 4:56 PM, James Byrne <[EMAIL PROTECTED]> wrote:
> aslak hellesoy wrote: > > > > > When this is implemented it will be easier to diagnose and fix problems > > like this. It will give you a hint about other --require options you > > might want to add. > > > > Cheers, > > Aslak > > Thank you. I have add my heartfelt thanks for your work on cucumber. I > tried to wrap my head around rspec/stories when they first appeared late > last summer and I never really did grasp how to use them. Cucumber has > simply transformed the way I now see things in BDD. > Thanks man. I appreciate it. I owe a lot to Dan North who did JBehave then RBehave then RSpec Stories which is where the ideas were born. I only improved the implementation and added some sugar coating. Seems like sugar coating is what's needed to make things fly hehe. Plus now there are 51 forks and I have merged in contribs from some 30 people thanks to GitHub. This would never have grown so fast in a centralised SCM like Subversion. > > I the meantime, could somebody provide me with a hint or two on what I > should pass cucumber with the -r option to get the same effect as rake > features? I have tried, without success, multiple variations on the > essence of the following: > > cucumber features -r config/environment lib/cucumber/rails/world Until we have a better way to display --verbose - I'd try to sprinkle some puts statements in the cli.rb class to see what gets loaded when you run via rake - and try to mimic that from the cucumber command line. HTH, Aslak > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
