[TASK] set issuer on destination_amount attribute in ripple-rest

But it is immediately clear. You'll get the expected/actual JSON representation, and you should see missing or invalid properties. Maybe the error is harder to detect with path tests. Most of the time the response is concise enough that it's pretty obvious what's wrong. I don't agree that there is any lack of `expressiveness`.

>As a reader of the test case, I cannot immediately understand what properties are relevant without first opening up a fixture file.

This is true for the mock rippled responses as well as the ripple-rest-formatted responses. I made the decision to not cram all of the content into one file. You *do* have to read the fixtures files to see what the full input/output looks like (in most cases). This is ok, probably even better.

>To answer your question about if a response is missing more than one property

Yeah... my point was that you'll have to re-run the test for every missing property, rather than seeing everything that's missing at once, making it not-easier. Like I said, maybe this [your method] makes more sense for path tests that are harder to parse.