Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rails 4.0, Ruby 2.0.0-p247, invalid option: --format (OptionParser::InvalidOption) #269

Closed
ExReanimator opened this issue Nov 1, 2013 · 5 comments

Comments

@ExReanimator
Copy link

$ bundle exec cucumber --format pretty
......
(features ok, then appears an error)

/Users/admin/.rvm/gems/ruby-2.0.0-p247@project/gems/minitest-4.7.5/lib/minitest/unit.rb:1037:in block in process_args: invalid option: --format (OptionParser::InvalidOption)
from /Users/admin/.rvm/gems/ruby-2.0.0-p247@project/gems/minitest-4.7.5/lib/minitest/unit.rb:1016:in 'new'
from /Users/admin/.rvm/gems/ruby-2.0.0-p247@project/gems/minitest-4.7.5/lib/minitest/unit.rb:1016:in 'process_args'
from /Users/admin/.rvm/gems/ruby-2.0.0-p247@project/gems/minitest-4.7.5/lib/minitest/unit.rb:1066:in '_run'
from /Users/admin/.rvm/gems/ruby-2.0.0-p247@project/gems/minitest-4.7.5/lib/minitest/unit.rb:1059:in 'run'
from /Users/admin/.rvm/gems/ruby-2.0.0-p247@project/gems/minitest-4.7.5/lib/minitest/unit.rb:795:in 'block in autorun'

@Kosmas
Copy link
Member

Kosmas commented Nov 3, 2013

Can you please let me know what is your cucumber-rails version?

Just created a brand new rails 4.0 app with ruby-2.0.0-p247, and cucumber-rails 1.4.0 and it seems to be working as expected for a simple feature:

$ bundle exec cucumber --format pretty
Using the default profile...
Feature: Post feature

Scenario: Visit home page # features/posts.feature:3
When I go to the posts index # features/step_definitions/post_steps.rb:1
Then I should see 'Listing Posts' # features/step_definitions/post_steps.rb:5

1 scenario (1 passed)
2 steps (2 passed)
0m0.785s

@ExReanimator
Copy link
Author

@Kosmas 1.4.0 too

@Kosmas
Copy link
Member

Kosmas commented Nov 3, 2013

OK, I think it's similar to '#252 and #253, which I thought was fixed. Need to have a look.

@Kosmas
Copy link
Member

Kosmas commented Nov 4, 2013

@ExReanimator try to use the master branch until the next version comes out. The problem should be resolved there.

@ExReanimator
Copy link
Author

@Kosmas Thank you! Resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants