Home/ Questions/Q 6174069
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T23:41:22+00:00

I’m building a Rails 3 app using Devise, with Capybara for UI testing. The

  • 0

I’m building a Rails 3 app using Devise, with Capybara for UI testing. The following test is failing:

class AuthenticationTest < ActionController::IntegrationTest

  def setup
    @user = User.create!(:email => 'test@example.com', 
                         :password => 'testtest', 
                         :password_confirmation => 'testtest')
    @user.save!
    Capybara.reset_sessions!
  end

  test "sign_in" do
    # this proves the user exists in the database ...
    assert_equal 1, User.count
    assert_equal 'test@example.com', User.first.email

    # ... but we still can't log in ...
    visit '/users/sign_in'
    assert page.has_content?('Sign in')
    fill_in :user_email, :with => 'test@example.com'
    fill_in :user_password, :with => 'testtest'
    click_button('user_submit')

    # ... because this test fails
    assert page.has_content?('Signed in successfully.')
  end

end

… but I have no idea why. As you can see from the code, the user is being created in the database; I’m using the same approach to create the user as I did in seeds.rb.

If I run the test through the debugger, I can see the user in the database and verify that the page is loading. But still the authentication fails; I can verify this because if I change the assertion to test for the failure case, the test passes:

# verify that the authentication actually failed
assert page.has_content?('Invalid email or password.')

I’m used to Rails 2, & using Selenium for this sort of testing, so I suspect I’m doing something daft. Could someone please point me in the right direction here?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I was having the same issue and found a thread with a solution:

    RSpec.configure do |config|
  config.use_transactional_fixtures = false

  config.before(:suite) do
    DatabaseCleaner.strategy = :truncation
  end

  config.before(:each) do
    DatabaseCleaner.start
  end

  config.after(:each) do
    DatabaseCleaner.clean
  end

end

    For the DatabaseCleaner stuff to work you’ll need to include the database_cleaner gem. If you haven’t used it before, you may need to rake db:test:prepare before rerunning your tests. I hope this works for you, too!

    • 0