openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
ghanshyam eed4031a9e Fix create container method 
Swift accept lot many headers in create container API but service
client method only accept the metadata headers.
This commit makes the PUT method to accept headers as kwargs.
Also this commit renames the PUT method to update_container because
that is PUT operation. In addition, this adds create_container as
the alias for the usability.

Details- https://developer.openstack.org/api-ref/object-store/#create-container

Partially implements blueprint consistent-service-method-names

Change-Id: I2a722bf181853ca903d05d4518b4c98764fadc12
 		2017-10-05 17:34:36 +00:00
..
README.rst Doc: fix markups, capitalization and add 2 REVIEWING advices 2017-07-11 20:26:32 +02:00
__init__.py add scenario directory 2013-05-17 08:52:22 -04:00
manager.py Fix create container method 2017-10-05 17:34:36 +00: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 Move test decorators to common 2017-08-23 17:09:33 +00:00
test_network_advanced_server_ops.py Move test decorators to common 2017-08-23 17:09:33 +00:00
test_network_basic_ops.py Move internal helpers to the class that uses them 2017-09-22 14:25:29 +08:00
test_network_v6.py Move test decorators to common 2017-08-23 17:09:33 +00:00
test_object_storage_basic_ops.py Move test decorators to common 2017-08-23 17:09:33 +00: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 test decorators to common 2017-08-23 17:09:33 +00:00
test_server_basic_ops.py Move test decorators to common 2017-08-23 17:09:33 +00: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 Move test decorators to common 2017-08-23 17:09:33 +00:00
test_volume_migrate_attached.py Merge "Move test decorators to common" 2017-08-24 06:48:00 +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.