[openstack-dev] [QA] Running Tempest tests for a customized cloud
esubramanian at godaddy.com
Wed Aug 17 00:27:29 UTC 2016
We do support both V2 and V3, that’s just a example I’ve stated BTW. We do have our own integration tests which are pretty much covers all our integration points with openstack. But we would like to leverage the tempest while doing our upstream merge for openstack components in CI.
I believe the tests support the include list, how can I exclude test? Any pointer would be a great help.
From: punal patel <punal.patel at gmail.com<mailto:punal.patel at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, August 16, 2016 at 4:16 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud
Best practice depends on your test plan and what coverage you. Does your test plan covers V3 Identity tests ? If it does and its failing, you should modify to make it work for your environment. Fast way to move forward is to exclude those tests.
On Tue, Aug 16, 2016 at 3:40 PM, Elancheran Subramanian <esubramanian at godaddy.com<mailto:esubramanian at godaddy.com>> wrote:
I’m currently playing with using Tempest as our integration tests for our internal and external clouds, facing some issues with api which are not supported in our cloud. For ex, listing domains isn’t supported for any user, due to this V3 Identity tests are failing. So I would like to know what’s the best practice? Like fix those tests, and apply those fix as patch? Or just exclude those tests?
Would be great if anyone could share their experience on this.
Thanks & Regards,
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStackemail@example.com?subject:unsubscribe>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev