Rails%203%20In%20Action

504 CHAPTER 17 Engines
You don’t need this controller to do much more than sit there and look pretty. Oh,
and it needs to have a login action that responds in an OK fashion too. Let’s define
this controller in your dummy application by creating a new file at spec/dummy/app/
controllers/fake_controller.rb and putting this content inside it:
class FakeController < ApplicationController
def sign_in
render :text => "Placeholder login page."
end
end
This action will now render the text “Placeholder login page,” thereby returning that
OK status you’re after, as well as some helpful text to indicate where you’re at. When
you run bin/rspec spec/integration/topics_spec.rb, you’ll see that it passes:
1 example, 0 failures
This means now that any user attempting to access the new action in the
Forem::TopicsController will be redirected to the login page. What happens when
you run the whole spec file? Let’s find out with bin/rspec spec/integration/
topics_spec.rb:
ActionView::Template::Error:
undefined method `current_user' for #
...
# ./spec/integration/topics_spec.rb:21:in ...
3 examples, 1 failure
Your final spec in this file is failing with an undefined method current_user, because
you’re not calling sign_in! before it. Move this code into its own context with a
before like the other two tests have, using the code shown in the following listing.
Listing 17.15 spec/integration/topics_spec.rb
context "authenticated users" do
before do
sign_in!
end
it "creating a new one" do
visit topics_path
click_link "New Topic"
fill_in "Subject", :with => "First topic!"
fill_in "Text", :with => "First post!"
click_button "Create Topic"
within "#flash_notice" do
page.should have_content("Topic has been created!")
end
within ".forem_topic #posts .forem_post" do
page.should have_content("First post!")
end
end
end