Rails%203%20In%20Action

def to_s
name
end
Changing a ticket’s state
By default, objects in Ruby have a to_s method that outputs the ugly version, the
inspected version of this object, you saw earlier. By overriding this in the model to call
the name method, you’ll get it to display the state’s name rather than its object output.
When you refresh the page in your browser, you should see the
correct state, as shown in figure 10.9.
Great! This should mean that the last scenario in your “Creat-
ing comments” feature will pass. Let’s run it with bin/cucumber
features/creating_comments.feature and find out:
1 scenario (1 passed)
14 steps (14 passed)
Indeed it’s passing! This is a good stage to ensure that everything is working by running
rake cucumber:ok spec. Blast, one of the features is failing:
Failing Scenarios:
cucumber features/
creating_comments.feature:26 # Scenario: Creating an invalid comment
A broken feature often means a broken part of your code, so you should investigate
this before continuing. If there are thoughts of “it’s only one feature,” think again. At
what point do you draw the line? One? Two? Three failing scenarios? Let’s have a zerotolerance
policy on these and fix them when they break.
10.2.5 Fixing creating comments
The entire reason why you write features before you write code is so that you can catch
scenarios like this where something unexpectedly breaks. If you didn’t have these scenarios
in place, then you wouldn’t be made aware of these scenarios until a user of
your site stumbled across it. This isn’t what you want. You want your users to assume
that you’re perfect.
You should look into why this feature is failing and fix it right away. This particular
scenario is failing with this backtrace:
And I press "Create Comment"
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.map (ActionView::Template::Error)
./app/views/comments/_form.html.erb:12
Here it claims you’re calling map on a nil object, and that it’s on line 12 of app/views/
comments/_form.html.erb. The line it’s referencing is the following:
Figure 10.9
The correct state
Alright, the only place where map is being called is on the @states variable, so it’s
pretty straightforward that @states is the nil object. But how did it come to be? Let’s
review this scenario, as shown in the following listing.
261