[openstack-dev] [qa][keystone] Help with XML Tempest API tests

Christopher Yeoh cbkyeoh at gmail.com
Fri Nov 1 10:45:13 UTC 2013

On Fri, Nov 1, 2013 at 8:55 PM, Sean Dague <sean at dague.net> wrote:

> On 11/01/2013 04:58 AM, Steven Hardy wrote:
going into testing is finding some real bugs! :) )
>> I notice there's a review associated with that bug, but I can't view it -
>> if it's draft can you please add me to the reviewers list?
>> Looking forward to seeing the patch, as you said the unit test examples
>> should help me complete my Tempest patch.
>> Also note I raised:
>> https://bugs.launchpad.net/**keystone/+bug/1246831<https://bugs.launchpad.net/keystone/+bug/1246831>
>> Which seems somewhat related to this (we get a 500 with the XML encoded
>> expires_at=None, which results in a zero-length string, so the trust
>> controller treats it as a valid timestamp instead of ignoring it)
>> I was planning to send a patch for the latter, but seems like it may
>> overlap with your XML fixes, so I'll hold off for now.
> My experience with the nova API and adding XML testing is that any
> service's XML API is broken by default (because the underlying logic is
> pretty JSON skewed, and the python clients talk JSON). So this isn't very
> surprising. Thanks again for diving into it!
> Honestly, one of these days we should have another serious conversation
> about dropping XML entirely again (across all projects). A single data
> payload that works is way better than additional payloads that don't.
+1 !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131101/bf048326/attachment.html>

More information about the OpenStack-dev mailing list