[openstack-dev] [QA] Questions about test policy for scenario test

Yair Fried yfried at redhat.com
Tue Jun 24 11:22:43 UTC 2014

----- Original Message -----

> From: "Fei Long Wang" <feilong at catalyst.net.nz>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Cc: bruno at catalyst.net.nz
> Sent: Tuesday, June 24, 2014 8:29:03 AM
> Subject: [openstack-dev] [QA] Questions about test policy for scenario test

> Greetings,

> We're leveraging the scenario test of Tempest to do the end-to-end
> functional test to make sure everything work great after upgrade,
> patching, etc. And We're happy to fill the gaps we found. However, I'm a
> little bit confused about the test policy from the scenario test
> perspective, especially comparing with the API test. IMHO, scenario test
> will cover some typical work flows of one specific service or mixed
> services, and it would be nice to make sure the function is really
> working instead of just checking the object status from OpenStack
> perspective. Is that correct?

> For example, live migration of Nova, it has been covered in API test of
> Tempest (see
> https://github.com/openstack/tempest/blob/master/tempest/api/compute/test_live_block_migration.py).
> But as you see, it just checks if the instance is Active or not instead
> of checking if the instance can be login/ssh successfully
Seems to me, that what you want is to add migration test to 
This scenario does exactly what you are looking for 
1. check VM connectivity 
2. mess with VM (reboot, resize, or in your case - migrate) 
3. check VM connectivity 

> . Obviously,
> from an real world view, we'd like to check if it's working indeed. So
> the question is, should this be improved? If so, the enhanced code
> should be in API test, scenario test or any other places? Thanks you.

> --
> Cheers & Best regards,
> Fei Long Wang (王飞龙)
> --------------------------------------------------------------------------
> Senior Cloud Software Engineer
> Tel: +64-48032246
> Email: flwang at catalyst.net.nz
> Catalyst IT Limited
> Level 6, Catalyst House, 150 Willis Street, Wellington
> --------------------------------------------------------------------------

> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140624/5bebff26/attachment.html>

More information about the OpenStack-dev mailing list