6

I've got a spec/controllers/add_to_carts_spec.rb:

require 'spec_helper'

describe CartItemsController do

  before (:each) do
    @user = Factory(:user)
    sign_in @user
  end

  describe "add stuff to the cart" do
    it "should add a product to the cart" do
      product = FactoryGirl.create(:product)
      visit products_path(product)
      save_and_open_page
      click_on('cart_item_submit')
    end
  end

end

and /spec/support/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 'capybara/rspec'

# 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.mock_with :rspec
  config.use_transactional_fixtures = true
end

... which also loads /spec/support/devise.rb:

RSpec.configure do |config|
  config.include Devise::TestHelpers, :type => :controller
end

Guard is running in the background and keeps throwing this:

Failures:

  1) CartItemsController add stuff to the cart should add a product to the cart
     Failure/Error: sign_in @user
     NoMethodError:
       undefined method `sign_in' for #<RSpec::Core::ExampleGroup::Nested_1::Nested_1:0x1057fd428>
     # ./spec/controllers/add_to_carts_spec.rb:7

I've spent the last couple hours trying various config adjustments and different syntaxes but nothing seems to change. Any ideas?

(edited to reflect newer error)

Jordan Sitkin
  • 2,303
  • 3
  • 26
  • 35

3 Answers3

19

The ideal solution would be to create a file at spec/support/devise.rb and include the devise test helpers in the Rspec config through the following code:

Rspec.configure do |config|
  config.include Devise::TestHelpers, :type => :controller
end

The type parameter includes the helpers only in your controller specs, this is to avoid future issues that could arise from its invocation when testing models or views. It's optional.

The reason we decided to add a discrete file for including the helpers, as opposed to including them in the specs as solnic did above is because in the event that the specs are regenerated, the spec will be overwritten.

ziyadb
  • 191
  • 1
  • 3
  • This answer has no upvotes (other than my own) and works very well. Don't overlook this as a possible solution. – Ecnalyr Jun 25 '13 at 16:07
  • While this is the right way to include these helpers the original poster is already using this method without success. It's the right answer to a different question. – zznq Dec 13 '13 at 23:50
  • The section about the `:type` parameter is where this question saved me some headache. It's not very clearly documented in the Devise docs on testing. – Matt Feb 27 '14 at 19:28
14

For some reason this also doesn't work for me so I just manually include this helper in my specs like this:

describe CartItemsController do
  include Devise::TestHelpers

  # ...
end
solnic
  • 5,733
  • 2
  • 23
  • 19
12

Those test helpers won't work for integration/request specs. The recommended way to test Devise in these situations is to visit the login page, fill in the form and submit it, and then run the test.

Please see David Chelimsky's answer to a previous SO question on this topic for a more complete explanation.

Community
  • 1
  • 1
zetetic
  • 47,184
  • 10
  • 111
  • 119
  • 1
    Thanks, you're right. I was confusing two types of specs. I was using capybara to visit the pages and thus using its session mechanisms, but trying to log in the user as i do in my controller specs. capybara doesn't use or have access to those. – Jordan Sitkin Aug 22 '11 at 17:36