[openstack-dev] [Neturon][Tempest] A test scenario for services

Nachi Ueno nachi at ntti3.com
Thu Nov 14 05:23:04 UTC 2013


Hi Eugene

Thanks.
Anyway, we need more API test for each services with fine coverage.
so if using only tempest is simple for you, please continue it.

I'll create the heat template mentioned in the slide.
so we can use that.

Best
Nachi


2013/11/14 Eugene Nikanorov <enikanorov at mirantis.com>:
> Hi Nachi and folks,
>
> Thanks for bringing this up.
> We started working on basic scenario testing for lbaas using tempest
> clients.
> We'll consider using heat for it.
> However I think we'll get something simple working at first (since we're not
> yet experts in tempest) then move to more complex topologies and scenarios.
>
> Thanks,
> Eugene.
>
>
> On Thu, Nov 14, 2013 at 7:47 AM, Nachi Ueno <nachi at ntti3.com> wrote:
>>
>> Hi Salvatore, Sumit
>>
>> > Salvatore
>> Thank you for your comment. I replied on the google doc.
>>
>> > Sumit
>> I think we need also API testing anyway (including negative test).
>> My idea is use heat api (heat also has tempest) for scenario testing
>> for more simplified testing code.
>> The good point of this is we can recreate the same env with tempest
>> just using heat.
>>
>> sometimes, it is hard to debug because tempest cleanup resources.
>> If we can use heat too, it should help debugging.
>>
>> Best
>> Nachi
>>
>>
>>
>>
>>
>>
>>
>>
>> 2013/11/14 Sumit Naiksatam <sumitnaiksatam at gmail.com>:
>> > Thanks Nachi. So is the suggestion to not have tempest tests (testing
>> > API)
>> > for each individual service?
>> >
>> > ~Sumit.
>> >
>> >
>> > On Wed, Nov 13, 2013 at 5:55 PM, Nachi Ueno <nachi at ntti3.com> wrote:
>> >>
>> >> Hi Sumit, Eugene
>> >>
>> >> How about to have one test scenario for services?
>> >> IMO, we need to combine LBaaS, FWaaS, VPNaaS scenario tests
>> >> because of utilization of test resources.
>> >>
>> >> I wrote my proposal here.
>> >>
>> >>
>> >> https://docs.google.com/presentation/d/1gu12liw-9el_pR_FDQ7qDRuFpnSXxVzOsp6K0ZzX-_o/edit#slide=id.g295949ab9_016
>> >>
>> >> I'm thinking about to use Heat for this testing, because we can re-use
>> >> the heat template.
>> >>
>> >> Best
>> >> Nachi
>> >>
>> >> _______________________________________________
>> >> OpenStack-dev mailing list
>> >> OpenStack-dev at lists.openstack.org
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>



More information about the OpenStack-dev mailing list