History

Ghanshyam Mann f5aef7bec1 Create default network for server advance scenario tests Previously when fixing this bug for API tests, we thought it cannot happen in scenario tests with same reason as scenario base class do fetch the specific network from neutron to pass it t nova for creating the server. But when 'CONF.network.port_vnic_type' and 'CONF.network.port_profile' are not configured in Tempest then Tempest scenario manager does not fetch the network from neutron. - `fec2c93cdc/tempest/scenario/manager.py (L242)` In that case, tenant network is used, which is not present as scenario manager does not create the default network resource for credential and tenant. - `fec2c93cdc/tempest/scenario/manager.py (L298)` This commit let server advance test (which is failing for multiple network erorr) to create the default network which will be used to pass to the nova API request while creating the test server. Related-Bug: #1844568 Change-Id: I5a73a4f25f9092a4cdddcaf86f9ff2c89720409e		2021-02-08 16:58:07 -06:00
..
api	Merge "Add client methods and tests for system grants"	2021-01-22 04:44:35 +00:00
cmd	Merge "Remove six.PY3/six.PY2"	2020-11-27 01:52:40 +00:00
common	Merge "Move horizon test from tempest-horizon to tempest"	2021-01-22 17:08:10 +00:00
hacking	Update hacking for Python3	2020-04-04 10:33:23 +02:00
lib	Merge "Add default RBAC personas to pre-provisioned creds"	2021-01-26 16:17:01 +00:00
scenario	Create default network for server advance scenario tests	2021-02-08 16:58:07 -06:00
services	Move the object client to tempest.lib	2017-10-17 00:14:20 +00:00
test_discover	Use os.path.join as possible	2020-09-06 09:49:40 +00:00
tests	Merge "Add client methods and tests for system grants"	2021-01-22 04:44:35 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Add placement API methods for testing routed provider nets	2020-09-28 06:45:37 +00:00
config.py	Merge "Move horizon test from tempest-horizon to tempest"	2021-01-22 17:08:10 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
manager.py	Need to have stable tempest scenario manager	2020-09-03 15:49:53 +05:30
test.py	Add workaround to handle the testtool skip exception in CLI test	2019-10-12 01:40:29 +00: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 overview of the Tempest repository structure to make this clear.

tempest/
   api/ - API tests
   scenario/ - complex scenario tests
   tests/ - unit tests for Tempest internals

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.