Rails%203%20In%20Action

266 CHAPTER 10 Tracking state
You can go one step further and move this code into a helper. Views are more for
displaying information than for deciding how it should be output, which should be left
to the helpers and controllers. Move this code into the app/helpers/tickets_helper.rb
because this partial is displayed from the TicketsController’s show template. The
entire TicketsHelper should now look like the following listing.
Listing 10.20 app/helpers/tickets_helper.rb
module TicketsHelper
def state_for(comment)
content_tag(:div, :class => "states") do
if comment.state
if comment.previous_state && comment.state != comment.previous_state
"#{render comment.previous_state} → #{render comment.state}"
else
"→" + render(comment.state)
end
end
end
end
end
In this example, you check to see if the comment has an assigned state and then if it
has a previous state. If it has a previous state that isn’t the assigned state, then you
show the state transition; otherwise you render the assigned state.
You can now replace the whole if statement in app/views/comments/_comment
.html.erb with this single line:
Now check to see if this is working by running your scenario using bin/cucumber
features/creating_comments.feature:33:
Then I should see "State: Open" within "#comments"
expected there to be content "State: Open" in
"\n \n user@ticketee.com (User)\n \n
Open\n\n This is a real issue\n\n"
It’s still failing? Are you sure you’ve set everything up correctly? Absolutely. Capybara
(through Cucumber) is telling you that it still can’t find this text on the page. Lucky
for you there’s a way to see the page that Cucumber is seeing: the “Then show me the
page” step you saw a little earlier.
10.3.4 Show me the page
When you use this step, it saves the current page to a file and opens it in the browser
so you’re able to see exactly what Cucumber is seeing. Let’s put this step as the secondto-last
step in “Changing a ticket’s state.” The last three steps in this scenario should
look like the following: