RSpec 3.1 undefined method `Funktion' for main:Object
Werde ich durch die eher schmerzhafte upgrade auf RSpec 3.1. Ich habe mehrere feature-Spezifikationen arbeitete, in RSpec 2.99 erhöhen:
undefined method `feature' for main:Object
Bemerkte ich, dass ich RSpec.describe
in meine anderen specs, da Sie nicht mehr an die Haupt-Objekt. Was wäre den entsprechenden Aufruf für die Funktion sein?
In meinen Funktionen, die ich benötigen '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
Gemfile
# ...
group :development, :test do
gem 'rspec-rails', '~> 3.1.0'
end
# ...
group :test do
# ...
gem 'capybara', '~> 2.4.3'
end
Du musst angemeldet sein, um einen Kommentar abzugeben.
Es sieht aus wie Ihre vergaß zu verlangen, Wasserschweine auf deine Skillung/rails_helper.rb
Außerdem können Sie versuchen, diese Zeile zu entfernen:
Oder prüfen Sie, ob "capybara", fügt der feature-Methode zu Rspec-namespace:
RSpec.feauture
arbeitet mitconfig.disable_monkey_patching!
und deaktivierenconfig.disable_monkey_patching!
ermöglichtfeature
als in älteren Versionen von RSpec.Ich habe vor dem gleichen Problem mit rails 4.2 obwohl ich ' ve hatte
require 'capybara/rspec'
imrails_helper.rb
und
require 'spec_helper'
Funktion spec.Lösung ist
require 'rails_helper'
im feature-Spezifikation als gut.rails_helper
in den meisten Spezifikationen, die tatsächlich mit dem rails framework. Die ganze Idee Spaltung zwischen den config-Dateien ist, dass Sie verwenden, die schneller ladenspec_helper
für plain old ruby-Objekte.In meinem Fall das problem war, dass ich die
Zeile niedriger in rails_helper.rb.
Wenn ich zog es auf die Spitze, lief alles wieder normal.
Für Ihre Referenz, meine rails_helper.rb die ersten Zeilen sind nun:
Ich hatte die Verwendung der folgenden in mein problem, das ist eine Kombination aus den vorherigen Antworten:
Spezifikation/features/Besucher/navigation_spec.rb
spec/rails_helper.rb
spec/spec_helper.rb