[openstack-qa] automatically skipping tests based on config

Sean Dague sdague at linux.vnet.ibm.com
Fri Mar 1 15:11:22 UTC 2013


On 03/01/2013 04:56 AM, Christopher Yeoh wrote:
> On Wed, 27 Feb 2013 13:23:32 -0500
> Sean Dague <sdague at linux.vnet.ibm.com> wrote:
>
>> On 02/27/2013 06:18 AM, Christopher Yeoh wrote:
>>> Hi,
>>>
>>> Any suggestions/comments?
>>
>> If we didn't quietly skip, it would have blocked the devstack change,
>> which is what we want. If a tempest config file variable is there,
>> but not right, it should be a fail, not a skip. Would that have fixed
>> this?
>
> Yes I think we'd make it similar to the situation now when there is an
> API change. Before putting through the image version change in devstack
> they would deliberately disable the tests, bump the version number in a
> devstack changeset, then re-enable the tests again.

Yeh, the "tempest two-step", which I think is the right approach.

Every skip should be required to have a bug number on it, so we can 
realize that the bugs are closed and we should now unskip.

	-Sean

-- 
Sean Dague
IBM Linux Technology Center
email: sdague at linux.vnet.ibm.com
alt-email: sldague at us.ibm.com




More information about the openstack-qa mailing list