Change-Id: I0c27300678414bd3baecccd8e51ca0dc15af73d5
Signed-off-by: Peter Mikus <pmikus@cisco.com>
----------
CSIT |release| follows a common structured naming convention for all
----------
CSIT |release| follows a common structured naming convention for all
-performance and system functional tests, introduced in CSIT |release-1|.
+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
The naming should be intuitive for majority of the tests. Complete
description of CSIT test naming convention is provided on
------------------------
CSIT |release| follows a common structured naming convention for all performance
------------------------
CSIT |release| follows a common structured naming convention for all performance
-and system functional tests, introduced in CSIT |release-1|.
+and system functional tests, introduced in CSIT rls1701.
The naming should be intuitive for majority of the tests. Complete description
The naming should be intuitive for majority of the tests. Complete description
-of CSIT test naming convention is provided on `CSIT test naming wiki
-<https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
+of CSIT test naming convention is provided on :ref:`csit_test_naming`.
Methodology: Multi-Core and Multi-Threading
-------------------------------------------
Methodology: Multi-Core and Multi-Threading
-------------------------------------------
Functional Tests Naming\r
-----------------------\r
\r
Functional Tests Naming\r
-----------------------\r
\r
-CSIT |release| follows a common structured naming convention for all\r
-performance and system functional tests, introduced in CSIT |release-1|.\r
+CSIT |release| follows a common structured naming convention for all performance\r
+and system functional tests, introduced in CSIT rls1701.\r
-The naming should be intuitive for majority of the tests. Complete\r
-description of CSIT test naming convention is provided on\r
-`CSIT test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
+The naming should be intuitive for majority of the tests. Complete description\r
+of CSIT test naming convention is provided on :ref:`csit_test_naming`..\r
\r
Here few illustrative examples of the new naming usage for functional test\r
suites:\r
\r
Here few illustrative examples of the new naming usage for functional test\r
suites:\r
| 4 | IPSec (software, no QAT HW) throughput | CSIT-1064 | IPSec throughput regression: NDR -3%..-8%, PDR -2%..-8%, MRR |\r
| | regression. | | -3%..-7%. Affects IPSec SW tests, QAT HW tests not affected. |\r
+---+-------------------------------------------------+------------+-----------------------------------------------------------------+\r
| 4 | IPSec (software, no QAT HW) throughput | CSIT-1064 | IPSec throughput regression: NDR -3%..-8%, PDR -2%..-8%, MRR |\r
| | regression. | | -3%..-7%. Affects IPSec SW tests, QAT HW tests not affected. |\r
+---+-------------------------------------------------+------------+-----------------------------------------------------------------+\r
-| 5 | High failure rate of creating working container | CSIT-1065 | Orchestrated container topology tests failing data plane |\r
-| | topologies with K8s/Ligato orchestration. | | verification indicating configuration issue. Suspected issue |\r
-| | | | with Ligato vpp-agent. |\r
+| 5 | High failure rate of creating working container | CSIT-1065 | About 20% of orchestrated container topology tests failing data |\r
+| | topologies with K8s/Ligato orchestration. | | plane verification indicating configuration issue. Suspected |\r
+| | | | issue with Ligato vpp-agent. |\r
+---+-------------------------------------------------+------------+-----------------------------------------------------------------+\r
+---+-------------------------------------------------+------------+-----------------------------------------------------------------+\r
------------------------
CSIT |release| follows a common structured naming convention for all performance
------------------------
CSIT |release| follows a common structured naming convention for all performance
-and system functional tests, introduced in CSIT |release-1|.
+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 :ref:`csit_test_naming`.
The naming should be intuitive for majority of the tests. Complete description
of CSIT test naming convention is provided on :ref:`csit_test_naming`.