tempest/tempest/scenario
Matthew Treinish a74f5d4fba Mildly wound the interlopers
This commit removes all the references to nose in the tempest tree.
Moving forward trying to support nose which doesn't support some of the
features we rely on in tempest is increasingly difficult. Please refer
to this thread:

http://lists.openstack.org/pipermail/openstack-dev/2014-January/024673.html

for a more detailed explanation and the discussion regarding this.

Change-Id: I3dee566d33efe1fb7808817b885d1680736abe6a
2014-02-19 16:17:32 +00:00
..
orchestration Convert scenario tests to use global CONF object 2014-01-30 18:43:09 -05:00
__init__.py add scenario directory 2013-05-17 08:52:22 -04:00
manager.py Rename images variable in TempestConfigPrivate 2014-02-10 06:46:38 -08:00
README.rst Adapt scenario readme with real-life aspect 2013-11-08 08:45:48 +01:00
test_aggregates_basic_ops.py Forbid availability_zone None in aggregate Nova API 2014-01-30 16:25:08 +00:00
test_cross_tenant_connectivity.py Convert scenario tests to use global CONF object 2014-01-30 18:43:09 -05:00
test_dashboard_basic_ops.py Convert scenario tests to use global CONF object 2014-01-30 18:43:09 -05:00
test_large_ops.py Convert scenario tests to use global CONF object 2014-01-30 18:43:09 -05:00
test_load_balancer_basic.py Fix syntax in test_load_balancer_basics._check_load_balancing 2014-02-08 12:07:17 -08:00
test_minimum_basic.py Let the soft reboot really happen in the minimum scenario 2014-02-08 19:00:09 +01:00
test_network_basic_ops.py make testing neutron api extensions optional 2014-02-05 15:02:43 +09:00
test_server_advanced_ops.py Convert scenario tests to use global CONF object 2014-01-30 18:43:09 -05:00
test_server_basic_ops.py Mildly wound the interlopers 2014-02-19 16:17:32 +00:00
test_snapshot_pattern.py Convert scenario tests to use global CONF object 2014-01-30 18:43:09 -05:00
test_stamp_pattern.py Fixed misspellings in Tempest 2014-02-07 00:04:15 -08:00
test_swift_basic_ops.py Fix services decorator to use object_storage 2014-02-02 13:37:44 -05:00
test_volume_boot_pattern.py Merge "Revert "skip test_volume_boot_pattern"" 2014-02-04 15:04:35 +00:00

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 use the official python client libraries for OpenStack, as they provide a more realistic approach in how people will interact with the services.

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.