[openstack-dev] [all] removing XML testing completely from Tempest
lbragstad at gmail.com
Mon Nov 24 17:36:10 UTC 2014
We are in the process of removing XML support from Keystone  and have
configuration options to Tempest for testing XML in older releases .
identity client is still tightly coupled to XML test cases. We can either
fix the 309 test cases
that use the XML identity client or let those cases be removed from
Tempest. I'd like to let this
air out a bit before I start fixing the identity client XML issues, in case
XML testing is completely
removed from Tempest.
On Mon, Nov 24, 2014 at 8:03 AM, Jay Pipes <jaypipes at gmail.com> wrote:
> On 11/24/2014 08:56 AM, Sean Dague wrote:
>> Having XML payloads was never a universal part of OpenStack services.
>> During the Icehouse release the TC declared that being an OpenStack
>> service requires having a JSON REST API. Projects could do what they
>> wanted beyond that. Lots of them deprecated and have been removing the
>> XML cruft since then.
>> Tempest is a tool to test the OpenStack API. OpenStack hasn't had an XML
>> API for a long time.
>> Given that current branchless Tempest only supports as far back as
>> Icehouse anyway, after these changes were made, I'd like to propose that
>> all the XML code in Tempest should be removed. If a project wants to
>> support something else beyond a JSON API that's on that project to test
>> and document on their own.
>> We've definitively blocked adding new XML tests in Tempest anyway, but
>> getting rid of the XML debt in the project will simplify it quite a bit,
>> make it easier for contributors to join in, and seems consistent with
>> the direction of OpenStack as a whole.
> But Sean, without XML support, we will lose all of our enterprise
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev