Databases
StackOverflow2013
Postsdbo
PORuby on Rails functional testing with the RESTful Authentication plugin
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORuby on Rails functional testing with the RESTful Authentication plugin
    text
    copied!<p>I started writing functional tests for my rails app today. I use the RESTful authentication plugin. I ran into a couple confusing things I hope someone can clarify for me.</p> <p>1) I wrote a quick login function because most of the functions in my rails app require authentication.</p> <pre><code>def login_as(user) @request.session[:user_id] = user ? user.id : nil end </code></pre> <p>The issue I see with this function, is it basically fakes authentication. Should I be worried about this? Maybe it is okay to go this route as long as I test the true authentication method somewhere. Or maybe this is terrible practice.</p> <p>2) The second confusing thing is that in some places in my functional tests, I need the full authentication process to happen. When a user is activated, I have the do_activate method create some initial objects for the user. It is analogous to the creation of a blank notebook object and pen object for a student application, if that makes sense.</p> <p>So in order to properly test my application, I need the user to hit that activation state so those objects are created. I am currently using Factory Girl to create the user, and then calling the login_as function above to fake authentication. </p> <p>I guess another option would be to skip the full authentication sequence and just create the blank objects with Factory Girl. I could test the proper authentication somewhere else.</p> <p>What do you think? If I should go through the proper sequence, why isn't the code below invoking the do_activate function?</p> <pre><code>user = Factory.create(:user) user.active = 1 user.save </code></pre> <p>Thank you!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload