History

Zuul 871fe9ece6 Merge "Fix test_port_pool when namespace is created"		2022-01-17 14:09:43 +00:00
..
README.rst	Add scenario test manager	2017-10-27 09:28:58 +00:00
__init__.py	Add scenario test manager	2017-10-27 09:28:58 +00:00
base.py	Merge "Add wait until active LB in NP test"	2022-01-14 02:26:36 +00:00
base_network_policy.py	Fix Namespace handling	2021-10-14 13:25:50 +00:00
consts.py	Tune curl repetitions value	2022-01-07 12:50:52 +00:00
test_cross_ping.py	Basic IPv6 support	2020-02-14 18:07:26 +01:00
test_cross_ping_multi_worker.py	Multi worker tests	2018-12-13 09:03:49 +02:00
test_daemon.py	Update docs building, py27 cleanup	2020-05-03 11:32:38 +02:00
test_ha.py	Check connectivity to an existing pod in test_ha	2019-08-07 15:23:12 +03:00
test_kuryr_restart.py	Use assertTrue in checking pod connectivity	2019-01-08 13:51:45 +02:00
test_namespace.py	Merge "Fix Namespace handling"	2021-11-05 08:41:32 +00:00
test_network_policy.py	Add wait until active LB in NP test	2022-01-11 12:36:58 +00:00
test_npwg_multi_vif.py	NPWG multi-vif driver tempest tests	2018-08-17 20:20:24 +08:00
test_ocp_route.py	OCP-Router - add support for OCP routes	2018-09-06 07:48:04 +03:00
test_port_pool.py	Fix test_port_pool when namespace is created	2021-12-27 09:50:31 +02:00
test_service.py	Ensure lb is active before checking connectivity	2022-01-07 12:36:44 +00:00

README.rst

What are these tests?

As stated in the tempest developer guide, scenario tests are meant to be used to test the interaction between several OpenStack services to perform a real-life use case.

In the case of the Kuryr Tempest Plugin it also involves interaction with Kubernetes pods, so its manager class includes handlers to its python bindings.

A developer using this manager would be able to perform, among others, CRUD operations with pods, alongside Kuryr-K8s added funcionality.