openstack
/
kuryr-tempest-plugin
Code Issues Proposed changes
kuryr-tempest-plugin/kuryr_tempest_plugin/tests/scenario
History
Antoni Segura Puimedon b7391ab1e3 Revert "Skip service test" 
This reverts commit 2555caf480.

Depends-On: I895d3e5af71ccc7219be422b9ca9e9f8833bad8f
Change-Id: I119d5bb2244fcbb89c709b8bd1fb73323d2cddca
 		2018-04-19 17:46:53 +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 Testing service creation and connectivity 2018-03-29 11:31:54 +03:00
test_cross_ping.py Check connectivity from Pod to VM 2018-03-01 15:51:54 +02:00
test_port_pool.py Testing port pool feature 2018-02-15 16:10:13 +02:00
test_service.py Revert "Skip service test" 2018-04-19 17:46:53 +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.