ario tests which are in Tempest
>> >>> scope
>> >>> because that can make confusion for developers (where to add scenario
>> >>> tests)
>> >>> as well as for tester(from where to run what scenario tests).
>> >>>
>> >>
o add scenario
> tests)
> >>> as well as for tester(from where to run what scenario tests).
> >>>
> >>> 3. How we make sure those tests run fine or at least run while
> >>> adding.
> >>>
> >>> a. I think devst
> a. I think devstack enhancement for multi-node etc can do this as
>>> mentioned by you also.
>>>
>>> b. If so then why not adding those tests in Tempest only using
>>> os-faults lib ?
>>>
>>>
>>>
>>> Overall I f
dea but tests scope can
>> go in Tempest under HW_scenario (or something else) till it does not break
>> basic principle of Tempest.
>>
>>
>>
>> Thanks
>>
>> gmann
>>
>>
>>
>> From: Timur Nurlygayanov [mailto:tnurlyga
*Sent:* 06 October 2016 20:09
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [QA] The end-user test suite for OpenStack
> clusters
>
>
>
> Ken, it is a good idea!
>
>
ct: Re: [openstack-dev] [QA] The end-user test suite for OpenStack clusters
Ken, it is a good idea!
The plan is to develop os-faults as a library which will be able
to manage cluster nodes and OpenStack services on these nodes.
It is a good idea to add some Tempest tests which will use
os-faults library a
Hi Timur,
I discussed this on irc, and it seems hard to get feedback from many
people because now the scope and implementation of this os-faults are
separated into multiple pieces(like multiple mails, github code,
gerrit etc).
So how about proposing this as qa-spec?
If doing that, We can discuss
Hi,
My first impression is "It's interesting" :)
I actually don't read whole of this threads, but, I re-read the QA
mission statement[1].
I feel os-faults is a little bit far from the mission statement.
Because os-faults seems like focusing on operator testing.
But I think this can be under the
Hi Timur,
2016-10-06 4:08 GMT-07:00 Timur Nurlygayanov :
> Ken, it is a good idea!
>
> The plan is to develop os-faults as a library which will be able
> to manage cluster nodes and OpenStack services on these nodes.
> It is a good idea to add some Tempest tests which
Ken, it is a good idea!
The plan is to develop os-faults as a library which will be able
to manage cluster nodes and OpenStack services on these nodes.
It is a good idea to add some Tempest tests which will use
os-faults library as well for some API tests.
The Stepler framework [1] will use
Hi Ken,
OS-Faults doesn't have any scenarios in the tree yet (the project is two
months old), but you can find some examples of the use in the
os-faults/examples directory.
Regards,
Yaroslav Lobankov.
On Tue, Oct 4, 2016 at 8:02 PM, Ken'ichi Ohmichi
wrote:
> Hi Timur,
>
Hi Timur,
Thanks for your explanation.
2016-09-29 6:22 GMT-07:00 Timur Nurlygayanov :
>
>> I am guessing the above "restart nodes" is for verifying each
>> OpenStack service restarts successfully, right?
>
> Yes, this is right. And we also will check that HA logic for
Hi Ken,
I am guessing the above "restart nodes" is for verifying each
> OpenStack service restarts successfully, right?
Yes, this is right. And we also will check that HA logic for these
services works correctly (for example, rescheduling of L3 Neutron
agents for networks).
But these service
Hi Timur,
Thanks for picking this up, that is interesting for me.
2016-09-22 5:58 GMT-07:00 Timur Nurlygayanov :
>
> we have an idea to create the test suite with destructive/HA and advanced
> end-user scenarios for the OpenStack clusters. This test suite will
14 matches
Mail list logo