On Sat, Nov 1, 2008 at 6:02 AM, Pau Cor [EMAIL PROTECTED] wrote:
When I run `rake features` after adding cucumber v0.1.8 to my rails app
(as a plugin), I get success. But when I upgrade to edge, I get this
error:
Thanks for such a detailed report!
Your steps and features look good to me. I believe this a bug.
I think it came about due to some work that was done on aligning
Scenario table values.
Could you raise a ticket in lighthouse please?
On Sat, Nov 1, 2008 at 5:02 AM, Pau Cor [EMAIL PROTECTED] wrote:
When I run `rake features` after adding cucumber v0.1.8 to my rails app
(as a plugin), I get success. But when I upgrade to edge, I get this
error:
Barry Mitchelson wrote:
This sounds like the issue I had here
http://rspec.lighthouseapp.com/projects/16211/tickets/60-patch-next_column_index-not-resetting-after-large-tables.
Is there a feature running before this one with a scenario table with
at
least 2 more columns than the one in the
When I run `rake features` after adding cucumber v0.1.8 to my rails app
(as a plugin), I get success. But when I upgrade to edge, I get this
error:
|/home/paul/sc/ror/cebu_heroku/vendor/plugins/cucumber/bin/../lib/cucumber/formatters/pretty_formatter.rb:205:in
`ljust': no implicit conversion
