Rails%203%20In%20Action

Tracking changes
And I should see "Open" within "#ticket .state"
Then show me the page
Then I should see "Open" within "#comments"
When you run your scenario again, it should pop up a browser window that shows you
the exact same page as Cucumber sees, shown in figure 10.13.
Here you can see the partials rendered with their HTML shown on the page. This is
because code coming from a string in a helper is automatically escaped, which is helpful—but
sometimes things like this happen. Better safe than sorry!
10.3.5 Automatic escaping saves your bacon
This automatic escaping of strings is one of Rails 3’s big features. This saves your
bacon because it stops malicious output being input into forms accidentally. This output
would be things like your ticket’s description or comment text, which comes from
the users. Never trust the users with outputting nonmalicious content!
If this input wasn’t escaped before it was output to the page, it could potentially
contain HTML tags like , which could contain malicious content. Rails 3 saves
your bacon in this respect by automatically escaping all strings output to the view
through ERB tags. Yes, sometimes it will be overzealous and escape things you don’t
want it to escape, like your state partials.
You can tell it that the string is safe by calling html_safe in your helper, changing
it to this:
"#{render comment.previous_state} → #{render comment.state}".html_safe
The html_safe method effectively tells Rails, “It’s cool, man,” and Rails won’t escape
anything inside the string. When you run bin/cucumber features/creating_tickets
.feature:33, your scenario will now pass:
1 scenario (1 passed)
17 steps (17 passed)
A browser window will appear, showing you the correct states, as shown in figure 10.14.
Let’s remove the “Then show me the page” step from this scenario now, and you’re
done. You’ve got your application showing the users what state a comment has
switched the ticket to. Now’s a good time to check that you haven’t broken anything.
When you run rake cucumber:ok spec, you should see that everything is A-OK:
49 scenarios (49 passed)
516 steps (516 passed)
# and
33 examples, 0 failures, 16 pending
Figure 10.13 The states aren’t what they should be…
267