I am trying to get some old “rbehave” scripts working with cucumber. I
am running into an error. I get the same error when I run the
“calculator_ruby_features” example.
Any suggestions?
Bret
C:\work\cucumber\examples\calculator_ruby_features>rake features
(in C:/work/cucumber/examples/calculator_ruby_features)
You must gem install win32console to get coloured output on this ruby
platform (
i386-mswin32)
C:/work/cucumber/bin/…/lib/cucumber/tree/feature.rb:37:in add_scenario': wrong number of arguments (1 for 2) (ArgumentError) from C:/work/cucumber/bin/../lib/cucumber/tree/feature.rb:37:inScenari
o’
from ./features/addition.rb:8
from C:/work/cucumber/bin/…/lib/cucumber/tree/feature.rb:13:in instanc e_eval' from C:/work/cucumber/bin/../lib/cucumber/tree/feature.rb:13:ininitial
ize’
from C:/work/cucumber/bin/…/lib/cucumber/tree.rb:8:in new' from C:/work/cucumber/bin/../lib/cucumber/tree.rb:8:inFeature’
from ./features/addition.rb:6
from
c:/ruby-186-26/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27
:in gem_original_require' from c:/ruby-186-26/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27 :inrequire’
from C:/work/cucumber/bin/…/lib/cucumber/cli.rb:188:in require_files' from C:/work/cucumber/bin/../lib/cucumber/cli.rb:186:ineach’
from C:/work/cucumber/bin/…/lib/cucumber/cli.rb:186:in require_files' from C:/work/cucumber/bin/../lib/cucumber/cli.rb:165:inexecute!’
from C:/work/cucumber/bin/…/lib/cucumber/cli.rb:11:in `execute’
from C:/work/cucumber/bin/cucumber:5
rake aborted!
Command failed with status (1): [c:/ruby-186-26/bin/ruby -I
"C:/work/cucumb…]
I am trying to get some old “rbehave” scripts working with cucumber. I
am running into an error. I get the same error when I run the
“calculator_ruby_features” example.
Any suggestions?
Bret
Are you using the latest cucumber from github? There was a problem with
the ruby example that was recently fixed. If that is not the issue
please open a ticket on Lighthouse.
-Ben
Yes. I did a git pull and reproduced the error right before reporting
it.
Afterwards, I converted my test to use the new *.feature format and this
worked fine.
I am curious what the thinking is about supporting the old format. I
suspect that I’ll be moving to the new format, but want to know what the
feeling is with others.
Afterwards, I converted my test to use the new *.feature format and this
worked fine.
I am curious what the thinking is about supporting the old format. I suspect
that I’ll be moving to the new format, but want to know what the feeling is
with others.
Interesting you should ask. I added it to make the migration easier
for those who used it.
However, I have a feeling that very few are using it, so in the long
run I’d like to bag it.
Maybe deprecate it in next release and bag it 2-3 releases later.
I’m a newb to git and apparently need to learn more about how to use it
correctly. I’m wondering if i somehow updated my local repo without
updating my workspace.
However, I have a feeling that very few are using it, so in the long
run I’d like to bag it.
Maybe deprecate it in next release and bag it 2-3 releases later.