Rails%203%20In%20Action

502 CHAPTER 17 Engines
forem_user; if it can’t do that, it will create one instead. This will then be the object that
is returned when you reference current_user in your application.
The next function you’re going to add to your engine is one that will redirect users
who aren’t logged in when they attempt to access the new action in Forem::Topics-
Controller. Your test will also test that an unauthenticated user can’t see the New
Topic link on theForem::TopicsController’s index action. You’ll add this spec in
spec/integration/topics_spec.rb by using the code in the following listing.
Listing 17.14 spec/integration/topics_spec.rb
context "unauthenticated users" do
before do
sign_out!
end
it "cannot see the 'New Topic' link" do
visit topics_path
page.should_not have_content("New Topic")
end
it "cannot begin to create a new topic" do
visit new_topic_path
page.current_url.should eql(sign_in_url)
end
end
In the before block of this new context, you call the sign_out! method, which will
set up the crucial current_user method that this test depends on. If it wasn’t defined,
then you’d get an undefined method when current_user attempted to access it.
In this spec, you use page.current_url B to read what the current URL is; it should
match whatever main_app.sign_in_path’s method points at. Remember: this is the
sign_in_path method, which is made available in the application by a definition in its
config/routes.rb file. This is not currently set up, and so you’ll do that later.
First, let’s see what the output has to say about your first test when you run bin/
rspec spec/integration/topics_spec.rb:25:
Failure/Error: page.should_not have_content("New Topic")
expected #has_content?("New Topic") to return false, got true
You’re asserting in your test that an unauthenticated user cannot see the New Topic
link, but they do. You can go into app/views/forem/topics/index.html.erb and change
this line
to these lines:
B Read current URL