Describing conditions that will cause an error response

[mohsen1]

This is for Swagger.next

With Swagger we can define error responses but there is no way to describe what will cause an error response. Things like auth, missing or invalid parameter can easily described in the specs. Should we have a way for such description in Swagger?

[mohsen1]

This will lead to better tooling for tests. If we describe how you can get an error, tooling can use that and test different responses

[webron]

Wouldn't that just be part of the "description" of the response?
https://github.com/wordnik/swagger-spec/blob/master/versions/2.0.md#responseDescription

[jharmn]

FWIW, this could also be defined by specifying HTTP status codes which occur for the given errors (401/403 for auth, 400 for validation errors etc).

#236 seems to address the perceived need for more error-specific handling of responses, let's look at it from that perspective.