CSIT rls1704 report - update to handcraftec sections:

- introduction /overview /general_notes /csit_test_naming
- vpp_performance_tests /overview /csit_release_notes /test_environment /documentation /xx_graphs
- vpp_functional_tests /overview /csit_release_notes /documentation
- testpmd_performance_tests /overview /csit_release_notes /test_environment /documentation /xx_graphs

Change-Id: I10593d4155edc663ca07ae5cd29eb679c5f5d85f
Signed-off-by: Maciek Konstantynowicz <mkonstan@cisco.com>

3 files changed, 7 insertions, 36 deletions

diff --git a/docs/report/vpp_functional_tests/csit_release_notes.rst b/docs/report/vpp_functional_tests/csit_release_notes.rst
index 6db4900046..c87cb46e3c 100644
--- a/docs/report/vpp_functional_tests/csit_release_notes.rst
+++ b/docs/report/vpp_functional_tests/csit_release_notes.rst
@@ -1,24 +1,10 @@
-
-.. |br| raw:: html
-
-    <br />
-
 CSIT Release Notes
 ==================
 
 Changes in CSIT |release|
 -------------------------
 
-#. Naming change for all VPP functional test suites in VIRL
-
-    - VPP functional test case names stayed unchanged
-
-#. VPP functional test environment changes
-
-    - upgrade to Ubuntu 16.04
-    - VM and vhost-user test environment optimizations
-
-#. Introduction of Centos tests
+#. Introduction of Centos7 tests
 
 #. Added VPP functional tests
 
@@ -66,11 +52,3 @@ Here is the list of known issues in CSIT |release| for VPP functional tests in V
 |   |                                                 | The (Rx) traffic is mirrored to correct destination port.       |
 +---+-------------------------------------------------+-----------------------------------------------------------------+
 
-Tests to be Added - Centos
---------------------------
-
-CSIT |release| added Centos functional test execution environment in FD.io
-VIRL testbeds.However due to the factors beyond CSIT project control execution
-of those tests within the LF FD.io test environment still need to complete.
-Once the results become available, they will be published as an addendum to
-the current version of CSIT |release| report.
diff --git a/docs/report/vpp_functional_tests/documentation.rst b/docs/report/vpp_functional_tests/documentation.rst
index e286e6cf19..d34877b0b3 100644
--- a/docs/report/vpp_functional_tests/documentation.rst
+++ b/docs/report/vpp_functional_tests/documentation.rst
@@ -2,6 +2,6 @@ Documentation
 =============

 

 `CSIT VPP Functional Tests Documentation

-<https://docs.fd.io/csit/master/doc/tests.func.html>`_ contains detailed

+<https://docs.fd.io/csit/rls1704/doc/tests.func.html>`_ contains detailed

 functional description and input parameters for each test case.

 

diff --git a/docs/report/vpp_functional_tests/overview.rst b/docs/report/vpp_functional_tests/overview.rst
index e85bb92f7b..0fa15a5472 100644
--- a/docs/report/vpp_functional_tests/overview.rst
+++ b/docs/report/vpp_functional_tests/overview.rst
@@ -38,7 +38,7 @@ Both logical test topologies are shown in the figures below.
           +--------------->                  <--------------+

           |            |  |                  |  |           |

           |  |------------>       DUT1       <-----------+  |

-          |  |         |  +--^--^------------+  |        |  |

+          |  |         |  +------------------+  |        |  |

           |  |         |                        |        |  |

           |  |         |                  SUT1  |        |  |

           |  |         +------------------------+        |  |

@@ -131,17 +131,10 @@ results listed in this report:
 Functional Tests Naming

 -----------------------

 

-CSIT |release| introduced a common structured naming convention for all

-performance and functional tests. This change was driven by substantially

-growing number and type of CSIT test cases. Firstly, the original practice did

-not always follow any strict naming convention. Secondly test names did not

-always clearly capture tested packet encapsulations, and the actual type or

-content of the tests. Thirdly HW configurations in terms of NICs, ports and

-their locality were not captured either. These were but few reasons that drove

-the decision to change and define a new more complete and stricter test naming

-convention, and to apply this to all existing and new test cases.

-

-The new naming should be intuitive for majority of the tests. The complete

+CSIT |release| follows a common structured naming convention for all

+performance and system functional tests, introduced in CSIT rls1701.

+

+The naming should be intuitive for majority of the tests. Complete

 description of CSIT test naming convention is provided on `CSIT test naming

 page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.