Hi Cheran, 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.
-Punal On Tue, Aug 16, 2016 at 3:40 PM, Elancheran Subramanian < esubraman...@godaddy.com> wrote: > Hello There, > 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, > Cheran > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
