Files

T

Ken'ichi Ohmichi ad1b862e8b Remove 'allow_port_security_disabled' option

The allow_port_security_disabled option had been added as a temporary
option for skipping the test on Liberty. Current Tempest doesn't support
Liberty, so this patch removes the config option from Tempest.

Change-Id: Ia7d7f3f545e7582be3c3f005576adceede5e97cb

2017-04-06 20:23:26 +00:00

__init__.py

add scenario directory

2013-05-17 08:52:22 -04:00

manager.py

Merge "Remove remaining usage of cinder v1 API call from Tempest"

2017-03-29 06:51:00 +00:00

README.rst

Fix doc for usage of python clients in scenario tests

2014-11-26 17:04:37 +09:00

test_aggregates_basic_ops.py

Use tempest.lib data_utils - scenario

2017-03-10 10:04:48 -08:00

test_encrypted_cinder_volumes.py

make -e full run tempest scenarios serially

2017-03-03 20:50:46 +00:00

test_minimum_basic.py

Remove unused variable

2017-03-01 10:09:55 +00:00

test_network_advanced_server_ops.py

make -e full run tempest scenarios serially

2017-03-03 20:50:46 +00:00

test_network_basic_ops.py

Remove set_mac_address from old remote_client

2017-03-28 20:50:27 +00:00

test_network_v6.py

Remove set_nic_state from old remote_client

2017-03-17 15:00:05 -07:00

test_object_storage_basic_ops.py

make -e full run tempest scenarios serially

2017-03-03 20:50:46 +00:00

test_security_groups_basic_ops.py

Remove 'allow_port_security_disabled' option

2017-04-06 20:23:26 +00:00

test_server_advanced_ops.py

Merge "Do not use skip_checks in TestServerAdvancedOps"

2017-03-28 04:13:22 +00:00

test_server_basic_ops.py

Remove redundant parameters for server creation

2017-02-14 09:08:52 +02:00

test_server_multinode.py

Merge "Check whether server is located on the requested host"

2017-02-14 23:31:52 +00:00

test_shelve_instance.py

make -e full run tempest scenarios serially

2017-03-03 20:50:46 +00:00

test_snapshot_pattern.py

make -e full run tempest scenarios serially

2017-03-03 20:50:46 +00:00

test_stamp_pattern.py

Remove name checking for api version 1

2017-03-27 14:54:40 +03:00

test_volume_boot_pattern.py

Remove name checking for api version 1

2017-03-27 14:54:40 +03:00

test_volume_migrate_attached.py

Remove remaining usage of cinder v1 API call from Tempest

2017-03-28 10:00:52 +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":

upload a glance image

deploy a vm from it

ssh to the guest

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.