Rails%203%20In%20Action

Classes outside your control
Next, you’ll apply what you’ve done here to associate the users who are signed in
with the topics they post. This is so people will be able to see who posted what.
17.7.3 Authenticating topics
By having a belongs_to :user association on the Forem::Post and Forem::Topic
models, you’ll be able to assign users to topics and posts when they create them so that
other users can know who’s been posting what.
You’ve got, on purpose, no authentication in your dummy application at the
moment, and so you’ll have to take a shortcut around this. Usually an application
would provide a current_user method that returns a User object, but your dummy
application doesn’t do this right now. You need this method to sometimes return a user
object (like with actions that require authentication), and to sometimes return nil.
A cool way to do this would be to dynamically redefine the current_user method
yourself. A way to do this is to have two methods that you can call in your tests—a
sign_in! method and a sign_out! method—which will redefine the current_user
method in ApplicationController to either return the user object or nil, respectively.
You’ll also make this method a helper method by using the helper_method
method, which is available in all controllers. This will mean that your fake
current_user method can then be referenced by the controllers and views of your
engine without any problems.
Define these two new methods in a new file at spec/support/dummy_login.rb using
the code shown in the following listing.
Listing 17.13 spec/support/dummy_login.rb
def sign_out!
ApplicationController.class_eval