We really should! I hate this code. I think that's a separate pull req, one that I think should also include coming up with some JSON middleware that auto-serializes responses as JSON. If we have our endpoints use that, then I don't think there's much value anymore in re-verifying that in every single HTTP test file.

This code in particular is a bit special...as the result of hitting "/v2/resources" is now a PipedInputStream, we actually need to slurp that into a string for the test cases to work (because they don't know how to deal with streams). A real Jetty instance does that automatically, but as this is just hitting our ring app directly without going through Jetty, we have to deal with the raw stream.