History

Slawek Kaplonski 126fe656a9 Wait couple of seconds for dns servers to be set in the guest In test tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_subnet_details there is renewal of the DHCP lease made to configure dns nameservers. And sometimes this test is failing due to missing nameservers in the /etc/resolv.conf file in the guest VM. After analyzing logs from such failed jobs I think that the reason of that may be race between getting dns nameservers from guest VM by test and actually configuring it inside the guest vm. So this patch proposes to add wait (5 seconds by default) for non empty list of the dns nameservers returned from the guest VM. That should avoid such failures of that test. Closes-bug: #1914229 Change-Id: I093ae5c11f88cc29e91285ff674788de53645b4e		2021-07-23 13:22:16 +02:00
..
api	Add volume_size_extend opt for volume tests	2021-06-29 07:01:17 +00:00
cmd	Merge "Update subunit_describe_calls about new ports"	2021-03-04 21:27:11 +00:00
common	Wait couple of seconds for dns servers to be set in the guest	2021-07-23 13:22:16 +02:00
hacking	Fix hacking check for service client	2021-04-30 10:32:13 -05:00
lib	Skip network creation for system and domain scoped token	2021-06-25 14:14:40 -05:00
scenario	Fix unstability in test_subnet_details	2021-03-29 08:31:15 +00:00
services	Remove usage of six	2021-02-18 10:43:57 +08:00
test_discover	Remove usage of six	2021-02-23 00:38:55 +00:00
tests	Remove skip for test_fix_argument_yes unit test	2021-06-24 07:03:08 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Add tests for "new" Transfers API (mv 3.55)	2021-05-20 22:28:26 -04:00
config.py	Add volume_size_extend opt for volume tests	2021-06-29 07:01:17 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
test.py	Remove usage of six	2021-04-15 09:25:19 +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.