Rails%203%20In%20Action

262 CHAPTER 10 Tracking state
Listing 10.16 features/creating_comments.feature:26
Scenario: Creating an invalid comment
When I follow "Change a ticket's state"
And I press "Create Comment"
Then I should see "Comment has not been created."
And I should see "Text can't be blank"
This scenario tests that you’re shown the “Text can’t be blank” error when you don’t
enter any text for your comment. In this scenario, you click the Create Comment button,
which submits your form, which goes to the create action in Comments-
Controller. This action looks like the following listing.
Listing 10.17 app/controllers/comments_controller.rb
def create
@comment = @ticket.comments.build(params[:comment].merge(:user
➥=> current_user))
if @comment.save
flash[:notice] = "Comment has been created."
redirect_to [@ticket.project, @ticket]
else
flash[:alert] = "Comment has not been created."
render :template => "tickets/show"
end
end
As you can see from this action, when the comment fails validation (when @comment
.save returns false), then it rerenders the app/views/tickets/show.html.erb template.
The problem with this is that, by rerendering this template, it calls the following line
in the template:
This inevitably leads you right back to app/views/comments/_form.html.erb, the
source of the problem. Therefore, you can determine that you need to set up the
@states variable during the “failed save” part of your action, and the best place for
this is right after the else so that this part ends up looking like the following listing.
Listing 10.18 app/controllers/comments_controller.rb
else
@states = State.all
flash[:alert] = "Comment has not been created."
render :template => "tickets/show"
end
Now that you’re correctly initializing your @states variable, this scenario will pass.
Let’s run the whole feature now using bin/cucumber features/creating_comments
.feature:
3 scenarios (3 passed)
39 steps (39 passed)