openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
Steve Baker 22c1660072 Make test_server_cfn_init a scenario test 
Converting test_server_cfn_init to a scenario test is long overdue
since it is more of a scenario than an exercising of the heat API.

The heat-slow job has gone non-voting because this test fails
~%50 of the time due to bug #1297560. The server boot log is now
logged regardless of success or failure to build up data to diagnose
the issue.

This also adds several convenience functions to the test base class.

Co-Authored-By: Steven Hardy <shardy@redhat.com>
Related-Bug: #1297560
Change-Id: I077aeaf2bf8b292699eb20c5a75c59df35645913
 		2014-05-23 15:48:53 +01:00
..
orchestration Make test_server_cfn_init a scenario test 2014-05-23 15:48:53 +01:00
README.rst Adapt scenario readme with real-life aspect 2013-11-08 08:45:48 +01:00
__init__.py add scenario directory 2013-05-17 08:52:22 -04:00
manager.py Make test_server_cfn_init a scenario test 2014-05-23 15:48:53 +01:00
test_aggregates_basic_ops.py Prepare for enabling H302 rule (scenario) 2014-02-25 09:45:21 +09:00
test_baremetal_basic_ops.py Adds Ironic test_baremetal_basic_ops scenario test 2014-03-31 14:45:29 -07:00
test_dashboard_basic_ops.py Prepare for enabling H302 rule (scenario) 2014-02-25 09:45:21 +09:00
test_large_ops.py Split large-ops into three tests so each has its own timeout 2014-05-09 15:25:18 -07:00
test_load_balancer_basic.py Merge "Use fixed ips for lbaas pool members" 2014-05-19 12:14:09 +00:00
test_minimum_basic.py Extend network debug infos on network failures 2014-02-26 21:58:57 +01:00
test_network_advanced_server_ops.py Enable H302 rule everywhere 2014-05-18 21:14:36 -04:00
test_network_basic_ops.py Merge "Extend network debug infos on network failures" 2014-03-13 15:15:10 +00:00
test_security_groups_basic_ops.py Access credential fields as attributes 2014-05-06 14:39:04 +01:00
test_server_advanced_ops.py Honor suspend/pause config switches in scenario tests 2014-04-01 08:02:07 -07:00
test_server_basic_ops.py Merge "Add load_test mechanism for InputScenarioUtils" 2014-04-15 19:40:19 +00:00
test_snapshot_pattern.py Fix RemoteClient usage in scenario tests 2014-03-06 14:56:07 +04:00
test_stamp_pattern.py Skip volume snapshot tests if feature is not enabled 2014-03-25 17:46:06 +01:00
test_swift_basic_ops.py Prepare for enabling H302 rule (scenario) 2014-02-25 09:45:21 +09:00
test_volume_boot_pattern.py Skip volume snapshot tests if feature is not enabled 2014-03-25 17:46:06 +01:00
utils.py Enforces the use of Credentials (part2) 2014-05-06 14:38:55 +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 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.