Functest Doc: first update for Euphrates

- move part of the dev group to the testing document
- move reporting into user guide
- update logs
- introduce alpine
- introduce functest API
- split documents per chapter

Change-Id: I08268091ce50309e891a648333da2054e902bcea
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>

1 files changed, 151 insertions, 824 deletions

diff --git a/docs/testing/developer/devguide/index.rst b/docs/testing/developer/devguide/index.rst
index dceb4ab0b..6bc46081f 100644
--- a/docs/testing/developer/devguide/index.rst
+++ b/docs/testing/developer/devguide/index.rst
@@ -9,6 +9,23 @@ OPNFV FUNCTEST developer guide
    :numbered:
    :maxdepth: 2
 
+Version history
+===============
++------------+----------+------------------+----------------------------------+
+| **Date**   | **Ver.** | **Author**       | **Comment**                      |
+|            |          |                  |                                  |
++------------+----------+------------------+----------------------------------+
+| 2017-01-23 | 1.0.0    | Morgan Richomme  | Creation for Danube              |
++------------+----------+------------------+----------------------------------+
+| 2017-08-16 | 1.0.1    | Morgan Richomme  | Adaptations for Euphrates        |
+|            |          |                  | - move generic part to Testing   |
+|            |          |                  | developer guide                  |
+|            |          |                  | - move reporting part to functest|
+|            |          |                  | user guide                       |
+|            |          |                  | - update test case list          |
+|            |          |                  | - include auto generated core    |
+|            |          |                  | documentation                    |
++------------+----------+------------------+----------------------------------+
 
 ============
 Introduction
@@ -17,16 +34,18 @@ Introduction
 Functest is a project dealing with functional testing.
 Functest produces its own internal test cases but can also be considered
 as a framework to support feature and VNF onboarding project testing.
-Functest developed a TestAPI and defined a test collection framework
-that can be used by any OPNFV project.
 
 Therefore there are many ways to contribute to Functest. You can:
 
  * Develop new internal test cases
  * Integrate the tests from your feature project
  * Develop the framework to ease the integration of external test cases
- * Develop the API / Test collection framework
- * Develop dashboards or automatic reporting portals
+
+Additional tasks involving Functest but addressing all the test projects
+may also be mentioned:
+
+  * Develop the API / Test collection framework
+  * Develop dashboards or automatic reporting portals
 
 This document describes how, as a developer, you may interact with the
 Functest project. The first section details the main working areas of
@@ -42,8 +61,23 @@ Functest developer areas
 Functest High level architecture
 ================================
 
-Functest is project delivering a test container dedicated to OPNFV.
+Functest is a project delivering test containers dedicated to OPNFV.
 It includes the tools, the scripts and the test scenarios.
+Until Danube, Functest produced 2 docker files based on Ubuntu 14.04:
+
+  * x86 Functest: https://hub.docker.com/r/opnfv/functest/
+  * aarch64 Functest: https://hub.docker.com/r/opnfv/functest_aarch64/
+
+In Euphrates Alpine containers have been introduced in order to lighten the
+container and manage testing slicing, the new containers are created according
+to the different tiers:
+
+  * functest-core: https://hub.docker.com/r/opnfv/functest-core/
+  * functest-healthcheck: https://hub.docker.com/r/opnfv/functest-healthcheck/
+  * functest-smoke: https://hub.docker.com/r/opnfv/functest-smoke/
+  * functest-features: TODO
+  * functest-components: TODO
+  * functest-vnf: TODO
 
 Functest can be described as follow::
 
@@ -63,7 +97,7 @@ Functest can be described as follow::
 
 Functest internal test cases
 ============================
-The internal test cases in Danube are:
+The internal test cases in Euphrates are:
 
 
  * api_check
@@ -72,33 +106,37 @@ The internal test cases in Danube are:
  * vping_ssh
  * vping_userdata
  * odl
+ * odl-netvirt
+ * odl-fds
  * rally_full
  * rally_sanity
  * snaps_health_check
  * tempest_full_parallel
  * tempest_smoke_serial
+ * cloudify_ims
 
-By internal, we mean that this particular test cases have been
-developped and/or integrated by functest contributors and the associated
-code is hosted in the Functest repository.
+By internal, we mean that this particular test cases have been developed and/or
+integrated by functest contributors and the associated code is hosted in the
+Functest repository.
 An internal case can be fully developed or a simple integration of
-upstream suites (e.g. Tempest/Rally developped in OpenStack are just
-integrated in Functest).
+upstream suites (e.g. Tempest/Rally developed in OpenStack, or odl suites are
+just integrated in Functest).
+
 The structure of this repository is detailed in `[1]`_.
 The main internal test cases are in the opnfv_tests subfolder of the
 repository, the internal test cases are:
 
- * sdn: odl, onos
- * openstack: api_check, connection_check, snaps_health_check, vping_ssh, vping_userdata, tempest_*, rally_*, snaps_smoke
+ * sdn: odl, odl_netvirt, odl_fds, onos
+ * openstack: api_check, connection_check, snaps_health_check, vping_ssh, vping_userdata, tempest_*, rally_*
  * vnf: cloudify_ims
 
-If you want to create a new test case you will have to create a new
-folder under the testcases directory.
+If you want to create a new test case you will have to create a new folder under
+the testcases directory (See next section for details).
 
 Functest external test cases
 ============================
-The external test cases are inherited from other OPNFV projects,
-especially the feature projects.
+The external test cases are inherited from other OPNFV projects, especially the
+feature projects.
 
 The external test cases are:
 
@@ -106,32 +144,36 @@ The external test cases are:
  * bgpvpn
  * doctor
  * domino
- * odl-netvirt
  * onos
  * fds
  * orchestra_ims
  * parser
  * promise
  * refstack_defcore
- * security_scan
  * snaps_smoke
- * sfc-odl
+ * functest-odl-sfc
  * vyos_vrouter
 
+External test cases integrated in previous versions but not released in
+Euphrates:
+
+ * copper
+ * netready
+ * security_scan
+
+
+The code to run these test cases is hosted in the repository of the project.
 
-The code to run these test cases may be directly in the repository of
-the project. We have also a **features** sub directory under opnfv_tests
-directory that may be used (it can be useful if you want to reuse
-Functest library).
 
 Functest framework
 ==================
 
-Functest can be considered as a framework.
-Functest is release as a docker file, including tools, scripts and a CLI
-to prepare the environment and run tests.
-It simplifies the integration of external test suites in CI pipeline
-and provide commodity tools to collect and display results.
+Functest is a framework.
+
+Historically Functest is released as a docker file, including tools, scripts and
+a CLI to prepare the environment and run tests.
+It simplifies the integration of external test suites in CI pipeline and provide
+commodity tools to collect and display results.
 
 Since Colorado, test categories also known as tiers have been created to
 group similar tests, provide consistent sub-lists and at the end optimize
@@ -148,19 +190,23 @@ The tiers are:
   * vnf
   * stress
 
+Note Functest deals with healthcheck, smoke, features, components and vnf tiers.
+Performance and stress tiers are out of scope.
+
 Functest abstraction classes
 ============================
 
-In order to harmonize test integration, 3 abstraction classes have been
-introduced in Danube:
+In order to harmonize test integration, abstraction classes have been
+introduced:
 
  * testcase: base for any test case
+ * unit: run unit tests as test case
  * feature: abstraction for feature project
- * vnf_base: abstraction for vnf onboarding
+ * vnf: abstraction for vnf onboarding
 
-The goal is to unify the way to run test from Functest.
+The goal is to unify the way to run tests in Functest.
 
-feature and vnf_base inherit from testcase::
+Feature, unit and vnf_base inherit from testcase::
 
               +-----------------------------------------+
               |                                         |
@@ -172,785 +218,94 @@ feature and vnf_base inherit from testcase::
               |         - check_criteria()              |
               |                                         |
               +-----------------------------------------+
-                     |                       |
-                     V                       V
-         +--------------------+   +--------------------------+
-         |                    |   |                          |
-         |    feature         |   |      vnf_base            |
-         |                    |   |                          |
-         |  - prepare()       |   |  - prepare()             |
-         |  - execute()       |   |  - deploy_orchestrator() |
-         |  - post()          |   |  - deploy_vnf()          |
-         |  - parse_results() |   |  - test_vnf()            |
-         |                    |   |  - clean()               |
-         |                    |   |  - execute()             |
-         |                    |   |                          |
-         +--------------------+   +--------------------------+
+                 |               |
+                 V               V
+  +--------------------+   +--------------+   +--------------------------+
+  |                    |   |              |   |                          |
+  |    feature         |   |    unit      |   |      vnf                 |
+  |                    |   |              |   |                          |
+  |                    |   |              |   |  - prepare()             |
+  |  - execute()       |   |              |   |  - deploy_orchestrator() |
+  | BashFeature class  |   |              |   |  - deploy_vnf()          |
+  |                    |   |              |   |  - test_vnf()            |
+  |                    |   |              |   |  - clean()               |
+  +--------------------+   +--------------+   +--------------------------+
+
+
+Testcase
+========
+.. raw:: html
+   :url: http://artifacts.opnfv.org/functest/docs/apidoc/functest.core.testcase.html
+
+Feature
+=======
+.. raw:: html
+   :url: http://artifacts.opnfv.org/functest/docs/apidoc/functest.core.feature.html
+
+Unit
+====
+.. raw:: html
+   :url: http://artifacts.opnfv.org/functest/docs/apidoc/functest.core.unit.html
+
+VNF
+===
+.. raw:: html
+   :url: http://artifacts.opnfv.org/functest/docs/apidoc/functest.core.vnf.html
+
+
+see `Functest framework overview`_ to get code samples
 
 
 Functest util classes
 =====================
 
-In order to simplify the creation of test cases, Functest develops some
+In order to simplify the creation of test cases, Functest develops also some
 functions that can be used by any feature or internal test cases.
 Several features are supported such as logger, configuration management and
 Openstack capabilities (snapshot, clean, tacker,..).
 These functions can be found under <repo>/functest/utils and can be described as
-follows:
-
-functest/utils/
-|-- config.py
-|-- constants.py
-|-- env.py
-|-- functest_logger.py
-|-- functest_utils.py
-|-- openstack_clean.py
-|-- openstack_snapshot.py
-|-- openstack_tacker.py
-`-- openstack_utils.py
-
-Note that for Openstack, keystone v3 is now deployed by default by compass,
-fuel and joid in Danube. All installers still support keystone v2 (deprecated in
-next version).
-
-Test collection framework
-=========================
-
-The OPNFV testing group created a test collection database to collect
-the test results from CI:
-
-
- http://testresults.opnfv.org/test/swagger/spec.html
-
- Authentication: opnfv/api@opnfv
-
-Any test project running on any lab integrated in CI can push the
-results to this database.
-This database can be used to see the evolution of the tests and compare
-the results versus the installers, the scenarios or the labs.
-
-
-Overall Architecture
---------------------
-The Test result management can be summarized as follows::
-
-  +-------------+    +-------------+    +-------------+
-  |             |    |             |    |             |
-  |   Test      |    |   Test      |    |   Test      |
-  | Project #1  |    | Project #2  |    | Project #N  |
-  |             |    |             |    |             |
-  +-------------+    +-------------+    +-------------+
-           |               |               |
-           V               V               V
-       +-----------------------------------------+
-       |                                         |
-       |         Test Rest API front end         |
-       |  http://testresults.opnfv.org/test      |
-       |                                         |
-       +-----------------------------------------+
-           A                |
-           |                V
-           |     +-------------------------+
-           |     |                         |
-           |     |    Test Results DB      |
-           |     |         Mongo DB        |
-           |     |                         |
-           |     +-------------------------+
-           |
-           |
-     +----------------------+
-     |                      |
-     |    test Dashboard    |
-     |                      |
-     +----------------------+
-
-TestAPI description
--------------------
-The TestAPI is used to declare pods, projects, test cases and test
-results. Pods are the pods used to run the tests.
-The results pushed in the database are related to pods, projects and
-cases. If you try to push results of test done on non referenced pod,
-the API will return an error message.
-
-An additional method dashboard has been added to post-process
-the raw results in release Brahmaputra (deprecated in Colorado).
-
-The data model is very basic, 5 objects are created:
-
-  * Pods
-  * Projects
-  * Testcases
-  * Results
-  * Scenarios
-
-The code of the API is hosted in the releng repository `[6]`_.
-The static documentation of the API can be found at `[17]`_.
-The TestAPI has been dockerized and may be installed locally in your
-lab. See `[15]`_ for details.
-
-The deployment of the TestAPI has been automated.
-A jenkins job manages:
-  * the unit tests of the TestAPI
-  * the creation of a new docker file
-  * the deployment of the new TestAPI
-  * the archive of the old TestAPI
-  * the backup of the Mongo DB
-
-TestAPI Authorization
-~~~~~~~~~~~~~~~~~~~~~
-
-PUT/DELETE/POST operations of the TestAPI now require token based authorization. The token needs
-to be added in the request using a header 'X-Auth-Token' for access to the database.
-
-e.g::
-    headers['X-Auth-Token']
-
-The value of the header i.e the token can be accessed in the jenkins environment variable
-*TestApiToken*. The token value is added as a masked password.
-
-.. code-block:: python
-
-    headers['X-Auth-Token'] = os.environ.get('TestApiToken')
-
-The above example is in Python. Token based authentication has been added so that only ci pods
-jenkins job can have access to the database.
-
-Please note that currently token authorization is implemented but is not yet enabled.
-
-  Automatic reporting
-  ===================
-
-  An automatic reporting page has been created in order to provide a
-  consistent view of the scenarios.
-  In this page, each scenario is evaluated according to test criteria.
-  The code for the automatic reporting is available at `[8]`_.
-
-  The results are collected from the centralized database every day and,
-  per scenario. A score is calculated based on the results from the last
-  10 days. This score is the addition of single test scores. Each test
-  case has a success criteria reflected in the criteria field from the
-  results.
-
-  Considering an instance of a scenario os-odl_l2-nofeature-ha, the
-  scoring is the addition of the scores of all the runnable tests from the
-  categories (tiers healthcheck, smoke and features)
-  corresponding to this scenario.
-
-
-   +---------------------+---------+---------+---------+---------+
-   | Test                | Apex    | Compass | Fuel    |  Joid   |
-   +=====================+=========+=========+=========+=========+
-   | vPing_ssh           |    X    |    X    |    X    |    X    |
-   +---------------------+---------+---------+---------+---------+
-   | vPing_userdata      |    X    |    X    |    X    |    X    |
-   +---------------------+---------+---------+---------+---------+
-   | tempest_smoke_serial|    X    |    X    |    X    |    X    |
-   +---------------------+---------+---------+---------+---------+
-   | rally_sanity        |    X    |    X    |    X    |    X    |
-   +---------------------+---------+---------+---------+---------+
-   | odl                 |    X    |    X    |    X    |    X    |
-   +---------------------+---------+---------+---------+---------+
-   | promise             |         |         |    X    |    X    |
-   +---------------------+---------+---------+---------+---------+
-   | doctor              |    X    |         |    X    |         |
-   +---------------------+---------+---------+---------+---------+
-   | security_scan       |    X    |         |         |         |
-   +---------------------+---------+---------+---------+---------+
-   | parser              |         |         |    X    |         |
-   +---------------------+---------+---------+---------+---------+
-   src: colorado (see release note for the last matrix version)
-
-  All the testcases listed in the table are runnable on
-  os-odl_l2-nofeature scenarios.
-  If no result is available or if all the results are failed, the test
-  case get 0 point.
-  If it was successful at least once but not anymore during the 4 runs,
-  the case get 1 point (it worked once).
-  If at least 3 of the last 4 runs were successful, the case get 2 points.
-  If the last 4 runs of the test are successful, the test get 3 points.
-
-  In the example above, the target score for fuel/os-odl_l2-nofeature-ha
-  is 3x6 = 18 points.
-
-  The scenario is validated per installer when we got 3 points for all
-  individual test cases (e.g 18/18).
-  Please note that complex or long duration tests are not considered for
-  the scoring. The success criteria are not always easy to define and may
-  require specific hardware configuration. These results however provide
-  a good level of trust on the scenario.
-
-  A web page is automatically generated every day to display the status.
-  This page can be found at `[9]`_. For the status, click on Status menu,
-  you may also get feedback for vims and tempest_smoke_serial test cases.
-
-  Any validated scenario is stored in a local file on the web server. In
-  fact as we are using a sliding windows to get results, it may happen
-  that a successful scenarios is no more run (because considered as
-  stable) and then the number of iterations (4 needed) would not be
-  sufficient to get the green status.
-
-  Please note that other test cases (e.g. sfc_odl, bgpvpn) need also
-  ODL configuration addons and as a consequence specific scenario.
-  There are not considered as runnable on the generic odl_l2 scenario.
-
-Dashboard
-=========
-
-Dashboard is used to provide a consistent view of the results collected
-in CI.
-The results showed on the dashboard are post processed from the Database,
-which only contains raw results.
-
-In Brahmaputra, we created a basic dashboard.
-Since Colorado, it was decided to adopt ELK framework. Mongo DB results
-are extracted to feed Elasticsearch database (`[7]`_).
+follows::
 
-A script was developed to build elasticsearch data set. This
-script can be found in `[16]`_.
+ functest/utils/
+ |-- config.py
+ |-- constants.py
+ |-- decoratos.py
+ |-- env.py
+ |-- functest_utils.py
+ |-- openstack_clean.py
+ |-- openstack_snapshot.py
+ |-- openstack_tacker.py
+ `-- openstack_utils.py
 
-For next versions, it was decided to integrated bitergia dashboard.
-Bitergia already provides a dashboard for code and infrastructure.
-A new Test tab will be added. The dataset will be built by consuming
-the TestAPI.
+Please note that it is possible to use snaps utils. SNAPS `[4]`_ is an OPNFV
+project providing OpenStack utils.
 
 
+TestAPI
 =======
-How TOs
-=======
-
-How Functest works?
-===================
-
-The installation and configuration of the Functest docker image is
-described in `[1]`_.
-
-The procedure to start tests is described  in `[2]`_
-
-
-How can I contribute to Functest?
-=================================
-
-If you are already a contributor of any OPNFV project, you can
-contribute to functest. If you are totally new to OPNFV, you must first
-create your Linux Foundation account, then contact us in order to
-declare you in the repository database.
-
-We distinguish 2 levels of contributors:
-
- * the standard contributor can push patch and vote +1/0/-1 on any Functest patch
- * The commitor can vote -2/-1/0/+1/+2 and merge
-
-Functest commitors are promoted by the Functest contributors.
-
-
-Where can I find some help to start?
-====================================
-
-This guide is made for you. You can also have a look at the project wiki
-page `[10]`_.
-There are references on documentation, video tutorials, tips...
-
-You can also directly contact us by mail with [Functest] prefix in the
-title at opnfv-tech-discuss@lists.opnfv.org or on the IRC chan
-#opnfv-functest.
-
-
-What kind of testing do you do in Functest?
-===========================================
-
-Functest is focusing on Functional testing. The results must be PASS or
-FAIL. We do not deal with performance and/or qualification tests.
-We consider OPNFV as a black box and execute our tests from the jumphost
-according to Pharos reference technical architecture.
-
-Upstream test suites are integrated (Rally/Tempest/ODL/ONOS,...).
-If needed Functest may bootstrap temporarily testing activities if they
-are identified but not covered yet by an existing testing project (e.g
-security_scan before the creation of the security repository)
-
-
-How are test constraints defined?
-=================================
-
-Test constraints are defined according to 2 parameters:
-
- * The scenario (DEPLOY_SCENARIO env variable)
- * The installer (INSTALLER_TYPE env variable)
-
-A scenario is a formal description of the system under test.
-The rules to define a scenario are described in `[4]`_
-
-These 2 constraints are considered to determinate if the test is runnable
-or not (e.g. no need to run onos suite on odl scenario).
-
-In the test declaration for CI, the test owner shall indicate these 2
-constraints. The file testcases.yaml `[5]`_ must be patched in git to
-include new test cases. A more elaborated system based on template is
-planned for next releases
-
-For each dependency, it is possible to define a regex::
-
-    name: promise
-    criteria: 'success_rate == 100%'
-    description: >-
-        Test suite from Promise project.
-    dependencies:
-        installer: '(fuel)|(joid)'
-        scenario: ''
-
-In the example above, it means that promise test will be runnable only
-with joid or fuel installers on any scenario.
-
-The vims criteria means any installer and exclude onos and odl with
-bgpvpn scenarios::
-
-    name: vims
-    criteria: 'status == "PASS"'
-    description: >-
-        This test case deploys an OpenSource vIMS solution from Clearwater
-        using the Cloudify orchestrator. It also runs some signaling traffic.
-    dependencies:
-        installer: ''
-        scenario: '(ocl)|(nosdn)|^(os-odl)((?!bgpvpn).)*$'
-
-
-How to write and check constraint regex?
-=======================================
-
-Regex are standard regex. You can have a look at  `[11]`_
-
-You can also easily test your regex via an online regex checker such as `[12]`_.
-Put your scenario in the TEST STRING window (e.g. os-odl_l3-ovs-ha), put
-your regex in the REGULAR EXPRESSION window, then you can test your rule.
-
-
-How to know which test I can run?
-=================================
-
-You can use the API `[13]`_. The static declaration is in git `[5]`_
-
-If you are in a Functest docker container (assuming that the
-environment has been prepared): just use the CLI.
-
-You can get the list per Test cases or by Tier::
-
-    # functest testcase list
-    healthcheck
-    vping_ssh
-    vping_userdata
-    tempest_smoke_serial
-    rally_sanity
-    odl
-    doctor
-    security_scan
-    tempest_full_parallel
-    rally_full
-    vims
-    # functest tier list
-    - 0. healthcheck:
-    ['healthcheck']
-    - 1. smoke:
-    ['vping_ssh', 'vping_userdata', 'tempest_smoke_serial', 'rally_sanity']
-    - 2. sdn_suites:
-    ['odl']
-    - 3. features:
-    ['doctor', 'security_scan']
-    - 4. openstack:
-    ['tempest_full_parallel', 'rally_full']
-    - 5. vnf:
-    ['vims']
-
-
-How to manually start Functest tests?
-=====================================
-
-Assuming that you are connected on the jumphost and that the system is
-"Pharos compliant", i.e the technical architecture is compatible with
-the one defined in the Pharos project::
-
-    # docker pull opnfv/functest:latest
-    # envs="-e INSTALLER_TYPE=fuel -e INSTALLER_IP=10.20.0.2 -e DEPLOY_SCENARIO=os-odl_l2-nofeature-ha -e CI_DEBUG=true"
-    # sudo docker run --privileged=true -id ${envs} opnfv/functest:latest /bin/bash
-
-
-Then you must connect to the docker container and source the
-credentials::
-
-    # docker ps (copy the id)
-    # docker exec -ti <container_id> bash
-    # source $creds
-
-
-You must first check if the environment is ready::
-
-    # functest env status
-    Functest environment ready to run tests.
-
-
-If not ready, prepare the env by launching::
-
-    # functest env prepare
-    Functest environment ready to run tests.
-
-Once the Functest env is ready, you can use the CLI to start tests.
-
-You can run test cases per test case or per tier:
- # functest testcase run <case name> or # functest tier run  <tier name>
-
-
-e.g::
-
-    # functest testcase run tempest_smoke_serial
-    # functest tier run features
-
-
-If you want to run all the tests you can type::
-
-    # functest testcase run all
-
-
-If you want to run all the tiers (same at the end that running all the
-test cases) you can type::
-
-    # functest tier run all
-
-
-How to declare my tests in Functest?
-====================================
-
-If you want to add new internal test cases, you can submit patch under
-the testcases directory of Functest repository.
-
-For feature test integration, the code can be kept into your own
-repository. The Functest files to be modified are:
-
- * functest/docker/Dockerfile: get your code in Functest container
- * functest/ci/testcases.yaml: reference your test and its associated constraints
-
-
-Dockerfile
-----------
-
-This file lists the repositories (internal or external) to be cloned in
-the Functest container. You can also add external packages::
-
- RUN git clone https://gerrit.opnfv.org/gerrit/<your project> ${REPOS_DIR}/<your project>
-
-testcases.yaml
---------------
-
-All the test cases that must be run from CI / CLI must be declared in
-ci/testcases.yaml.
+Functest is using the Test collection framework and the TestAPI developed by
+the OPNFV community. See `OPNFV Test collection framework`_ for details.
 
-This file is used to get the constraints related to the test::
 
-    name: <my_super_test_case>
-    criteria: <not used yet in Colorado, could be > 'PASS', 'rate > 90%'
-    description: >-
-        <the description of your super test suite>
-    dependencies:
-        installer: regex related to installer e.g. 'fuel', '(apex)||(joid)'
-        scenario: regex related to the scenario e.g. 'ovs*no-ha'
-
-
-You must declare your test case in one of the category (tier).
-
-If you are integrating test suites from a feature project, the default
-category is **features**.
-
-
-How to select my list of tests for CI?
-======================================
-
-Functest can be run automatically from CI, a jenkins job is usually
-called after an OPNFV fresh installation.
-By default we try to run all the possible tests (see `[14]` called from
-Functest jenkins job)::
-
-    cmd="python ${FUNCTEST_REPO_DIR}/ci/run_tests.py -t all ${flags}"
-
-
-Each case can be configured as daily and/or weekly task.
-Weekly tasks are used for long duration or experimental tests.
-Daily tasks correspond to the minimum set of test suites to validate a scenario.
-
-When executing run_tests.py, a check based on the jenkins build tag will
-be considered to detect whether it is a daily and/or a weekly test.
-
-in your CI you can customize the list of test you want to run by case or
-by tier, just change the line::
-
-    cmd="python ${FUNCTEST_REPO_DIR}/ci/run_tests.py -t <whatever you want> ${flags}"
-
-e.g.::
-
-    cmd="python ${FUNCTEST_REPO_DIR}/ci/run_tests.py -t healthcheck,smoke ${flags}"
-
-This command will run all the test cases of the first 2 tiers, i.e.
-healthcheck, connection_check, api_check, vping_ssh, vping_userdata,
-snaps_smoke, tempest_smoke_serial and rally_sanity.
-
-
-How to push your results into the Test Database
-===============================================
-
-The test database is used to collect test results. By default it is
-enabled only for CI tests from Production CI pods.
-
-The architecture and associated API is described in previous chapter.
-If you want to push your results from CI, you just have to call the API
-at the end of your script.
-
-You can also reuse a python function defined in functest_utils.py::
-
-    def push_results_to_db(db_url, case_name, logger, pod_name,version, payload):
-      """
-      POST results to the Result target DB
-      """
-      url = db_url + "/results"
-      installer = get_installer_type(logger)
-      params = {"project_name": "functest", "case_name": case_name,
-                "pod_name": pod_name, "installer": installer,
-                "version": version, "details": payload}
-
-      headers = {'Content-Type': 'application/json'}
-      try:
-          r = requests.post(url, data=json.dumps(params), headers=headers)
-          if logger:
-              logger.debug(r)
-          return True
-      except Exception, e:
-          print "Error [push_results_to_db('%s', '%s', '%s', '%s', '%s')]:" \
-              % (db_url, case_name, pod_name, version, payload), e
-          return False
-
-
-Where can I find the documentation on the test API?
-===================================================
-
-http://artifacts.opnfv.org/releng/docs/testapi.html
-
-
-How to exclude Tempest case from default Tempest smoke suite?
-=============================================================
-
-Tempest default smoke suite deals with 165 test cases.
-Since Colorado the success criteria is 100%, i.e. if 1 test is failed the
-success criteria is not matched for the scenario.
-
-It is necessary to exclude some test cases that are expected to fail due to
-known upstream bugs (see release notes).
-
-A file has been created for such operation: https://git.opnfv.org/cgit/functest/tree/functest/opnfv_tests/openstack/tempest/custom_tests/blacklist.txt.
-
-It can be described as follows::
-
-    -
-        scenarios:
-            - os-odl_l2-bgpvpn-ha
-            - os-odl_l2-bgpvpn-noha
-        installers:
-            - fuel
-            - apex
-        tests:
-            - tempest.api.compute.servers.test_create_server.ServersTestJSON.test_list_servers
-            - tempest.api.compute.servers.test_create_server.ServersTestJSON.test_verify_server_details
-            - tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_list_servers
-            - tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_verify_server_details
-            - tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_reboot_server_hard
-            - tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops
-            - tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops
-            - tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
-            - tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
-
-Please note that each exclusion must be justified. the goal is not to exclude
-test cases because they do not pass. Several scenarios reached the 100% criteria.
-So it is expected in the patch submitted to exclude the cases to indicate the
-reasons of the exclusion.
-
-
-How do I know the Functest status of a scenario?
-================================================
-
-A Functest automatic reporting page is generated daily.
-This page is dynamically created through a cron job and is based on the results
-stored in the Test DB.
-You can access this reporting page: http://testresults.opnfv.org/reporting
-
-See https://wiki.opnfv.org/pages/viewpage.action?pageId=6828617 for details.
-
-
-I have tests, to which category should I declare them?
-======================================================
-
-CATEGORIES/TIERS description:
-
-+----------------+-------------------------------------------------------------+
-| healthcheck    | Simple OpenStack healthcheck tests case that validates the  |
-|                | basic operations in OpenStack                               |
-+----------------+-------------------------------------------------------------+
-|   Smoke        | Set of smoke test cases/suites to validate the most common  |
-|                | OpenStack and SDN Controller operations                     |
-+----------------+-------------------------------------------------------------+
-|   Features     | Test cases that validate a specific feature on top of OPNFV.|
-|                | Those come from Feature projects and need a bit of support  |
-|                | for integration                                             |
-+----------------+-------------------------------------------------------------+
-| Components     | Advanced OpenStack tests: Full Tempest, Full Rally          |
-+----------------+-------------------------------------------------------------+
-| Performance    | Out of Functest Scope                                       |
-+----------------+-------------------------------------------------------------+
-| VNF            | Test cases related to deploy an open source VNF including   |
-|                | an orchestrator                                             |
-+----------------+-------------------------------------------------------------+
-
-The main ambiguity could be between features and VNF.
-In fact sometimes you have to spawn VMs to demonstrate the capabilities of the
-feature you introduced.
-We recommend to declare your test in the feature category.
-
-VNF category is really dedicated to test including:
-
- * creation of resources
- * deployment of an orchestrator/VNFM
- * deployment of the VNF
- * test of the VNFM
- * free resources
-
-The goal is not to study a particular feature on the infrastructure but to have
-a whole end to end test of a VNF automatically deployed in CI.
-Moreover VNF are run in weekly jobs (one a week), feature tests are in daily
-jobs and use to get a scenario score.
-
-Where are the logs?
-===================
-
-Functest deals with internal and external testcases. Each testcase can generate
-logs.
-
-Since Colorado we introduce the possibility to push the logs to the artifact.
-A new script (https://git.opnfv.org/releng/tree/utils/push-test-logs.sh) has
-been created for CI.
-
-When called, and assuming that the POD is authorized to push the logs to
-artifacts, the script will push all the results or logs locally stored under
-/home/opnfv/functest/results/.
-
-If the POD is not connected to CI, logs are not pushed.
-But in both cases, logs are stored in /home/opnfv/functest/results in the
-container.
-Projects are encouraged to push their logs here.
-
-Since Colorado it is also easy for feature project to integrate this feature by
-adding the log file as output_file parameter when calling execute_command from
-functest_utils library
-
-  ret_val = functest_utils.execute_command(cmd, output_file=log_file)
-
-
-How does Functest deal with VNF onboarding?
-===========================================
-
-VNF onboarding has been introduced in Brahmaputra through the automation of a
-clearwater vIMS deployed thanks to cloudify orchestrator.
-
-This automation has been described at OpenStack summit Barcelona:
-https://youtu.be/Jr4nG74glmY
-
-The goal of Functest consists in testing OPNFV from a functional perspective:
-the NFVI and/or the features developed in OPNFV. Feature test suites are
-provided by the feature project. Functest just simplifies the integration of
-the suite into the CI and gives a consolidated view of the tests per scenario.
-
-Functest does not develop VNFs.
-
-Functest does not test any MANO stack.
-
-OPNFV projects dealing with VNF onboarding
-------------------------------------------
-
-Testing VNF is not the main goal however it gives interesting and realistic
-feedback on OPNFV as a Telco cloud.
-
-Onboarding VNF also allows to test a full stack: orchestrator + VNF.
-
-Functest is VNF and MANO stack agnostic.
-
-An internship has been initiated to reference the Open Source VNF: Intern
-Project Open Source VNF catalog
-
-New projects dealing with orchestrators or VNFs are candidate for Danube.
-
-The 2 projects dealing with orchestration are:
-
- * orchestra (Openbaton)
- * opera (Open-O)
-
-The Models project address various goals for promoting availability and
-convergence of information and/or data models related to NFV service/VNF
-management, as being defined in standards (SDOs) and as developed in open
-source projects.
-
-Functest VNF onboarding
------------------------
-
-In order to simplify VNF onboarding a new abstraction class has been developed
-in Functest.
-
-This class is based on vnf_base and can be described as follow:
-
- +------------+             +--------------+
- | test_base  |------------>|   vnf_base   |
- +------------+             +--------------+
-                              |_ prepare
-                                  |_ deploy_orchestrator (optional)
-                                      |_ deploy_vnf
-                                        |_ test_vnf
-                                          |_ clean
-
-
-Several methods are declared in vnf_base:
-
- * prepare
- * deploy_orchestrator
- * deploy_vnf
- * test_vnf
- * clean
-
-deploy_vnf and test_vnf are mandatory.
-
-prepare will create a user and a project.
-
-How to declare your orchestrator/VNF?
--------------------------------------
-1) test declaration
-
-You must declare your testcase in the file <Functest repo>/functest/ci/testcases.yaml
-
-2) configuration
-
-You can precise some configuration parameters in config_functest.yaml
-
-3) implement your test
+Reporting
+=========
+A web page is automatically generated every day to display the status based on
+jinja2 templates `[3]`_.
 
-Create your own VnfOnboarding file
 
-you must create your entry point through a python class as referenced in the
-configuration file
+Dashboard
+=========
 
-e.g. aaa => creation of the file <Functest repo>/functest/opnfv_tests/vnf/aaa/aaa.py
+Additional dashboarding is managed at the testing group level, see
+`OPNFV Testing dashboard`_
 
-the class shall inherit vnf_base.
-You must implement the methods deploy_vnf() and test_vnf() and may implement
-deploy_orchestrator()
 
-you can call the code from your repo (but need to add the repo in Functest if
-it is not the case)
+=======
+How TOs
+=======
 
-4) success criteria
+See `How to section`_ on Functest wiki
 
-So far we considered the test as PASS if vnf_deploy and test_vnf is PASS
-(see example in aaa).
 
 ==========
 References
@@ -960,44 +315,16 @@ _`[1]`: http://artifacts.opnfv.org/functest/docs/configguide/index.html Functest
 
 _`[2]`: http://artifacts.opnfv.org/functest/docs/userguide/index.html functest user guide
 
-_`[3]`: https://wiki.opnfv.org/opnfv_test_dashboard Brahmaputra dashboard
-
-_`[4]`: https://wiki.opnfv.org/display/INF/CI+Scenario+Naming
-
-_`[5]`: https://git.opnfv.org/cgit/functest/tree/ci/testcases.yaml
+_`[3]`: https://git.opnfv.org/cgit/releng/tree/utils/test/reporting
 
-_`[6]`: https://git.opnfv.org/cgit/releng/tree/utils/test/result_collection_api
+_`[4]`: https://git.opnfv.org/snaps/
 
-_`[7]`: https://git.opnfv.org/cgit/releng/tree/utils/test/scripts
+_`Functest framework overview` : http://testresults.opnfv.org/functest/framework/index.html
 
-_`[8]`: https://git.opnfv.org/cgit/releng/tree/utils/test/reporting/functest
+_`OPNFV Test collection framework`: TODO
 
-_`[9]`: http://testresults.opnfv.org/reporting/
+_`OPNFV Testing dashboard`: https://opnfv.biterg.io/goto/283dba93ca18e95964f852c63af1d1ba
 
-_`[10]`: https://wiki.opnfv.org/opnfv_functional_testing
-
-_`[11]`: https://docs.python.org/2/howto/regex.html
-
-_`[12]`: https://regex101.com/
-
-_`[13]`: http://testresults.opnfv.org/test/api/v1/projects/functest/cases
-
-_`[14]`: https://git.opnfv.org/cgit/releng/tree/jjb/functest/functest-daily.sh
-
-_`[15]`: https://git.opnfv.org/cgit/releng/tree/utils/test/result_collection_api/README.rst
-
-_`[16]`: https://git.opnfv.org/cgit/releng/tree/utils/test/scripts/mongo_to_elasticsearch.py
-
-_`[17]`: http://artifacts.opnfv.org/releng/docs/testapi.html
-
-OPNFV main site: http://www.opnfv.org
-
-OPNFV functional test page: https://wiki.opnfv.org/opnfv_functional_testing
+_`How to section`: https://wiki.opnfv.org/pages/viewpage.action?pageId=7768932
 
 IRC support chan: #opnfv-functest
-
-_`OpenRC`: http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html
-
-_`Rally installation procedure`: https://rally.readthedocs.org/en/latest/tutorial/step_0_installation.html
-
-_`config_functest.yaml` : https://git.opnfv.org/cgit/functest/tree/functest/ci/config_functest.yaml