Rails%203%20In%20Action

Creating tickets
Alternative validation syntax
You can use a slightly differently named method call to accomplish the same thing
here:
validates_presence_of :title
validates_presence_of :description
Some people prefer this syntax because it’s been around for a couple of years; others
prefer the newer style. It’s up to you which to choose. A number of other
validates_* methods are available.
And I press "Create Ticket"
Then I should see "Ticket has not been created."
And I should see "Description is too short"
The final line here is written this way because you do not know what the validation
message is, but you’ll find out later. To implement this scenario, add another option
to the end of the validation for the description in your Ticket model, as shown in
the following listing.
Listing 5.7 app/models/ticket.rb
validates :description, :presence => true,
:length => { :minimum => 10 }
If you go into rails console and try to create a new Ticket object by using create!,
you can get the full text for your error:
irb(main):001:0> Ticket.create!
ActiveRecord::RecordInvalid: ... Description is too short
(minimum is 10 characters)
That is the precise error message you are looking for in your feature. When you run
bin/cucumber features/creating_tickets.feature again, you see that all three scenarios
are now passing:
3 scenarios (3 passed)
25 steps (25 passed)
You should ensure that the rest of the project still works. Because you have both features
and specs, you should run the following command to check everything:
rake cucumber:ok spec
The summary for these two tasks together is 2
9 scenarios (9 passed)
62 steps (62 passed)
# and
5 examples, 0 failures, 4 pending
2 The summary is altered to cut down on line noise with only the important parts shown.
107