openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
Matt Riedemann ebaf245369 Skip ebs scenario test due to bug 1489581 
test_create_ebs_image_and_check_boot race fails frequently in
the cells and ceph jobs, so we need to skip it for now until
people can dig into what the failures are.

Change-Id: Id077a68a9cd274e5b68a36c8eb1032632ceaedc5
Related-Bug: #1489581
 		2015-08-31 10:20:52 -04: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 "add waiting for snapshot available status" 2015-08-28 16:12:24 +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 "Return complete response from flavors_client part-1" 2015-08-25 18:08:29 +00:00
test_dashboard_basic_ops.py Fixed few typos 2015-08-25 05:26:03 -07:00
test_encrypted_cinder_volumes.py Add compute_feature_enabled.attach_encrypted_volume config option 2015-06-20 14:24:36 -07:00
test_large_ops.py Return complete resp from security_groups_client 2015-08-24 19:00:41 +09:00
test_minimum_basic.py Add "server" to action methods 2015-08-13 02:05:39 +00:00
test_network_advanced_server_ops.py Add "server" to action methods 2015-08-13 02:05:39 +00:00
test_network_basic_ops.py Skip router rescheduling test 2015-08-28 11:22:39 -04:00
test_network_v6.py Enhance IPv6 scenario - dual network testing 2015-08-12 14:44:02 +02:00
test_security_groups_basic_ops.py Remove some dead code 2015-08-19 16:24:29 +02:00
test_server_advanced_ops.py Add "server" to action methods 2015-08-13 02:05:39 +00:00
test_server_basic_ops.py Merge "Return complete response from floating_ips_client" 2015-08-25 05:57:46 +00:00
test_shelve_instance.py Return complete response from floating_ips_client 2015-08-18 17:03:55 +09:00
test_snapshot_pattern.py Update all Oslo module use 2015-03-11 21:07:56 +00:00
test_stamp_pattern.py Merge "Full response for Volume SnapshotsClient methods" 2015-08-24 05:42:05 +00: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 ceilometermiddleware sample target 2015-06-30 19:06:09 +00:00
test_volume_boot_pattern.py Skip ebs scenario test due to bug 1489581 2015-08-31 10:20:52 -04:00
utils.py Return complete response from compute images_client 2015-08-26 11:29:56 +09: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.