Merge "Updated documentation for juju_epc tests"

[functest.git] / docs / testing / user / userguide / test_overview.rst

diff --git a/docs/testing/user/userguide/test_overview.rst b/docs/testing/user/userguide/test_overview.rst
index 91eb343..b88a99c 100644 (file)
--- a/docs/testing/user/userguide/test_overview.rst
+++ b/docs/testing/user/userguide/test_overview.rst
@@ -8,11 +8,12 @@ In the Continuous Integration pipeline, it is launched after an OPNFV fresh
 installation to validate and verify the basic functions of the
 infrastructure.
 
-The current list of test suites can be distributed over 4 main domains:
+The current list of test suites can be distributed over 5 main domains:
   * VIM (Virtualised Infrastructure Manager)
   * Controllers (i.e. SDN Controllers)
   * Features
   * VNF (Virtual Network Functions)
+  * Kubernetes
 
 Functest test suites are also distributed in the OPNFV testing categories:
 healthcheck, smoke, features, components, performance, VNF, Stress tests.
@@ -96,13 +97,6 @@ validate the scenario for the release.
 |             |               |            | operations mainly based on       |
 |             |               |            | upstream testcases. See below    |
 |             |               |            | for details                      |
-|             |               +------------+----------------------------------+
-|             |               | odl        | Test Suite for the OpenDaylight  |
-|             |               | \_netvirt  | SDN Controller when the NetVirt  |
-|             |               |            | features are installed. It       |
-|             |               |            | integrates some test suites from |
-|             |               |            | upstream using Robot as the test |
-|             |               |            | framework                        |
 +-------------+---------------+------------+----------------------------------+
 | Features    | features      | bgpvpn     | Implementation of the OpenStack  |
 |             |               |            | bgpvpn API from the SDNVPN       |
@@ -153,8 +147,15 @@ validate the scenario for the release.
 |             |               | vyos       | vRouter testing                  |
 |             |               | \_vrouter  |                                  |
 |             |               +------------+----------------------------------+
-|             |               | juju_epc   | vEPC validation with Juju as VNF |
-|             |               |            | manager and ABoT as test executor|
+|             |               | juju_epc   | Validates deployment of a complex|
+|             |               |            | mobility VNF on OPNFV Platform.  |
+|             |               |            | Uses Juju for deploying the OAI  |
+|             |               |            | EPC  and ABot for defining test  |
+|             |               |            | scenarios using high-level DSL.  |
+|             |               |            | VNF tests reference 3GPP         |
+|             |               |            | Technical Specs and are executed |
+|             |               |            | through protocol drivers provided|
+|             |               |            | by ABot.                         |
 |             |               +------------+----------------------------------+
 |             |               | cloudify   | Based on cloudify_ims test case  |
 |             |               | \_ims_perf | cloudify_ims_perf substitutes    |
@@ -171,6 +172,21 @@ validate the scenario for the release.
 |             |               |            | requires access to proprietary   |
 |             |               |            | resources (Ixia loader)          |
 +-------------+---------------+------------+----------------------------------+
+| Kubernetes  | healthcheck   | k8s_smoke  | Test a running Kubernetes        |
+|             |               |            | cluster and ensure it satisfies  |
+|             |               |            | minimal functional requirements  |
+|             +---------------+------------+----------------------------------+
+|             | smoke         | k8s\_      | Run a subset of Kubernetes       |
+|             |               | conformance| End-to-End tests, expected to    |
+|             |               |            | pass on any Kubernetes cluster   |
+|             +---------------+------------+----------------------------------+
+|             | stor4nfv      | stor4nfv   | Run tests necessary to           |
+|             |               | \_k8s      | demonstrate conformance of the   |
+|             |               |            | K8s+Stor4NFV deployment          |
+|             +---------------+------------+----------------------------------+
+|             | clover        | clover_k8s | Test functionality of            |
+|             |               |            | K8s+Istio+Clover deployment.     |
++-------------+---------------+------------+----------------------------------+
 
 
 As shown in the above table, Functest is structured into different 'domains',
@@ -186,7 +202,7 @@ In Danube, we merged smoke and sdn controller tiers in smoke tier.
 
 An overview of the Functest Structural Concept is depicted graphically below:
 
-.. figure:: ../../../images/concepts_mapping_final.png
+.. figure:: ../../../images/concepts_mapping_fraser.png
    :align: center
    :alt: Functest Concepts Structure