aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/honeycomb_functional_tests/overview.rst
diff options
context:
space:
mode:
authorTibor Frank <tifrank@cisco.com>2018-07-27 13:59:21 +0200
committerTibor Frank <tifrank@cisco.com>2018-07-27 15:02:50 +0200
commitc7b2541ae5ff737691547daef2e4b25f9d232eba (patch)
treecbb8b07192044d5671d6d21d279b2a3af9d7d3ba /docs/report/honeycomb_functional_tests/overview.rst
parentdd1a88208be79852a99dc673411fe1ab0760a051 (diff)
CSIT-1213: Add 2n/3n-skx to Test Oper Data
Change-Id: I217cc8dc6691c2a443460bd4e51ea96c4ec82806 Signed-off-by: Tibor Frank <tifrank@cisco.com>
Diffstat (limited to 'docs/report/honeycomb_functional_tests/overview.rst')
-rw-r--r--docs/report/honeycomb_functional_tests/overview.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/report/honeycomb_functional_tests/overview.rst b/docs/report/honeycomb_functional_tests/overview.rst
index 741c2dd5e7..9100ed6e2c 100644
--- a/docs/report/honeycomb_functional_tests/overview.rst
+++ b/docs/report/honeycomb_functional_tests/overview.rst
@@ -46,7 +46,7 @@ for clarity).
Functional Tests Coverage
-------------------------
-The following Honeycomb functional test areas are included in the CSIT |release|
+The following Honeycomb functional test areas are included in the |csit-release|
with results listed in this report:
- **Basic interface management** - CRUD for interface state,
@@ -161,7 +161,7 @@ with results listed in this report:
- Netconf/Restconf northbound over IPv6
- Test case count: 12
-Total 219 Honeycomb functional tests in the CSIT |release|.
+Total 219 Honeycomb functional tests in the |csit-release|.
Operational data in Honeycomb should mirror configuration data at all times.
Because of this, test cases follow this general pattern:
@@ -179,7 +179,7 @@ the DUT node.
Functional Tests Naming
-----------------------
-CSIT |release| introduced a common structured naming convention for all
+|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