openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
Sean Dague 17487fb9e8 skip test_connectivity_between_vms_on_different_networks 
This test doesn't work on OVH if we make it so that created guests
actually have the ability to talk to external networks. We're not
really sure why, but having guests be able to talk to external
networks is quite important from a devstack neutron default
perspective.

This is temporary so that we can move forward with the devstack switch
over to neutron, and we can figure out what needs to be addressed to
fix the bug in question.

Depends-On: Ia75068dcf36dff548170c0fa5482ca825f5a9758
(requirements fix)

Change-Id: Ia07cd8d8d88d445420f881df6aca4a77cf9468fb
Related-Bug: #1610994
 		2016-08-08 16:54:00 +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 "Add a TODO to remove Ironic related workaround" 2016-08-03 04:56:11 +00:00
test_aggregates_basic_ops.py Removes explicit looping over dict .keys() method 2016-07-11 16:45:22 +02:00
test_baremetal_basic_ops.py Remove some dead code 2016-02-16 14:01:57 +00:00
test_encrypted_cinder_volumes.py Migrate scenario tests ssh-auth-strategy 2015-12-01 16:02:01 +00:00
test_minimum_basic.py Scenarios: remove trivial wrapper methods 2016-01-26 17:10:55 +01:00
test_network_advanced_server_ops.py Merge "Remove neutron OO wrappers" 2016-06-15 18:43:59 +00:00
test_network_basic_ops.py skip test_connectivity_between_vms_on_different_networks 2016-08-08 16:54:00 +00:00
test_network_v6.py Skip unstable v6 scenario tests 2016-07-21 18:07:57 -07:00
test_object_storage_basic_ops.py Trival: Remove unused logging import in some files 2016-01-06 16:22:53 +08:00
test_security_groups_basic_ops.py Remove neutron OO wrappers 2016-06-14 21:10:03 -05: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 Remove unused LOG to keep code clean 2016-07-18 01:52:54 +00:00
test_server_multinode.py Merge "Trival: Remove unused logging import in some files" 2016-01-13 11:16:00 +00:00
test_shelve_instance.py Use skip_checks instead of skipUnless in TestShelveInstance 2016-07-13 13:48:12 +08:00
test_snapshot_pattern.py Use skip_checks in test_snapshot_pattern 2016-07-25 11:19:36 +08:00
test_stamp_pattern.py Use common "waiters.wait_for_snapshot_status" function everywhere 2016-03-25 16:39:35 +00:00
test_volume_boot_pattern.py Use common "waiters.wait_for_snapshot_status" function everywhere 2016-03-25 16:39:35 +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":
    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.