我经历了相当痛苦的升级到RSpec 3.1.我有几个功能规格,在RSpec 2.99中起作用： @H_403_2@undefined method `feature' for main:Object

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

在我的功能我需要’rails_helper’

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

投机/ rails_helper.rb

@H_403_2@# 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_helper.rb
#

@H_403_2@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

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