Background\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 it to all existing and new test suites and test\r
-cases.\r
-\r
-The new naming should be intuitive for majority of the tests. Complete\r
-description of the newly adopted CSIT test naming convention is provided on\r
-`CSIT test naming page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_. Here\r
-few illustrative examples of the new naming usage for test suites across CSIT\r
+CSIT |release| follows a common structured naming convention for all\r
+performance and system functional tests, introduced in CSIT rls1701.\r
+\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>`_. Below\r
+few illustrative examples of the naming usage for test suites across CSIT\r
performance, functional and HoneyComb management test areas.\r
\r
Naming Convention\r
sub-interface events with HoneyComb NetConf Notifications, functional tests.\r
\r
For complete description of CSIT test naming convention please refer to `CSIT\r
-test naming page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
+test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.\r
Code Review / csit.git / blobdiff