Home/ Questions/Q 7186157
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T18:34:22+00:00

I’m using cucumber to test my rails 3.1 application and i’m using devise for

  • 0

I’m using cucumber to test my rails 3.1 application and i’m using devise for authentication.
I need to test if current user email is the same with the one used during authorization.
The problem is that devise helpers are not available in cucumber step definition.

Is there any solution to make devise helpers available in cucumber step definitions?

i tried this: 

Cucumber::Rails::World.send('define_method', 'current_user') do
    @current_user ||= (session[:user] && User.find(session[:user])) || :false
end

but that didn’t help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Add this to the step definitions file that needs to use it:

    World(Devise::TestHelpers)

    While this makes the ‘sign_in’ and ‘sign_out’ methods available, they can’t actually be used from Cucumber, so this DOES NOT WORK. The comments at the top of devise’s file says “Do not use Devise::TestHelpers in integration tests”. See: https://github.com/plataformatec/devise/blob/master/lib/devise/test_helpers.rb

    Unfortunately, cucumber steps don’t have access to the web request object and session parameters. It appears the only way to do this is to repeatedly perform the login web requests at the start of each scenario. Boring. I find it odd that cucumber can directly manipulate the test rails app’s database but not the web request/session. In any case, this old post shows a good example of refactoring steps to be in a module that can be shared by many steps easily: http://drnicwilliams.com/2009/04/15/cucumber-building-a-better-world-object/

    If anyone else has an answer for how a scenario can set the logged in state without having to do all the capybara web calls, I’d love to hear it.

    • 0