aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/introduction/csit_test_naming.rst
diff options
context:
space:
mode:
authorMaciek Konstantynowicz <mkonstan@cisco.com>2017-04-20 22:42:01 +0100
committerPeter Mikus <pmikus@cisco.com>2017-04-21 12:27:38 +0000
commit5d294b7d4c501d971d67c4e3fe192a9dc504d76e (patch)
tree62602fa98b43a4a42d8a65fbffeb1d5f7d0b17fa /docs/report/introduction/csit_test_naming.rst
parent2c1706d69455d8479b0b0318d4c2fa8b4ab806cb (diff)
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>
Diffstat (limited to 'docs/report/introduction/csit_test_naming.rst')
-rw-r--r--docs/report/introduction/csit_test_naming.rst24
1 files changed, 8 insertions, 16 deletions
diff --git a/docs/report/introduction/csit_test_naming.rst b/docs/report/introduction/csit_test_naming.rst
index 0415e5c5d6..a4de765e0a 100644
--- a/docs/report/introduction/csit_test_naming.rst
+++ b/docs/report/introduction/csit_test_naming.rst
@@ -4,21 +4,13 @@ CSIT Test Naming
Background
----------
-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 it to all existing and new test suites and test
-cases.
-
-The new naming should be intuitive for majority of the tests. Complete
-description of the newly adopted CSIT test naming convention is provided on
-`CSIT test naming page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_. Here
-few illustrative examples of the new naming usage for test suites across CSIT
+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 wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_. Below
+few illustrative examples of the naming usage for test suites across CSIT
performance, functional and HoneyComb management test areas.
Naming Convention
@@ -123,4 +115,4 @@ topologies:
sub-interface events with HoneyComb NetConf Notifications, functional tests.
For complete description of CSIT test naming convention please refer to `CSIT
-test naming page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
+test naming wiki page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.