If there is an response that sends a content-type that matches a response handler, but the response does not actually match the content-type (can't be parsed etc) this can lead to problematic errors.
Two things may need to happen:
more effectively handle the bad parsing (better error message and smoother failure)
allow the test to declare "don't use any handlers here"
This is (sadly) necessary to be able to run tests (or run gabbi in whatever way) against poorly formed APIs that send bad response headers.
Whether this is done as a boolean parameter related to "no handlers" or something like a content-type-override needs to be decided.
If there is an response that sends a content-type that matches a response handler, but the response does not actually match the content-type (can't be parsed etc) this can lead to problematic errors.
Two things may need to happen:
This is (sadly) necessary to be able to run tests (or run gabbi in whatever way) against poorly formed APIs that send bad response headers.
Whether this is done as a boolean parameter related to "no handlers" or something like a content-type-override needs to be decided.