openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
Jenkins 1bca50c070 Merge "Reworked scenario tests to use their own non-default security groups" 2014-06-17 21:29:53 +00: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 Merge "Reworked scenario tests to use their own non-default security groups" 2014-06-17 21:29:53 +00:00
test_aggregates_basic_ops.py test_aggregates_basic_ops picks a non compute node 2014-05-30 00:42:44 +02:00
test_baremetal_basic_ops.py Remove the validate_driver_info test 2014-06-13 15:48:11 +01: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 Switch back to nc in test_load_balancer_basic 2014-05-19 19:03:44 +04:00
test_minimum_basic.py Reworked scenario tests to use their own non-default security groups 2014-06-04 00:09:27 +04:00
test_network_advanced_server_ops.py Consolidate _check_tenant_network_connectivity in NetworkScenarioTest 2014-06-09 13:53:48 -07:00
test_network_basic_ops.py Disable isolated_creds.net_resources on network scenarios 2014-06-16 06:50:15 +00:00
test_security_groups_basic_ops.py Disable isolated_creds.net_resources on network scenarios 2014-06-16 06:50:15 +00: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 Reworked scenario tests to use their own non-default security groups 2014-06-04 00:09:27 +04:00
test_snapshot_pattern.py Reworked scenario tests to use their own non-default security groups 2014-06-04 00:09:27 +04:00
test_stamp_pattern.py Reworked scenario tests to use their own non-default security groups 2014-06-04 00:09:27 +04: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 Reworked scenario tests to use their own non-default security groups 2014-06-04 00:09:27 +04: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.