Rails%203%20In%20Action

90 CHAPTER 4 Oh CRUD!
4.2.2 The update action
As the following listing shows, you can now define this update action underneath the
edit action in your controller.
Listing 4.9 app/controllers/projects_controller.rb
def update
@project = Project.find(params[:id])
@project.update_attributes(params[:project])
flash[:notice] = "Project has been updated."
redirect_to @project
end
Notice the new method here, update_attributes. It takes a hash of attributes identical
to the ones passed to new or create, updates those specified attributes on the
object, and then saves them to the database if they are valid. This method, like save,
returns true if the update is valid or false if it is not.
Now that you’ve implemented the update action, let’s see how the feature is going
by running bin/cucumber features/editing_projects.feature:
1 scenario (1 passed)
8 steps (8 passed)
What happens if somebody fills in the name field with a blank value? The user receives
an error, just as in the create action. You should move the first four steps from the
first scenario in features/editing_projects.feature into a Background so the Feature
now looks like the following listing.
Listing 4.10 features/editing_projects.feature
Feature: Editing Projects
In order to update project information
As a user
I want to be able to do that through an interface
Background:
Given there is a project called "TextMate 2"
And I am on the homepage
When I follow "TextMate 2"
And I follow "Edit Project"
Scenario: Updating a project
And I fill in "Name" with "TextMate 2 beta"
And I press "Update Project"
Then I should see "Project has been updated."
Then I should be on the project page for "TextMate 2 beta"
Now you can add a new scenario, shown in the following listing, to test that the user is
shown an error message for when the validations fail on update directly under the
other scenario in this file.