openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
Masayuki Igawa 22b3008661 Remove unused service tags and client 
This commit removes unused service tags and a client. We should keep our
code clean as possible.

Change-Id: I428ac6740feaaabdd17a02a03ea5230d202d89d2
 		2016-06-28 15:09:31 +09: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 Remove unused service tags and client 2016-06-28 15:09:31 +09:00
test_aggregates_basic_ops.py Scenarios: remove trivial wrapper methods 2016-01-26 17:10:55 +01:00
test_baremetal_basic_ops.py Remove some dead code 2016-02-16 14:01:57 +00:00
test_encrypted_cinder_volumes.py Migrate scenario tests ssh-auth-strategy 2015-12-01 16:02:01 +00:00
test_minimum_basic.py Scenarios: remove trivial wrapper methods 2016-01-26 17:10:55 +01:00
test_network_advanced_server_ops.py Merge "Remove neutron OO wrappers" 2016-06-15 18:43:59 +00:00
test_network_basic_ops.py Remove neutron OO wrappers 2016-06-14 21:10:03 -05:00
test_network_v6.py Remove neutron OO wrappers 2016-06-14 21:10:03 -05:00
test_object_storage_basic_ops.py Trival: Remove unused logging import in some files 2016-01-06 16:22:53 +08:00
test_security_groups_basic_ops.py Remove neutron OO wrappers 2016-06-14 21:10:03 -05:00
test_server_advanced_ops.py Revert "Skip test_resize_volume_backed_server_confirm for now" 2016-05-11 19:35:14 +00:00
test_server_basic_ops.py Fix AttributeError with run_validation=true 2016-06-24 16:04:08 +09:00
test_server_multinode.py Merge "Trival: Remove unused logging import in some files" 2016-01-13 11:16:00 +00:00
test_shelve_instance.py Move shelve server logic in compute utility 2016-04-15 18:49:26 +09:00
test_snapshot_pattern.py Merge "Remove redundant import from scenario tests" 2016-02-06 00:42:36 +00:00
test_stamp_pattern.py Use common "waiters.wait_for_snapshot_status" function everywhere 2016-03-25 16:39:35 +00:00
test_volume_boot_pattern.py Use common "waiters.wait_for_snapshot_status" function everywhere 2016-03-25 16:39:35 +00: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.