History

Zuul 0dead2620e Merge "Working with noop for vif_pool_driver"		2019-01-26 20:39:09 +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 "Working with noop for vif_pool_driver"	2019-01-26 20:39:09 +00:00
consts.py	Multi worker tests	2018-12-13 09:03:49 +02: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	A/P HA tests	2018-10-16 19:25:38 +02:00
test_kuryr_restart.py	Use assertTrue in checking pod connectivity	2019-01-08 13:51:45 +02:00
test_namespace.py	Checking connectivity from host to pod/service in the namespace	2019-01-02 11:41:38 +02: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	Working with noop for vif_pool_driver	2019-01-08 11:58:51 +02:00
test_service.py	Add connectivity test for service UDP	2018-11-15 12:32:40 +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.