One thing I wanted to bring up was the design decision to include the JSON bodies statically within each test. I can see this causing severe headaches down the road as the specification changes. What I really liked about the test suite I had started with was the ability to have the format of a request abstracted away from the test itself so that when modifications are made that we only have one place to fix instead of many. The only solution I can think of based on the current framework would be to use helper methods to construct the body and pass it back to the test. An approach that would allow us to flip between using JSON and XML bodies also probably wouldn't be a bad idea.
One thing I wanted to bring up was the design decision to include the JSON bodies statically within each test. I can see this causing severe headaches down the road as the specification changes. What I really liked about the test suite I had started with was the ability to have the format of a request abstracted away from the test itself so that when modifications are made that we only have one place to fix instead of many. The only solution I can think of based on the current framework would be to use helper methods to construct the body and pass it back to the test. An approach that would allow us to flip between using JSON and XML bodies also probably wouldn't be a bad idea.