diff options
| author |   Maciek Konstantynowicz <mkonstan@cisco.com> | 2017-04-20 22:42:01 +0100 |
|---|---|---|
| committer |   Peter Mikus <pmikus@cisco.com> | 2017-04-21 12:28:05 +0000 |
| commit | 182e755776923c81b2e2138125728b592dabe27b (patch) | |
| tree | 03ea3e56470a76f58b45b86489f8fa4ca1441b32 /docs/report/vpp_functional_tests/overview.rst | |
| parent | aef6be686bfb1cdbf85d1fca0e5d28e43650ec0d (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>
(cherry picked from commit 5d294b7d4c501d971d67c4e3fe192a9dc504d76e)
Diffstat (limited to 'docs/report/vpp_functional_tests/overview.rst')
| -rw-r--r-- | docs/report/vpp_functional_tests/overview.rst | 17 |
1 files changed, 5 insertions, 12 deletions
diff --git a/docs/report/vpp_functional_tests/overview.rst b/docs/report/vpp_functional_tests/overview.rst index e85bb92f7b..0fa15a5472 100644 --- a/docs/report/vpp_functional_tests/overview.rst +++ b/docs/report/vpp_functional_tests/overview.rst @@ -38,7 +38,7 @@ Both logical test topologies are shown in the figures below. +---------------> <--------------+
| | | | | |
| |------------> DUT1 <-----------+ |
- | | | +--^--^------------+ | | |
+ | | | +------------------+ | | |
| | | | | |
| | | SUT1 | | |
| | +------------------------+ | |
@@ -131,17 +131,10 @@ results listed in this report: Functional Tests Naming
-----------------------
-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 this to all existing and new test cases.
-
-The new naming should be intuitive for majority of the tests. The complete
+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
page <https://wiki.fd.io/view/CSIT/csit-test-naming>`_.
|