From 10649b3ce07bbb3144d196c403d8c1fa65ddf116 Mon Sep 17 00:00:00 2001 From: Peter Mikus Date: Mon, 22 May 2017 09:35:17 +0200 Subject: CSIT-612 Report: Minimization of hand-crafted content. - replace dynamic text content and links by variables. Change-Id: I1a7ec371fc80af3c9dd416bf91dd2c639097cf1e Signed-off-by: Peter Mikus --- docs/report/introduction/csit_test_naming.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/report/introduction/csit_test_naming.rst') diff --git a/docs/report/introduction/csit_test_naming.rst b/docs/report/introduction/csit_test_naming.rst index a4de765e0a..682fcd941a 100644 --- a/docs/report/introduction/csit_test_naming.rst +++ b/docs/report/introduction/csit_test_naming.rst @@ -5,12 +5,12 @@ Background ---------- CSIT |release| follows a common structured naming convention for all -performance and system functional tests, introduced in CSIT rls1701. +performance and system functional tests, introduced in CSIT |release-1|. 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 `_. Below -few illustrative examples of the naming usage for test suites across CSIT +`CSIT test naming wiki page `_. +Below few illustrative examples of the naming usage for test suites across CSIT performance, functional and HoneyComb management test areas. Naming Convention -- cgit 1.2.3-korg