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

When running rake cucumber at the end of the run I get invalid option #507

Closed
bram-bba opened this issue Jul 25, 2013 · 7 comments
Closed

Comments

@bram-bba
Copy link

When running rake cucumber at the end of the run I get invalud option

rake cucumber
/home/upbram/.rvm/rubies/ruby-1.9.3-p448/bin/ruby -S bundle exec cucumber  --profile default
Using the default profile...
Feature: Log in
    In order to reach the landing page
    A visitor
    Should log in

  Scenario: Redirect to login          # features/login.feature:6
    Given I am on the home page        # features/step_definitions/navigation_steps.rb:3
    When I go to the maymay_rules page # features/step_definitions/navigation_steps.rb:12
    Then I should see "Sign in"        # features/step_definitions/navigation_steps.rb:54

  Scenario: Come back after login                 # features/login.feature:11
    Given I go to the maymay_rules page           # features/step_definitions/navigation_steps.rb:12
    And I fill in "Email" with "[email protected]" # features/step_definitions/navigation_steps.rb:24
    And I fill in "Password" with "password"      # features/step_definitions/navigation_steps.rb:24
    And I press "Sign in"                         # features/step_definitions/navigation_steps.rb:16
    Then I should see "Rules"                     # features/step_definitions/navigation_steps.rb:54

Feature: Rules Management
    In order to allow other persons to access entities
    As a person that can manage rule
    I want send me a message by contact form

  @javascript
  Scenario: Create a user rule                    # features/rules_management.feature:7
    Given I go to the maymay_rules page           # features/step_definitions/navigation_steps.rb:12
    And I fill in "Email" with "[email protected]" # features/step_definitions/navigation_steps.rb:24
    And I fill in "Password" with "password"      # features/step_definitions/navigation_steps.rb:24
    And I press "Sign in"                         # features/step_definitions/navigation_steps.rb:16
    When I click "New Rule"                       # features/step_definitions/navigation_steps.rb:20
    And I click "Add User Condition"              # features/step_definitions/navigation_steps.rb:20
    And I fill in "Property Name" with "email"    # features/step_definitions/navigation_steps.rb:24
    And I click "Add Action"                      # features/step_definitions/navigation_steps.rb:20
    And I fill in "Action" with "manage"          # features/step_definitions/navigation_steps.rb:24
    And I fill in "Type" with "User"              # features/step_definitions/navigation_steps.rb:24
    And I click "Create Rule"                     # features/step_definitions/navigation_steps.rb:20
    And I go to the users page                    # features/step_definitions/navigation_steps.rb:12
    Then I should see "New User"                  # features/step_definitions/navigation_steps.rb:54

3 scenarios (3 passed)
21 steps (21 passed)
0m9.524s
/home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/test/unit.rb:49:in `process_args': invalid option: --profile (OptionParser::InvalidOption)
    from /home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/minitest/unit.rb:891:in `_run'
    from /home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/minitest/unit.rb:884:in `run'
    from /home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/test/unit.rb:21:in `run'
    from /home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/test/unit.rb:326:in `block (2 levels) in autorun'
    from /home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/test/unit.rb:27:in `run_once'
    from /home/upbram/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/test/unit.rb:325:in `block in autorun'

I found some old "fixed" issues but no fix for this.

GemFile

gem 'rails', '3.2.14'
#
# Gems used only for assets and not required
# in production environments by default.
group :assets do
  gem 'sass-rails',   '~> 3.2.3'
  gem 'coffee-rails', '~> 3.2.1'

  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
  # gem 'therubyracer', :platforms => :ruby

  gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails'
gem 'thin'
gem 'devise', '2.2.4'
gem 'devise-i18n', '0.8.5'
gem 'i18n-js', '2.1.2.upnxt'

 group :assets do
    gem 'bootstrap-sass', '~> 2.0.3'
    gem 'compass-rails', '~> 1.0.3'
 end

gem 'simple_form'
gem 'cucumber-rails', group: 'test'
gem 'database_cleaner', group: 'test'
gem 'selenium-webdriver', group: 'test'
gem 'headless', group: 'test'
gem 'rspec-rails', '>= 2.0.1', group: 'test'

Please advice

@ambirag
Copy link
Contributor

ambirag commented Jul 29, 2013

@@stop_auto_run = true in your env.rb should fix this.

@svoynow
Copy link

svoynow commented Jul 29, 2013

I've got the same issue and @@stop_auto_run = true doesn't appear to make any difference.

@bram-bba
Copy link
Author

thanks @ambirag for me it did the trick

@h3h
Copy link

h3h commented Sep 22, 2013

I am finding that @@stop_auto_run = true in my env.rb file does not fix the underlying issue.

There are a bunch of issues and monkey patches floating around for this issue, but it doesn't seem like anyone has definitively fixed it. Can anyone point to a legitimate fix?

@aslakhellesoy
Copy link
Contributor

@h3h others have reported this as fixed if you use cucumber 1.3.8 and cucumber-rails master, which fixes cucumber/cucumber-rails#253

@h3h
Copy link

h3h commented Sep 22, 2013

@aslakhellesoy Thanks. cucumber 1.3.8 + cucumber-rails@master seem to work.

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants