History

Zuul 2ddd1dd65d Merge "Reduce flakiness of pod creation timeout"		2019-12-04 12:22:46 +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	Add a check for ClusterIP IP of LB service	2019-11-27 16:27:27 +02:00
consts.py	Make the label of kuryr-controller customizable	2019-09-26 08:54:42 +00:00
test_cross_ping.py	Testing VM to loadBalancer service connectivity	2018-08-12 10:06:13 +03:00
test_cross_ping_multi_worker.py	Multi worker tests	2018-12-13 09:03:49 +02:00
test_daemon.py	Do not rely on ps to check the daemon	2018-09-17 18:41:56 +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 "Reduce flakiness of pod creation timeout"	2019-12-04 12:22:46 +00:00
test_network_policy.py	Increading a timeout to 120 seconds on CRD creation	2019-11-25 13:06:23 +02: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	Merge "Adjust expected number of ports to config values"	2019-10-25 19:11:03 +00:00
test_service.py	Add a check for ClusterIP IP of LB service	2019-11-27 16:27:27 +02: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.