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.
Zuul d8904d0aee
Merge "Pass custom args to create_port through create_server"
2 years ago
README.rst Fix docs markup consistency 5 years ago add scenario directory 10 years ago Merge "Pass custom args to create_port through create_server" 2 years ago Skip adding host to aggregate with az if host already in other zone 2 years ago Use of single interface for creating image 3 years ago Remove slow tag from test_minbw test 2 years ago Use of single interface for creating image 3 years ago Set image_alt_ssh_user during stack 2 years ago Merge "Remove any reference to "tenant_id" in network" 3 years ago Need to have stable tempest scenario manager 3 years ago docs: Fix incorrect docstrings in reStructuredText format 4 years ago Remove any reference to "tenant_id" in network 3 years ago Trivial docstring cleanup in TestServerAdvancedOps 5 years ago Update json module to jsonutils 4 years ago Move test decorators to common 6 years ago Add related test to Bug #1732428 2 years ago Add image "version" metadata in test_snapshot_pattern 3 years ago Remove unused LOG var in 2 years ago Add status check for creating volume backup 5 years ago Use new encryption provider constants (reprise) 3 years ago Introduce an attached volume migration test 4 years ago


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.