Le specifiche del controller RSpec non funzionano a meno che non si aggiunga esplicitamente: type =>: controller

Question

Sto tentando di eseguire il comando $ rspec ma tutti i test del mio controller non funzionano a meno che non aggiunga esplicitamente :type => :controller a ciascuna delle specifiche.

Ecco l'errore che sto ricevendo:

1) AccountsController GET index assigns all accounts as @accounts 
    Failure/Error: get :index, {}, valid_session 
    NoMethodError: 
     undefined method `get' for #<RSpec::ExampleGroups::AccountsController_2::GETIndex:0x007fd96c8a6a68> 
    # ./spec/controllers/accounts_controller_spec.rb:36:in `block (3 levels) in <top (required)>' 

Ecco le specifiche generato:

require 'spec_helper' 

# This spec was generated by rspec-rails when you ran the scaffold generator. 
# It demonstrates how one might use RSpec to specify the controller code that 
# was generated by Rails when you ran the scaffold generator. 
# 
# It assumes that the implementation code is generated by the rails scaffold 
# generator. If you are using any extension libraries to generate different 
# controller code, this generated spec may or may not pass. 
# 
# It only uses APIs available in rails and/or rspec-rails. There are a number 
# of tools you can use to make these specs even more expressive, but we're 
# sticking to rails and rspec-rails APIs to keep things simple and stable. 
# 
# Compared to earlier versions of this generator, there is very limited use of 
# stubs and message expectations in this spec. Stubs are only used when there 
# is no simpler way to get a handle on the object needed for the example. 
# Message expectations are only used when there is no simpler way to specify 
# that an instance is receiving a specific message. 

describe AccountsController do 

    # This should return the minimal set of attributes required to create a valid 
    # Account. As you add validations to Account, be sure to 
    # adjust the attributes here as well. 
    let(:valid_attributes) { { "subdomain" => "MyString" } } 

    # This should return the minimal set of values that should be in the session 
    # in order to pass any filters (e.g. authentication) defined in 
    # AccountsController. Be sure to keep this updated too. 
    let(:valid_session) { {} } 

    describe "GET index" do 
    it "assigns all accounts as @accounts" do 
     account = Account.create! valid_attributes 
     get :index, {}, valid_session 
     assigns(:accounts).should eq([account]) 
    end 
    end 
... 

Se guardo nel file spec/rails_helper.rb, vedo questo frammento:

# RSpec Rails can automatically mix in different behaviours to your tests 
    # based on their file location, for example enabling you to call `get` and 
    # `post` in specs under `spec/controllers`. 
    # 
    # You can disable this behaviour by removing the line below, and instead 
    # explicitly tag your specs with their type, e.g.: 
    # 
    #  RSpec.describe UsersController, :type => :controller do 
    #  # ... 
    #  end 
    # 
    # The different available types are documented in the features, such as in 
    # https://relishapp.com/rspec/rspec-rails/docs 
    config.infer_spec_type_from_file_location! 

Ma sono nuovo a RSpec e TDD e non sono sicuro che questo file rails_helper.rb venga letto o meno.

spec/spec_helper.rb

# This file is copied to spec/ when you run 'rails generate rspec:install' 
ENV["RAILS_ENV"] ||= 'test' 
require File.expand_path("../../config/environment", __FILE__) 
require 'rspec/rails' 
require 'email_spec' 
require 'rspec/autorun' 

# Requires supporting ruby files with custom matchers and macros, etc, 
# in spec/support/ and its subdirectories. 
Dir[Rails.root.join("spec/support/**/*.rb")].each {|f| require f} 

RSpec.configure do |config| 
    config.include(EmailSpec::Helpers) 
    config.include(EmailSpec::Matchers) 
    # ## Mock Framework 
    # 
    # If you prefer to use mocha, flexmock or RR, uncomment the appropriate line: 
    # 
    # config.mock_with :mocha 
    # config.mock_with :flexmock 
    # config.mock_with :rr 

    # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures 
    config.fixture_path = "#{::Rails.root}/spec/fixtures" 

    # 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 = true 

    # If true, the base class of anonymous controllers will be inferred 
    # automatically. This will be the default behavior in future versions of 
    # rspec-rails. 
    config.infer_base_class_for_anonymous_controllers = false 

    # 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" 

    config.before(:suite) do 
    DatabaseCleaner.strategy = :truncation 
    end 
    config.before(:each) do 
    DatabaseCleaner.start 
    end 
    config.after(:each) do 
    DatabaseCleaner.clean 
    end 
end 

qualcuno può dirmi come posso ottenere mio specifiche del controller per eseguire senza dover aggiungere in modo esplicito :type => :controller? Le specifiche del controller sono tutte nella dir spec/controllers così RSpec dovrebbe solo sapere che sono le specifiche del controller.

Answer 1

si sta eseguendo RSpec 3 e non hanno completamente aggiornato la configurazione dalla RSpec 2.

RSpec-rail 3 genera 'spec_helper.rb' e 'rails_helper.rb'. 'rails_helper.rb' richiede 'spec_helper.rb'. In rspec-rails 3, le specifiche delle classi di Rails dovrebbero essere require 'rails_helper', non require 'spec_helper' come sta facendo la specifica generata. Quindi, o

• cambiamento require 'spec_helper'-require 'rails_helper',
• rigenerare il patibolo (credo che la tua spec è stato generato da RSpec-rails 2), o
• rimuovere la funzionalità richiedono tutto e messo --require rails_helper nel file del progetto .rspec quindi è automaticamente incluso in tutte le specifiche.

E quindi config.infer_spec_type_from_file_location! avrà effetto.