+---------------> <--------------+\r
| | | | | |\r
| |------------> DUT1 <-----------+ |\r
- | | | +--^--^------------+ | | |\r
+ | | | +------------------+ | | |\r
| | | | | |\r
| | | SUT1 | | |\r
| | +------------------------+ | |\r
Functional Tests Naming\r
-----------------------\r
\r
-CSIT |release| introduced a common structured naming convention for all\r
-performance and functional tests. This change was driven by substantially\r
-growing number and type of CSIT test cases. Firstly, the original practice did\r
-not always follow any strict naming convention. Secondly test names did not\r
-always clearly capture tested packet encapsulations, and the actual type or\r
-content of the tests. Thirdly HW configurations in terms of NICs, ports and\r
-their locality were not captured either. These were but few reasons that drove\r
-the decision to change and define a new more complete and stricter test naming\r
-convention, and to apply this to all existing and new test cases.\r
-\r
-The new naming should be intuitive for majority of the tests. The complete\r
+CSIT |release| follows a common structured naming convention for all\r
+performance and system functional tests, introduced in CSIT |release-1|.\r
+\r
+The naming should be intuitive for majority of the tests. Complete\r
description of CSIT test naming convention is provided on `CSIT test naming\r
page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
\r