Open Stack

On Tue, Jul 16, 2013 at 06:15:39PM +0000, Daryl Walleck wrote:
> My two cents, but would it be less painful to have this as a command line option (run_tests --exclude cinder, networks) ? It seems like that would be more flexible than having to manipulate config files to determine which tests are run.
> 

The config options are there for the case when neutron or cinder aren't
running. Yes, you can always manually exclude those tests in that case but 
whether or not your environment has certain projects running is really
configuration information. It also has the advantage of printing skip messages
for those tests, while the exclude flag just filters those tests out of the list
of which tests get run.

-Matt Treinish

> Daryl
> ________________________________
> From: Jay Buffington [me at jaybuff.com]
> Sent: Tuesday, July 16, 2013 1:06 PM
> To: openstack-qa at lists.openstack.org
> Subject: [openstack-qa] Disable all volume tests?
> 
> My openstack installation does not include volume storage.  I want to run tempests against it, but I get a lot of errors/failures related to cinder.  For example, all the tests in tempest.api.compute.volumes error.
> 
> I see that BaseVolumeTest skips tests when it can't find a cinder endpoint, but that code doesn't get run for tests under tempest.api.compute.
> 
> Perhaps tempest should having a setting to skip all tests that require cinder:
> 
>     [volume]
>     cinder_available = false
> 
> Is there a way to do this that I'm missing?  Or should I add a blueprint/bug for this?
> 
> Thanks,
> Jay

> _______________________________________________
> openstack-qa mailing list
> openstack-qa at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa