Files

ghanshyam 6b0b8b718e Deprecate glance APIs version config options

Glance v1 APIs are deprecated and v2 are current.
Tempest should tests only v2 APIs and by default v1
APIs are being disabled - I7f962a07317cdad917ee896d79e49ee18938d074

This commit deprecate the API version selection config options
so that we can switch to v2 only testing soon.

Change-Id: I6c4b92f0f2da2797efbb27e16061e6e325dda504

2017-03-08 04:36:34 +00:00

api

Merge "Add call_and_ignore_notfound_exc to Keystone base"

2017-03-08 01:49:08 +00:00

cmd

Add --combine option to tempest run

2017-03-03 14:16:56 -05:00

common

Add network_mask_bits argument to assign_static_ip()

2017-03-07 17:38:32 +00:00

hacking

Delete Savanna element in client list

2016-09-21 03:00:15 +00:00

lib

Merge "Deprecate the skip_unless_attr decorator."

2017-03-07 23:02:24 +00:00

scenario

Add network_mask_bits argument to assign_static_ip()

2017-03-07 17:38:32 +00:00

services

Swift list containers should test for reverse listing param

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

test_discover

Use oslo.log library instead of system logging module

2017-01-16 05:56:54 +00:00

tests

Merge "Remove get_ram_size_in_mb, get_number_of_vcpus, etc"

2017-03-07 17:36:21 +00:00

__init__.py

…

clients.py

Remove default_params_with_timeout_values variable

2017-01-27 02:42:47 +00:00

config.py

Deprecate glance APIs version config options

2017-03-08 04:36:34 +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.