tempest/tempest/scenario
Jenkins e0e6552063 Merge "make schedule_to_every_node use real scheduler hint" 2015-11-13 18:07:26 +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 Merge "Split out Neutron ports client" 2015-11-11 08:39:00 +00:00
test_aggregates_basic_ops.py Merge "Return complete response from compute/aggregates_client" 2015-08-25 05:52:30 +00:00
test_baremetal_basic_ops.py Merge "Modify scenario tests" 2015-11-11 18:44:22 +00:00
test_dashboard_basic_ops.py Fix way to create login_url in dashboard test 2015-09-11 14:39:42 +09:00
test_encrypted_cinder_volumes.py test_minimum_basic: cleanup class scope variable usage 2015-10-14 15:01:12 +02:00
test_large_ops.py Make create_server use **kwargs 2015-09-16 01:43:40 +09:00
test_minimum_basic.py test_minimum_basic: cleanup class scope variable usage 2015-10-14 15:01:12 +02:00
test_network_advanced_server_ops.py test_network_advanced_server_ops: cleanup class scope variable usage 2015-10-14 16:22:03 +02:00
test_network_basic_ops.py Split out Neutron ports client 2015-11-02 09:26:19 -05:00
test_network_v6.py Remove checks for ipv6 utilities before use 2015-10-26 11:34:35 +00:00
test_object_storage_basic_ops.py Rename SwiftScenarioTest to ObjectStorageScenarioTest 2015-09-18 21:15:26 +09:00
test_object_storage_telemetry_middleware.py Rename SwiftScenarioTest to ObjectStorageScenarioTest 2015-09-18 21:15:26 +09:00
test_security_groups_basic_ops.py Split out Neutron ports client 2015-11-02 09:26:19 -05:00
test_server_advanced_ops.py Return complete response from servers_client 2015-09-11 13:05:38 +09:00
test_server_basic_ops.py Modify scenario tests 2015-11-07 11:16:28 +02:00
test_server_multinode.py make schedule_to_every_node use real scheduler hint 2015-11-13 09:38:09 -05:00
test_shelve_instance.py Modify scenario tests 2015-11-07 11:16:28 +02:00
test_snapshot_pattern.py test_snapshot_pattern: cleanup class scope variable usage 2015-10-27 14:05:14 +00:00
test_stamp_pattern.py test_stamp_pattern: cleanup class scope variable usage 2015-10-14 11:50:59 +02:00
test_volume_boot_pattern.py Refactor volume_boot_pattern test 2015-11-05 11:58:03 +02:00
utils.py Stop validating pre-provisioned credentials 2015-10-21 11:06:56 +01: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.