summaryrefslogtreecommitdiffstats
path: root/docs/testing
diff options
context:
space:
mode:
authorKonrad Djimeli <konraddjimeli@gmail.com>2018-04-19 01:52:05 +0100
committerCedric Ollivier <cedric.ollivier@orange.com>2018-04-20 07:56:15 +0000
commit5b441a51bbe048960330f5bc8913b702f39f3ee8 (patch)
tree0d29cf5d558b4d5329c284a43e86d487d8a3ac97 /docs/testing
parentc3665460e44f7b8721d57f51eba35e9207e65cc7 (diff)
Add Kubernetes test details to functest userguide
Change-Id: I032bfe5f079c185d6217800b4a4d16e94c29b05c Signed-off-by: Konrad Djimeli <konraddjimeli@gmail.com> (cherry picked from commit cf04ef760710de425afef62d2584d7fb5a908d33)
Diffstat (limited to 'docs/testing')
-rw-r--r--docs/testing/user/userguide/test_details.rst28
1 files changed, 28 insertions, 0 deletions
diff --git a/docs/testing/user/userguide/test_details.rst b/docs/testing/user/userguide/test_details.rst
index fe7e6a9b6..935298fdd 100644
--- a/docs/testing/user/userguide/test_details.rst
+++ b/docs/testing/user/userguide/test_details.rst
@@ -419,6 +419,33 @@ The vyos-vrouter architecture is described in `[14]`_
juju_epc
^^^^^^^^
+
+Kubernetes (K8s)
+----------------
+
+Kubernetes testing relies on sets of tests, which are part of the Kubernetes
+source tree, such as the Kubernetes End-to-End (e2e) tests `[15]`_.
+
+The kubernetes testcases are distributed across various Tiers:
+
+ * Healthcheck Tier
+
+ * k8s_smoke Test Case: Creates a Guestbook application that contains redis
+ server, 2 instances of redis slave, frontend application, frontend service
+ and redis master service and redis slave service. Using frontend service,
+ the test will write an entry into the guestbook application which will
+ store the entry into the backend redis database. Application flow MUST
+ work as expected and the data written MUST be available to read.
+
+ * Smoke Tier
+
+ * k8s_conformance Test Case: Runs a series of k8s e2e tests expected to
+ pass on any Kubernetes cluster. It is a subset of tests necessary to
+ demonstrate conformance grows with each release. Conformance is thus
+ considered versioned, with backwards compatibility guarantees and are
+ designed to be run with no cloud provider configured.
+
+
.. _`[2]`: http://docs.openstack.org/developer/tempest/overview.html
.. _`[3]`: https://rally.readthedocs.org/en/latest/index.html
.. _`[5]`: https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater/blob/master/openstack-blueprint.yaml
@@ -429,3 +456,4 @@ juju_epc
.. _`[12]`: http://docs.opnfv.org/en/latest/submodules/functest/docs/testing/user/userguide/index.html
.. _`[13]`: https://wiki.opnfv.org/display/PROJ/SNAPS-OO
.. _`[14]`: https://github.com/oolorg/opnfv-functest-vrouter
+.. _`[15]`: https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-tests.md