assert_response assumes a rendered template

I am unable to post a comment that includes my ruby source code -LH blows up. But the code example is pretty simple: implement a rescue_action_in_public and render a string directly instead of a template. That's a common practices for XML and JSON error messages.

Also attaching a patch that fixes the problem. Tests to come.

Here's a pastie of the code that causes LH to barf:

http://pastie.caboo.se/193322

NB: Even if I remove the "@@@ ruby" tag, it doesn't help.

I can write a failing test against 2.0.2, but to get one against edge is going to take me a while. Would 2.0.2 be good enough?

-Chris

One against edge would be nicer. But if you can't, then 2.0.x is fine too and I'll try to port it to edge.

Thanks.

Jeremy fixed this already in Edge (Commit eb837b52e34c1f7f0c71d704ffdb3e4eb4b582e2).

Since I had gone to the trouble of writing a failing test before I found Jeremy's patch on Edge, I figured it would be a good idea to add the test anyway.

Attached is a patch against Edge that validates assert_response's behavior faced with a failure response but no exception.

Automatic cleanup of spam.