Luigi, >From my point of view, Tempest should verify Cinder for DefCore requirements [1] only. Such integration tests won't be just a re-implementation if a Tempest tests. It will me more extended set of tests for integration between cinderclient and other projects.
[1] https://github.com/openstack/defcore Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Wed, Mar 2, 2016 at 1:20 PM, Luigi Toscano <ltosc...@redhat.com> wrote: > On Wednesday 02 of March 2016 12:24:57 Ivan Kolodyazhny wrote: > > Sean, > > > > I do understand why we have tempest for python-cinderclient now. > > > > But my point is: tempest runs more than 200 tests per each cinderclient > > change request which takes a lot of time. Why can't we just introduce few > > integration tests which will tests nova<=>python-cinderclient API. > > > > Also, Nova is not only one consumer of cinderclient. What about Heat? We > > don't want to break it too but to run all Heat-related Tempest tests is > not > > a good idea. We have to implement integration tests between Heat and > > python-cinderclient too. > > So you want to reimplement the tests you already have in Tempest? If the > issue > is the time, why not run a relevant subset of the tempests tests? > > Ciao > -- > Luigi > >
__________________________________________________________________________ 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
