RSpec 3.1 undefined方法`feature'for main：Object

I´m going through the rather painful upgrade to RSpec 3.1. I have several feature specs which worked in RSpec 2.99 that raise:

我正在经历相当痛苦的升级到RSpec 3.1。我有几个功能规格在RSpec 2.99中有效提升：

undefined method `feature' for main:Object

I noticed that I have to use RSpec.describe in my other specs since they are are no longer attached to the main object. What would the equivalent call for feature be?

我注意到我必须在我的其他规范中使用RSpec.describe，因为它们不再附加到主对象。相同的功能要求是什么？

In my features I require 'rails_helper'

在我的功能中，我需要'rails_helper'

require 'rails_helper'
feature 'Facebook Authentiation' do
  ...
end

spec/rails_helper.rb

投机/ rails_helper.rb

# This file is copied to spec/ when you run 'rails generate rspec:install'
ENV["RAILS_ENV"] ||= 'test'
require 'spec_helper'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'
require 'rails/application'
# Add additional requires below this line. Rails is not loaded until this point!

ActiveRecord::Migration.maintain_test_schema!

RSpec.configure do |config|
  # If you're not using ActiveRecord, or you'd prefer not to run each of your
  # examples within a transaction, remove the following line or assign false
  # instead of true.
  config.use_transactional_fixtures = false

  # RSpec Rails can automatically mix in different behaviours to your tests
  # based on their file location
  config.infer_spec_type_from_file_location!
end

spec/spec_helper.rb #

spec / spec_helper.rb＃

 See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
RSpec.configure do |config|

  # rspec-expectations config goes here. You can use an alternate
  # assertion/expectation library such as wrong or the stdlib/minitest
  # assertions if you prefer.
  config.expect_with :rspec do |expectations|
    # This option will default to `true` in RSpec 4. It makes the `description`
    # and `failure_message` of custom matchers include text for helper methods
    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
  end

  # rspec-mocks config goes here. You can use an alternate test double
  # library (such as bogus or mocha) by changing the `mock_with` option here.
  config.mock_with :rspec do |mocks|
    # Prevents you from mocking or stubbing a method that does not exist on
    # a real object. This is generally recommended, and will default to
    # `true` in RSpec 4.
    mocks.verify_partial_doubles = true
  end

  # These two settings work together to allow you to limit a spec run
  # to individual examples or groups you care about by tagging them with
  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
  # get run.
  config.filter_run :focus
  config.run_all_when_everything_filtered = true

  # Limits the available syntax to the non-monkey patched syntax that is recommended.
  # For more details, see:
  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
  config.disable_monkey_patching!

  # Many RSpec users commonly either run the entire suite or an individual
  # file, and it's useful to allow more verbose output when running an
  # individual spec file.
  if config.files_to_run.one?
    # Use the documentation formatter for detailed output,
    # unless a formatter has already been configured
    # (e.g. via a command-line flag).
    config.default_formatter = 'doc'
  end

  # Print the 10 slowest examples and example groups at the
  # end of the spec run, to help surface which specs are running
  # particularly slow.
  config.profile_examples = 10

  # Run specs in random order to surface order dependencies. If you find an
  # order dependency and want to debug it, you can fix the order by providing
  # the seed, which is printed after each run.
  #     --seed 1234
  config.order = :random

  # Seed global randomization in this process using the `--seed` CLI option.
  # Setting this allows you to use `--seed` to deterministically reproduce
  # test failures related to randomization by passing the same `--seed` value
  # as the one that triggered the failure.
  Kernel.srand config.seed
end

Gemfile

的Gemfile

# ...
group :development, :test do
  gem 'rspec-rails', '~> 3.1.0'
end

# ...
group :test do
  # ...
  gem 'capybara', '~> 2.4.3'
end

3 个解决方案

#1

It looks like your forgot to require capybara at your spec/rails_helper.rb

看起来您忘了在spec / rails_helper.rb上要求使用水豚

require 'capybara/rspec'

Also you can try to remove this line:

您也可以尝试删除此行：

config.disable_monkey_patching!

Or check if capybara adds feature method to Rspec namespace:

或者检查capybara是否为Rspec命名空间添加了feature方法：

RSpec.feature "My feature" do
  ...
end

#2

I've faced the same issue with rails 4.2 even though I've had

我遇到了与rails 4.2相同的问题，即使我已经有了

require 'capybara/rspec' in rails_helper.rb

在rails_helper.rb中要求'capybara / rspec'

and

和

require 'spec_helper' in feature spec.

在功能规范中要求'spec_helper'。

Solution is to require 'rails_helper' in feature spec as well.

解决方案是在功能规范中也需要'rails_helper'。

#3

In my case the problem was that I had the

在我的情况下，问题是我有

require "spec_helper"

line lower in rails_helper.rb.

在rails_helper.rb中较低的一行。

When I moved it at the top, everything went back to normal.

当我把它移到顶部时，一切都恢复正常。

For your reference, my rails_helper.rb first lines now are:

供您参考，我的rails_helper.rb现在的第一行是：

require "spec_helper"
ENV["RAILS_ENV"] ||= "test"
require File.expand_path("../../config/environment", __FILE__)
abort("The Rails environment is running in production mode!") if Rails.env.production?
require "rspec/rails"

#1