8ec2c709a2
Since both tests change the same configmap and restart the controller, we'll reduce the flakiness if serial execution among these two tests is enforced. Change-Id: Icfa7b13398e2fd64180b72b07ca68e532fa1e544 Signed-off-by: Antoni Segura Puimedon <celebdor@gmail.com> |
||
---|---|---|
.. | ||
README.rst | ||
__init__.py | ||
base.py | ||
consts.py | ||
test_cross_ping.py | ||
test_daemon.py | ||
test_ha.py | ||
test_kuryr_restart.py | ||
test_namespace.py | ||
test_network_policy.py | ||
test_npwg_multi_vif.py | ||
test_ocp_route.py | ||
test_port_pool.py | ||
test_service.py |
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.