History

Zuul a560f73666 Merge "Allow kwargs in _get_router"		2021-02-10 17:17:04 +00:00
..
README.rst	Fix docs markup consistency	2017-11-21 19:02:54 +09:00
__init__.py	add scenario directory	2013-05-17 08:52:22 -04:00
manager.py	Merge "Allow kwargs in _get_router"	2021-02-10 17:17:04 +00:00
test_aggregates_basic_ops.py	Skip adding host to aggregate with az if host already in other zone	2020-10-12 20:10:25 +00:00
test_dashboard_basic_ops.py	Move horizon test from tempest-horizon to tempest	2021-01-22 00:11:44 +00:00
test_encrypted_cinder_volumes.py	test_encrypted_cinder_volumes: Do not create an image for this test	2021-01-22 10:10:32 +00:00
test_minbw_allocation_placement.py	Test for changing QoS policy with min bw of bound port	2021-01-28 20:20:31 +01:00
test_minimum_basic.py	Use of single interface for creating image	2020-08-28 12:14:25 +05:30
test_network_advanced_server_ops.py	Set image_alt_ssh_user during stack	2020-11-04 16:02:37 +01:00
test_network_basic_ops.py	Merge "Remove any reference to "tenant_id" in network"	2020-07-10 00:40:03 +00:00
test_network_v6.py	Make _log_console_output non-private	2021-02-04 22:05:57 +05:30
test_object_storage_basic_ops.py	docs: Fix incorrect docstrings in reStructuredText format	2018-11-21 19:06:43 -06:00
test_security_groups_basic_ops.py	Merge "Make _create_security_group_rule non-private"	2021-02-10 08:02:23 +00:00
test_server_advanced_ops.py	Create default network for server advance scenario tests	2021-02-08 16:58:07 -06:00
test_server_basic_ops.py	1912117: Fix the IP URL for metadata service in fixed network scenario	2021-01-18 19:35:27 +00:00
test_server_multinode.py	Move test decorators to common	2017-08-23 17:09:33 +00:00
test_shelve_instance.py	Add related test to Bug #1732428	2020-11-19 07:38:59 +00:00
test_snapshot_pattern.py	Add image "version" metadata in test_snapshot_pattern	2020-05-22 16:53:48 +00:00
test_stamp_pattern.py	Remove unused LOG var in test_stamp_pattern.py	2020-12-08 14:24:06 +00:00
test_volume_backup_restore.py	Add status check for creating volume backup	2018-06-19 01:08:28 +00:00
test_volume_boot_pattern.py	Use new encryption provider constants (reprise)	2020-04-22 12:34:46 +02:00
test_volume_migrate_attached.py	Introduce an attached volume migration test	2019-04-25 10:34:58 +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 Tempest's 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.