Rails%203%20In%20Action

106 CHAPTER 5 Nested resources
Then create the view for this action at app/views/tickets/show.html.erb using this code:
The new method, simple_format, converts the line breaks 1 entered into the description
field into HTML break tags () so that the description renders exactly how the
user intends it to.
Based solely on the changes that you’ve made so far, your first scenario should be
passing. Let’s see with a quick run of bin/cucumber features/creating_tickets
.feature:
Then I should see "Ticket has been created."
...
2 scenarios (1 failed, 1 passed)
16 steps (1 failed, 2 skipped, 13 passed)
This means that you’ve got the first scenario under control and that users of your
application can create tickets within a project. Next, you need to add validations to
the Ticket model to get the second scenario to pass.
5.1.6 Ticket validations
The second scenario fails because the @ticket that it saves is valid, at least according
to your application in its current state:
expected there to be content "Ticket has not been created" in "[text]"
You need to ensure that when somebody enters a ticket into the application, the
title and description attributes are filled in. To do this, define the following validations
inside the Ticket model.
Listing 5.6 app/models/ticket.rb
validates :title, :presence => true
validates :description, :presence => true
Now when you run bin/cucumber features/creating_tickets.feature, the entire
feature passes:
2 scenarios (2 passed)
16 steps (16 passed)
Before we wrap up here, let’s add one more scenario to ensure that what is entered
into the description field is longer than 10 characters. You want the descriptions to be
useful! Let’s add this scenario to the features/creating_tickets.feature file:
Scenario: Description must be longer than 10 characters
When I fill in "Title" with "Non-standards compliance"
And I fill in "Description" with "it sucks"
1 Line breaks are represented as \n and \r\n in strings in Ruby rather than as visible line breaks.