[cucumber] Bug introduced in 0.3.1

Hi All,

I’m new to the list, but a happy cucumber user with a few weeks
experience
now… a bit of a shock this morning when someone upgraded here and
happened
to jump up to 0.3.1, we’re seeing the following output…

I haven’t had chance to investigate more, but I will try to… this goes
away
if we roll back to 0.3.0.

I also listed the relevant local gems as far as I can see, I’ll post
back
here if I come up with anything, pointers or suggestions would be
welcomed!

Thank you,

Lee H.

Lee H. wrote:

* http://gist.github.com/104429

I also listed the relevant local gems as far as I can see, I’ll post
back here if I come up with anything, pointers or suggestions would be
welcomed!

Thank you,

Lee H.

What is your rails environment file? (test.rb)

-Ben

Hi Ben,
Please see this Gist http://gist.github.com/104711 - note also that it
doesn’t seem to matter about the dependencies I’ve got in that file now,
they’re a recent addition and don’t seem to affect this behavior.

  • Thanks,

Lee

2009/4/30 Ben M. [email protected]

Hi List,
We didn’t resolve this in the end, we rolled back to Cucumber 0.3.0; has
anyone else seen anything similar?

  • Lee

2009/4/30 Julian L. [email protected]

I have NO idea if this is relevant, but the way you extend worlds has
changed, I’m fairly sure.

Julian.

Hi List,
We didn’t resolve this in the end, we rolled back to Cucumber 0.3.0; has
anyone else seen anything similar?

Nobody else has reported anything similar on this mailing list.
Can you run with --backtrace on so we can see where the error is coming
from?
Can you also gist your features/support/env.rb file?

Aslak

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs