[openstack-qa] [Tempest] Blueprint: add-scenario-tests

Sean Dague sean at dague.net
Wed Mar 27 13:44:54 UTC 2013


On 03/27/2013 09:43 AM, Jay Pipes wrote:
> On 03/26/2013 09:27 PM, Yaniv Kaul wrote:
>> Without the ability to configure OpenStack,  it's not going to fly.  Configure means:
>> 0. Installation scenarios (installation of different components on different hosts)
>> 1. Ini files manipulation (nova.conf and friends)  and restarting services
>> 2. JSON files manipulation (policy files)
>> 3. Configuration via the API (and/or nova-manage)
>>
>> The above are basic blocks to any true scenario (and end to end) testing.
>> Y.
>
> Tempest does not need to do any of the above. Tempest assumes that
> environment has been set up already, and executes its tests for expected
> behaviour regardless of the configuration of the environment.
>
> Projects like devstack-gate (which runs devstack and configures the
> environments used in continuous integration testing) also write
> Tempest's configuration file, which tells Tempest certain key details
> about the environment it will execute against, including capabilities
> like ability to resize images, perform migrations, etc.
>
> Now what *would* enable better support for scenario testing would be
> API-based discovery of an OpenStack environment's capabilities and
> configuration settings... that would enable Tempest to customize some of
> its settings based on what it can query the OpenStack endpoints for.

My thoughts exactly.

	-Sean

-- 
Sean Dague
http://dague.net



More information about the openstack-qa mailing list