openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
Doug Hellmann 583ce2c043 Update all Oslo module use 
Use graduated libraries where available and update the incubated modules
that remain.

Update imports for libraries that were being used already to avoid the
'oslo' namespace package.

Update config file for creating example configuration files and provide
a new sample file based on the options defined in the libraries.

Note: because of the number of libraries involved there is no real way
to break this change up into smaller pieces. Fortunately, most of the
changes are just to import statements.

Change-Id: Ia0de957b681cb924a57af98d99a9389ee234ed5b
 		2015-03-11 21:07:56 +00:00
..
README.rst Fix doc for usage of python clients in scenario tests 2014-11-26 17:04:37 +09:00
__init__.py add scenario directory 2013-05-17 08:52:22 -04:00
manager.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_aggregates_basic_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_baremetal_basic_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_dashboard_basic_ops.py Split resource_setup for scenario tests 2015-03-09 01:55:26 +00:00
test_encrypted_cinder_volumes.py Merge "Move to hacking 0.10" 2015-03-04 07:43:34 +00:00
test_large_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_load_balancer_basic.py Split resource_setup for scenario tests 2015-03-09 01:55:26 +00:00
test_minimum_basic.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_network_advanced_server_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_network_basic_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_network_v6.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_security_groups_basic_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_server_advanced_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_server_basic_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_shelve_instance.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_snapshot_pattern.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_stamp_pattern.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_swift_basic_ops.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_swift_telemetry_middleware.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_volume_boot_pattern.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
utils.py Remove migrated utils code 2015-03-06 19:16:10 -05:00

README.rst

Tempest Field Guide to Scenario tests

What are these tests?

Scenario tests are "through path" tests of OpenStack function. Complicated setups where one part might depend on completion of a previous part. They ideally involve the integration between multiple OpenStack services to exercise the touch points between them.

Any scenario test should have a real-life use case. An example would be:

  • "As operator I want to start with a blank environment":
    1. upload a glance image
    2. deploy a vm from it
    3. ssh to the guest
    4. create a snapshot of the vm

Why are these tests in tempest?

This is one of tempests core purposes, testing the integration between projects.

Scope of these tests

Scenario tests should always use the Tempest implementation of the OpenStack API, as we want to ensure that bugs aren't hidden by the official clients.

Tests should be tagged with which services they exercise, as determined by which client libraries are used directly by the test.

Example of a good test

While we are looking for interaction of 2 or more services, be specific in your interactions. A giant "this is my data center" smoke test is hard to debug when it goes wrong.

A flow of interactions between glance and nova, like in the introduction, is a good example. Especially if it involves a repeated interaction when a resource is setup, modified, detached, and then reused later again.