RSpec 3.1 main:Object 的未定义方法“特征”答案

【问题标题】：RSpec 3.1 undefined method `feature' for main:ObjectRSpec 3.1 main:Object 的未定义方法“特征”
【发布时间】：2014-10-06 13:23:11
【问题描述】：

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

undefined method `feature' for main:Object

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

在我的功能中，我需要“rails_helper”

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

spec/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 #

 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

宝石文件

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

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

【问题讨论】：

标签： ruby-on-rails ruby rspec

【解决方案1】：

您似乎忘记在您的 spec/rails_helper.rb 中要求 capybara

require 'capybara/rspec'

您也可以尝试删除此行：

config.disable_monkey_patching!

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

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

【讨论】：

对不起，我忘了补充说我已经测试过了，Capybara 已经定义好了。
谢谢，RSpec.feauture 与 config.disable_monkey_patching! 一起使用，禁用 config.disable_monkey_patching! 允许 feature 与旧版本的 RSpec 一样。

【解决方案2】：

我在使用 rails 4.2 时也遇到过同样的问题，即使我遇到过

require 'capybara/rspec' in rails_helper.rb

和

require 'spec_helper' 在功能规范中。

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

【讨论】：

您需要在大多数实际使用 rails 框架的规范中要求 rails_helper。拆分配置文件之间的整个想法是您使用更快的加载 spec_helper 来处理普通的旧 ruby 对象。

【解决方案3】：

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

require "spec_helper"

rails_helper.rb 中的下一行。

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

供您参考，我的 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"

【讨论】：

【解决方案4】：

我必须在我的问题中使用以下答案，这是以前答案的组合：

spec/features/visitors/navigation_spec.rb

require 'spec_helper'
require 'capybara/rspec'

RSpec.feature 'Navigation links', :devise do
...
end

spec/rails_helper.rb

require 'capybara/rspec'

spec/spec_helper.rb

config.disable_monkey_patching = false

【讨论】：