From 35ac362d7ba35413493b165808362e1169f9f240 Mon Sep 17 00:00:00 2001 From: Peter Mikus Date: Mon, 7 May 2018 13:38:29 +0200 Subject: FIX: Small inconsistencies in report sections Change-Id: I0c27300678414bd3baecccd8e51ca0dc15af73d5 Signed-off-by: Peter Mikus --- docs/report/vpp_functional_tests/overview.rst | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 'docs/report/vpp_functional_tests') diff --git a/docs/report/vpp_functional_tests/overview.rst b/docs/report/vpp_functional_tests/overview.rst index fda35072ef..1cd5def87d 100644 --- a/docs/report/vpp_functional_tests/overview.rst +++ b/docs/report/vpp_functional_tests/overview.rst @@ -127,12 +127,11 @@ results listed in this report: Functional Tests Naming ----------------------- -CSIT |release| follows a common structured naming convention for all -performance and system functional tests, introduced in CSIT |release-1|. +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 `_. +The naming should be intuitive for majority of the tests. Complete description +of CSIT test naming convention is provided on :ref:`csit_test_naming`.. Here few illustrative examples of the new naming usage for functional test suites: -- cgit 1.2.3-korg