History

Antoni Segura Puimedon 5b6df793c1 Do not rely on ps to check the daemon Our container images do not install 'ps'. It is something that, if present, comes from the base image. Since base images come and go, it is much better to rely on 'cat' which is always there. Depends-on: Ic57fbe20b7bf396ea92e0c2cbcca42814ae2a119 Change-Id: I794290c61e7ce7bc61dd8d52d6a6b57ffeebdf23 Signed-off-by: Antoni Segura Puimedon <celebdor@gmail.com>		2018-09-17 18:41:56 +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	Do not rely on ps to check the daemon	2018-09-17 18:41:56 +02:00
consts.py	Use expected pod output as a constant	2018-08-08 13:17:47 +00: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_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	Using pod ready condition for pod readiness check	2018-09-03 15:12:09 +03: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.