From 182e755776923c81b2e2138125728b592dabe27b Mon Sep 17 00:00:00 2001 From: Maciek Konstantynowicz Date: Thu, 20 Apr 2017 22:42:01 +0100 Subject: 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 (cherry picked from commit 5d294b7d4c501d971d67c4e3fe192a9dc504d76e) --- docs/report/introduction/csit_test_naming.rst | 24 ++++++++---------------- 1 file changed, 8 insertions(+), 16 deletions(-) (limited to 'docs/report/introduction/csit_test_naming.rst') 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 `_. 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 `_. 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 `_. +test naming wiki page `_. -- cgit 1.2.3-korg