openstack
/
tempest
Code Issues Proposed changes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0ea2c01d75'
${ noResults }
tempest/tempest/scenario
History
Zuul 4968958158
Merge "Improve ipv6 configuration" 		4 years ago
..
README.rst Fix docs markup consistency 5 years ago
__init__.py add scenario directory 10 years ago
manager.py Merge "Adds protocol options for test_cross_tenant_traffic" 4 years ago
test_aggregates_basic_ops.py Replace list_hypervisors with list_services 5 years ago
test_encrypted_cinder_volumes.py docs: Fix incorrect docstrings in reStructuredText format 4 years ago
test_minimum_basic.py Add autopep8 to tox.ini 4 years ago
test_network_advanced_server_ops.py Mark test_server_connectivity_reboot as slow 4 years ago
test_network_basic_ops.py Make test_hotplug_nic test first check the IP 4 years ago
test_network_v6.py Improve ipv6 configuration 4 years ago
test_object_storage_basic_ops.py docs: Fix incorrect docstrings in reStructuredText format 4 years ago
test_security_groups_basic_ops.py Merge "Adds protocol options for test_cross_tenant_traffic" 4 years ago
test_server_advanced_ops.py Trivial docstring cleanup in TestServerAdvancedOps 5 years ago
test_server_basic_ops.py Update json module to jsonutils 4 years ago
test_server_multinode.py Move test decorators to common 6 years ago
test_shelve_instance.py Log server console output during create/get timestamp 5 years ago
test_snapshot_pattern.py Log server console output during create/get timestamp 5 years ago
test_stamp_pattern.py Log server console output during create/get timestamp 5 years ago
test_volume_backup_restore.py Add status check for creating volume backup 5 years ago
test_volume_boot_pattern.py Merge "Add autopep8 to tox.ini" 4 years ago
test_volume_migrate_attached.py Introduce an attached volume migration test 4 years ago

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.