Change Details

Swagger spec entry points potentially specify a JSON spec for the return value. Currently, we ignore this spec in x-ample tests, which leads to some amount of duplication. A lot of x-ample response assertions are only asserting the presence of mandatory attributes, which is also covered by the schema. I think it would be attractive to validate responses against the JSON schema when available, before executing other x-ample assertions. This way we can reduce the duplication between x-ample and the schema, and make sure that the schema reflects actual output. @mobrovac, @eevans, @bearnd, @yurik, @joe, @pchelolo, @sniedzielski, @arlolra: Any thoughts?