Files

T

Ken'ichi Ohmichi f66799e915 Remove oslo.i18n entry from config-generator

oslo.i18n is not used in Tempest at all and it has been removed
from requirements.txt since Iff37af95269c38e4d435a53a21e5d60e2c5a3fa8
It is not necessary to keep it in config-generator, and this patch
removes it.

Related-Bug: #1620861
Change-Id: Icf43d6421f3a30ca72fdc4e985e070ebeb736fbb

2017-04-07 12:08:54 -07:00

api

Merge "Skip arbitrary container tests for Ceph"

2017-04-07 16:22:58 +00:00

cmd

Remove oslo.i18n entry from config-generator

2017-04-07 12:08:54 -07:00

common

Rename server arg in wait_for_interface_status method

2017-04-03 11:37:28 -04:00

hacking

Cleanup ignored_list for T110 and T111

2017-03-13 15:27:32 -07:00

lib

Merge "Add Nova version log"

2017-04-07 12:25:25 +00:00

scenario

Remove 'allow_port_security_disabled' option

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

services

Swift list containers should test for reverse listing param

2017-02-08 10:42:19 -08:00

test_discover

Use Sphinx 1.5 warning-is-error

2017-03-23 11:51:45 +00:00

tests

Merge "Fix no module unit test for Python3.6"

2017-04-05 19:48:30 +00:00

__init__.py

…

clients.py

Separate volume v2 transfers service clients

2017-04-06 01:20:59 +00:00

config.py

Merge "Remove 'allow_port_security_disabled' option"

2017-04-07 08:14:13 +00:00

exceptions.py

Add a generic "wait_for_volume_resource_status" function

2017-02-19 09:12:42 +02:00

manager.py

Merge "Revert "Move dscv and ca_certs to config section service_clients""

2016-08-20 22:48:10 +00:00

README.rst

Remove the Stress framework

2016-10-19 14:31:13 +02:00

test.py

Improve error info in assertEmpty and assertNotEmpty

2017-03-03 15:20:10 +08:00

version.py

Add reno to tempest

2016-02-24 11:31:32 -05:00

README.rst

Tempest Field Guide Overview

Tempest is designed to be useful for a large number of different environments. This includes being useful for gating commits to OpenStack core projects, being used to validate OpenStack cloud implementations for both correctness, as well as a burn in tool for OpenStack clouds.

As such Tempest tests come in many flavors, each with their own rules and guidelines. Below is the proposed Havana restructuring for Tempest to make this clear.

tempest/
api/ - API tests
scenario/ - complex scenario tests

Each of these directories contains different types of tests. What belongs in each directory, the rules and examples for good tests, are documented in a README.rst file in the directory.

`api_field_guide`

API tests are validation tests for the OpenStack API. They should not use the existing python clients for OpenStack, but should instead use the tempest implementations of clients. Having raw clients let us pass invalid JSON to the APIs and see the results, something we could not get with the native clients.

When it makes sense, API testing should be moved closer to the projects themselves, possibly as functional tests in their unit test frameworks.

`scenario_field_guide`

Scenario tests are complex "through path" tests for OpenStack functionality. They are typically a series of steps where complicated state requiring multiple services is set up exercised, and torn down.

Scenario tests should not use the existing python clients for OpenStack, but should instead use the tempest implementations of clients.

`unit_tests_field_guide`

Unit tests are the self checks for Tempest. They provide functional verification and regression checking for the internal components of tempest. They should be used to just verify that the individual pieces of tempest are working as expected.