CSIT-1197: Add Comparison Across Testbeds to the Report

[csit.git] / docs / report / honeycomb_functional_tests / overview.rst

diff --git a/docs/report/honeycomb_functional_tests/overview.rst b/docs/report/honeycomb_functional_tests/overview.rst
index 493499a..f67f735 100644 (file)
--- 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,
@@ -154,13 +154,14 @@ with results listed in this report:
 - **Border Gateway Protocol** - CRUD and functional tests for BGP.
   - Configure peers and routes
   - Check interactions with another BGP peer.
-  - Test case count: 9
+  - Test case count: 13
 - **Honeycomb Infractructure** - configuration persistence,
   - Netconf notifications for interface events,
   - Netconf negative tests aimed at specific issues
   - Netconf/Restconf northbound over IPv6
+  - Test case count: 12
 
-Total 217 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:
@@ -178,7 +179,7 @@ the DUT node.
 Functional Tests Naming
 -----------------------
 
-CSIT |release| introduced a common structured naming convention for all
+CSIT-17.01 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