Hi! I have I question regarding validating responses during API tests.
Has it been decided some time ago that no additional properties are allowed when verifying response schemas during API tests? I have an OpenStack based product that contains few additional properties in it's compute API and few tempest cases fail like: tempest_lib.exceptions.InvalidHTTPResponseBody: HTTP response body is invalid json or xml Details: HTTP response body is invalid (Additional properties are not allowed (u'nics' was unexpected) So currently I have to update related schema descriptions located under tempest/api_schema/ in order to get those tests passed. Just wondering if there is some more convenient way to handle such kind of drawbacks. Could this schema validating be more flexible (e.g. with posibility to define additional properties in some single place like tempest.conf file)? -Viktor __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
