openstack/tempest
Code Issues Proposed changes
b0d15bfefb
tempest/tempest
History
Ghanshyam Mann b0d15bfefb Revert "cinder backup force-delete when backup is error" 
force-delete feature is backend specific and not implemented by ceph.
It return 405 in case of ceph.
http://logs.openstack.org/01/458201/2/check/gate-tempest-dsvm-full-ceph-plugin-src-glance_store-ubuntu-xenial/d058f29/logs/testr_results.html.gz

Currently it block the glance_store gate where ceph job is voting.
Let's revert this for now and discuss such backend specific feature
should be tested on Tempest side or not.

This reverts commit 31169e21d6.

Related-Bug: #1687538
Change-Id: I81c0911812945f8ada7c09fe98690aabacb0eda1
2017-05-02 05:05:38 +00:00
..
api Revert "cinder backup force-delete when backup is error" 2017-05-02 05:05:38 +00:00
cmd Add --combine option to tempest run 2017-03-03 14:16:56 -05:00
common Add note on get_disks about unsupported guests 2017-03-24 16:43:04 -04:00
hacking Cleanup ignored_list for T110 and T111 2017-03-13 15:27:32 -07:00
lib Revert "cinder backup force-delete when backup is error" 2017-05-02 05:05:38 +00:00
scenario Merge "Do not use skip_checks in TestServerAdvancedOps" 2017-03-28 04:13:22 +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 "Adding server evacuate client" 2017-03-27 19:43:41 +00:00
__init__.py
clients.py Add "list Cinder API versions" 2017-03-22 10:14:59 -07:00
config.py Merge "Deprecate the dvr_extra_resources config switch." 2017-03-28 01:18:31 +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.