History

Mohammed Naser b6c6d2a128 Refactor config drive mounting

There are a few places where we mount the config drive which
is not done in a consistent manner which results in failures
for the cases where the config drive is VFAT, which makes the
device label report as CONFIG-2 and not config-2 (uppercase).

This refactors the mounting and unmounting codebase to the
same block and reuses it to ensure a consistent behaviour across
tests, also letting the tags checks pass when using VFAT for
config drives.

Change-Id: I529cff87c848bc87d63d2ec407ed18cdd631ecef

2018-02-19 10:16:13 -05:00

__init__.py

add scenario directory

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

manager.py

[TrivialFix] Remove unused statement in scenario/manager.py

2018-02-11 09:28:52 +08:00

README.rst

Fix docs markup consistency

2017-11-21 19:02:54 +09:00

test_aggregates_basic_ops.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_encrypted_cinder_volumes.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_minimum_basic.py

Refresh server data after fip is assigned

2018-02-06 11:17:06 +00:00

test_network_advanced_server_ops.py

Add flavor check after resize server

2018-01-16 16:00:36 +08:00

test_network_basic_ops.py

Merge "test_mtu_sized_frames: sanity check connectivity first"

2017-11-23 16:58:45 +00:00

test_network_v6.py

test_network_v6: log console when test fails

2017-11-16 21:39:48 +00:00

test_object_storage_basic_ops.py

Fix senario test: test_swift_acl_anonymous_download

2017-10-09 16:58:10 +08:00

test_security_groups_basic_ops.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_server_advanced_ops.py

Move and update test_resize_volume_backed_server_confirm

2017-11-13 23:03:31 +00:00

test_server_basic_ops.py

Refactor config drive mounting

2018-02-19 10:16:13 -05:00

test_server_multinode.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_shelve_instance.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_snapshot_pattern.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_stamp_pattern.py

Move test decorators to common

2017-08-23 17:09:33 +00:00

test_volume_boot_pattern.py

Add some verify in test_create_ebs_image_and_check_boot

2017-11-21 12:34:26 +08:00

test_volume_migrate_attached.py

Merge "Add NOTE related to 'on-demand' migration"

2018-01-17 05:30:19 +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 Tempest's 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.