Rails%203%20In%20Action

to this:
The projects API
before_filter :find_project, :only => [:show, :update]
Now in the update action you’ll have a project that you can work with because this
before_filter will find it for you. Next, you’ll write this action into the controller
using the code from the following listing.
Listing 13.18 app/controllers/api/v1/projects_controller.rb
def update
@project.update_attributes(params[:project])
respond_with(@project)
end
Well isn’t this quite a difference from your standard update actions? You only need to
call update_attributes here, which will save the object and return a valid object in
the format that you’ve asked for. If this object fails validation, the status code returned
by respond_with will be 422, which represents an Unprocessable Entity, and the body
will contain only the validation errors that occurred. If the object is valid,
respond_with will return a 200 status code, but an empty response. This is because
the client should be aware of what changes it has made to the object, and so there’s no
need to send back the object.
So which is it? Does the update action work and return the 200 status code you
want, or does it break? It’s easy to find out by running bin/rspec spec/api/v1/
projects_spec.rb:
5 examples, 0 failures
All working, good stuff. You’ve now got a check that the update action responds correctly
when a valid object is given, but what if invalid parameters are given instead?
Well, the action should return that 422 response mentioned earlier. Although this is
testing the already extensively tested 13 Rails behavior, you’re making sure that this
action always does what you think it should. No misbehaving allowed! You’ll quickly
whip up a spec for this, placing it right underneath the previous example, “successful
JSON” that you wrote in spec/api/v1/projects_spec.rb. The code for it is shown in the
following listing.
Listing 13.19 spec/api/v1/projects_spec.rb
it "unsuccessful JSON" do
@project.name.should eql("Ticketee")
put "#{url}.json", :token => token,
:project => {
:name => ""
}
last_response.status.should eql(422)
13 It’s tested within Rails itself.
371