Add a key benefits section in Release Notes

It also precises the side effects if test cases are in failure.

Change-Id: Id4a2a3428da33deed51415fce5d98b81e64d35fe
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
(cherry picked from commit 23adae76dc5c3132b5ad2336b7bc3b855f725d9f)

diff --git a/docs/release/release-notes/fuel_amd64.rst b/docs/release/release-notes/fuel_amd64.rst
index 6c8b488..39f281c 100644 (file)
--- a/docs/release/release-notes/fuel_amd64.rst
+++ b/docs/release/release-notes/fuel_amd64.rst
@@ -7,20 +7,20 @@ os-nosdn-nofeature-ha
 ====================  ===================  ==========  ========  ========
 testcase              date                 pod_name    result    jira
 ====================  ===================  ==========  ========  ========
-connection_check      2018-04-07 22:08:05  lf-pod2     PASS
-api_check             2018-04-07 22:19:50  lf-pod2     PASS
-snaps_health_check    2018-04-07 22:20:38  lf-pod2     PASS
-vping_ssh             2018-04-07 22:21:45  lf-pod2     PASS
-vping_userdata        2018-04-07 22:22:57  lf-pod2     PASS
-tempest_smoke_serial  2018-04-07 22:42:15  lf-pod2     PASS
-rally_sanity          2018-04-07 23:13:04  lf-pod2     PASS
-refstack_defcore      2018-04-07 23:19:35  lf-pod2     PASS
-patrole               2018-04-07 23:25:04  lf-pod2     PASS
-snaps_smoke           2018-04-08 00:31:06  lf-pod2     FAIL      FUEL-356
-neutron_trunk         2018-04-08 00:34:04  lf-pod2     PASS
-cloudify_ims          2018-04-08 00:51:42  lf-pod2     FAIL
-vyos_vrouter          2018-04-08 01:09:38  lf-pod2     FAIL
-juju_epc              2018-04-08 01:18:36  lf-pod2     FAIL
+connection_check      2018-04-08 22:25:51  lf-pod2     PASS
+api_check             2018-04-08 22:37:50  lf-pod2     PASS
+snaps_health_check    2018-04-08 22:38:39  lf-pod2     PASS
+vping_ssh             2018-04-08 22:39:46  lf-pod2     PASS
+vping_userdata        2018-04-08 22:41:03  lf-pod2     PASS
+tempest_smoke_serial  2018-04-08 23:00:26  lf-pod2     PASS
+rally_sanity          2018-04-08 23:31:15  lf-pod2     PASS
+refstack_defcore      2018-04-08 23:35:19  lf-pod2     PASS
+patrole               2018-04-08 23:40:12  lf-pod2     PASS
+snaps_smoke           2018-04-09 00:46:28  lf-pod2     FAIL      FUEL-356
+neutron_trunk         2018-04-09 00:49:24  lf-pod2     PASS
+cloudify_ims          2018-04-09 01:07:03  lf-pod2     FAIL
+vyos_vrouter          2018-04-09 01:24:45  lf-pod2     FAIL
+juju_epc              2018-04-09 01:33:37  lf-pod2     FAIL
 ====================  ===================  ==========  ========  ========
 
 os-odl-nofeature-ha

diff --git a/docs/release/release-notes/functest-gating.rst b/docs/release/release-notes/functest-gating.rst
index eb9bc6b..0aac41b 100644 (file)
--- a/docs/release/release-notes/functest-gating.rst
+++ b/docs/release/release-notes/functest-gating.rst
@@ -3,9 +3,17 @@
 Release Gating
 ==============
 
-Regarding the offical OPNFV results and local tests (see
+Thanks to the analysis of the offical OPNFV results and local tests (see
 `Orange ONAP Openlab`_), Functest is trustable for verifying all OPNFV Fraser
-installers and more generally classical OpenStack Pike deployments.
+installers and more generally classical OpenStack Pike and Kubernetes
+deployments.
+
+It should be noted that:
+
+  * any failed result highlights side effects for end users
+  * OpenStack scenarios which don't pass tempest_smoke_serial break the
+    upstream rules (and then decrease the overall quality) as all patches are
+    tested vs tempest in OpenStack gating
 
 .. _`Orange ONAP Openlab`: https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751
 

diff --git a/docs/release/release-notes/functest-release.rst b/docs/release/release-notes/functest-release.rst
index d436e45..0701fcf 100644 (file)
--- a/docs/release/release-notes/functest-release.rst
+++ b/docs/release/release-notes/functest-release.rst
@@ -134,6 +134,20 @@ Key changes
 .. _`OpenStack Pike`: https://raw.githubusercontent.com/openstack/requirements/stable/pike/upper-constraints.txt
 .. _Xtesting: http://xtesting.readthedocs.io/en/latest/
 
+Key benefits
+------------
+
+ * the enduser can run all tests by setting only one input (EXTERNAL_NETWORK)
+ * the developer can only work on the test suites without diving into CI/CD
+   integration
+ * both OpenStack and Kubernetes deployments can be verified
+ * Functest test cases are trustable as they meet the best coding rules (unit
+   tests, coverage, linters, etc.)
+ * Functest can be reused in other projects (e.g.
+   `ONS: Re-using OPNFV framework tests for LFN projects`_)
+
+.. _`ONS: Re-using OPNFV framework tests for LFN projects`: https://wiki.lfnetworking.org/display/LN/LFN+Developer+Forum+Schedule?preview=/328197/328329/ONS-OPNFV%20framework%20tests%20for%20LFN%20projects.pdf
+
 Code quality
 ------------