History

Jenkins 52225ece39 Merge "Fallback to creds provider for fixed IP network if no network_for_ssh"		2016-10-13 00:21:44 +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 "Fallback to creds provider for fixed IP network if no network_for_ssh"	2016-10-13 00:21:44 +00:00
test_aggregates_basic_ops.py	Scenarios: remove redundant call to `resource_setup()`	2016-09-16 15:00:32 +02:00
test_baremetal_basic_ops.py	Remove a word 'smoke' from some scenario tests	2016-08-31 16:44:39 -07:00
test_encrypted_cinder_volumes.py	Lower the aes-xts-plain64 key_size to 256	2016-08-23 15:38:34 -04:00
test_minimum_basic.py	Wait for floating_ip to detach from server after deletion	2016-09-27 17:56:00 +08:00
test_network_advanced_server_ops.py	Remove _setup_network_and_servers() in TestNetworkAdvancedServerOps	2016-09-15 10:21:50 -04:00
test_network_basic_ops.py	Update hotplug test description.	2016-09-29 07:29:36 +00:00
test_network_v6.py	Move `call_until_true` to tempest/lib	2016-09-02 18:03:37 +02:00
test_object_storage_basic_ops.py	Remove unused config.CONF	2016-08-29 10:34:08 +08:00
test_security_groups_basic_ops.py	Use a common method for is a router interface	2016-10-07 20:42:24 +02: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	Move `call_until_true` to tempest/lib	2016-09-02 18:03:37 +02:00
test_server_multinode.py	Scenarios: remove redundant call to `resource_setup()`	2016-09-16 15:00:32 +02:00
test_shelve_instance.py	Fix test_shelve_volume_backed_instance	2016-08-16 21:26:50 -07:00
test_snapshot_pattern.py	Use skip_checks in test_snapshot_pattern	2016-07-25 11:19:36 +08:00
test_stamp_pattern.py	Move `call_until_true` to tempest/lib	2016-09-02 18:03:37 +02:00
test_volume_boot_pattern.py	Moving scenario docstring under the relevant test method	2016-10-04 17:08:42 +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":

upload a glance image

deploy a vm from it

ssh to the guest

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.