History

Gena Cher 28a141f0cd Update port pool with non-default values Change the test to work with the namespaces, so it can run non sequentually Update port pool on newly created namespace with non-default values Create new pods in that namespace Check that port pool is working as before Perform connectivity test between pods Depends-On: Ic0dac5075418ec71e3beca48fdd811c5df1ff467 Change-Id: I13cca6f77c66e88788365cc7bf94ddcfa787c167		2018-11-15 12:42:23 +02: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	Update port pool with non-default values	2018-11-15 12:42:23 +02:00
consts.py	A/P HA tests	2018-10-16 19:25:38 +02:00
test_cross_ping.py	Testing VM to loadBalancer service connectivity	2018-08-12 10:06:13 +03:00
test_daemon.py	Do not rely on ps to check the daemon	2018-09-17 18:41:56 +02:00
test_ha.py	A/P HA tests	2018-10-16 19:25:38 +02:00
test_kuryr_restart.py	Use class-level skips when necessary	2018-07-17 14:29:55 +02:00
test_namespace.py	Remove direct calls to os_client for SGs	2018-09-11 05:44:45 -04:00
test_network_policy.py	Add Network Policy tests	2018-09-10 06:37:51 -04: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	Update port pool with non-default values	2018-11-15 12:42:23 +02:00
test_service.py	Use ThreadPool and requests instead of subprocess	2018-08-19 13:01:27 +03: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.