Forum: Ruby on Rails Can't seem to test http error codes

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
davetron5000 (Guest)
on 2008-11-17 18:39
(Received via mailing list)
in application.rb

  rescue_from ActiveRecord::RecordNotFound   { |e| http_status_code
(:missing, e) }

  def http_status_code(status, exception)
    @exception = exception
    respond_to do |format|
      format.html { render :template => "shared/status_#
{status.to_s}", :status => status }
      format.any  { head status }

in a controller

    project = Project.find(params[:id])

in my test

  def test_bad_project
    put :update, :id => KNOWN_BAD_ID

The result is that I get a 500 every time.

Any clues as to whats' going on?  There's nothing in the log to
explain the 500 I get during tests; the application controller seems
to be detecting the exception and setting the status to 404, but my
tests get 500.

Frederick C. (Guest)
on 2008-11-17 18:54
(Received via mailing list)
On 17 Nov 2008, at 16:39, davetron5000 wrote:

> {status.to_s}", :status => status }
>      format.any  { head status }
>    end
>  end
IIRC the test harness snarfs the exception before it gets to your
exception handler.

davetron5000 (Guest)
on 2008-11-17 20:27
(Received via mailing list)
The exception handler IS getting called (I put log statements in and
they appear in test.log).

In previous versions of rails, there seemed to be some sort of magic
where a non-200 http response gets turned into a 500 for development,
but not production.  Is that the case, and if so, how do I deal with
this?  I need to test that the correct http responses are being


On Nov 17, 11:54 am, Frederick C. <removed_email_address@domain.invalid>
This topic is locked and can not be replied to.