History

Jenkins aa34225ab8 Merge "Apply a naming rule of GET to compute clients(f*)"		2015-06-10 07:22:17 +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 "Remove extra return value from scenario call to show_router"	2015-05-29 14:54:09 +00:00
test_aggregates_basic_ops.py	Initial class creds creation in test base class	2015-04-27 15:23:13 +01:00
test_baremetal_basic_ops.py	Apply a naming rule of GET to compute clients(f*)	2015-06-08 05:31:07 +00:00
test_dashboard_basic_ops.py	Switch all uses of urllib and HTMLParser to import from six	2015-05-10 12:46:20 -04:00
test_encrypted_cinder_volumes.py	Distinguish between luks and cryptsetup volume types	2015-03-13 09:50:52 -07:00
test_large_ops.py	Fix server creation n test_large_ops	2015-05-07 09:10:07 +02:00
test_load_balancer_basic.py	Switch all uses of iteritems to use six instead	2015-05-10 12:46:22 -04:00
test_minimum_basic.py	Apply a naming rule of GET to volume client	2015-04-07 05:24:00 +00:00
test_network_advanced_server_ops.py	Merge "Allow sress test runner to skip based on available services"	2015-03-20 22:48:40 +00:00
test_network_basic_ops.py	not all scenario tests should be in smoke	2015-04-29 06:05:50 -04:00
test_network_v6.py	Check IPv6 mupltiprefix feature	2015-05-12 13:46:05 +03:00
test_security_groups_basic_ops.py	Merge "Introduce creds_provider in test.py"	2015-05-13 15:26:40 +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	Ensure scenario utils creds are cleaned up	2015-05-15 13:02:03 -04: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	Replace "hardcode" in scenario tests	2015-05-25 21:34:47 +03: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	Merge "Remove skip for bug 1439371 on test_volume_boot_pattern"	2015-05-26 15:43:51 +00:00
utils.py	Apply a naming rule of GET to compute clients(f*)	2015-06-08 05:31:07 +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.