From 3e3c96b2aa15d7757f281ce00518a67e2a1225a9 Mon Sep 17 00:00:00 2001 From: helenyao Date: Mon, 21 Nov 2016 06:50:06 -0500 Subject: Extracted all global parameters into functest_constants.py JIRA: FUNCTEST-533 1. Extracted all global variables into functest_constants.py and updated all affected areas accordingly 2. Used os.path.join to replace '/' to come up with the path for better cross-platform support and improve the path accuracy 3. Removed unused variables 4. Updated the hardcoded path in Dockerfile by using variable reference 5. Removed "/" ending from all path variables 6. Updated the unit test Change-Id: Ib30a81d1f0c83fbaef042d63c187c27bd18301bb Signed-off-by: helenyao --- docs/userguide/troubleshooting.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/userguide/troubleshooting.rst') diff --git a/docs/userguide/troubleshooting.rst b/docs/userguide/troubleshooting.rst index dbbcc5d6..bf94935e 100644 --- a/docs/userguide/troubleshooting.rst +++ b/docs/userguide/troubleshooting.rst @@ -44,8 +44,8 @@ These test cases can be run inside the container, using new Functest CLI as foll The Functest CLI is designed to route a call to the corresponding internal python scripts, located in paths: -*$repos_dir/functest/testcases/vPing/CI/libraries/vPing_ssh.py* and -*$repos_dir/functest/testcases/vPing/CI/libraries/vPing_userdata.py* +*$REPOS_DIR/functest/functest/opnfv_tests/vPing/CI/libraries/vPing_ssh.py* and +*$REPOS_DIR/functest/functest/opnfv_tests/vPing/CI/libraries/vPing_userdata.py* Notes: #. In this Colorado Funtest Userguide, the use of the Functest CLI is @@ -125,7 +125,7 @@ This test case creates a floating IP on the external network and assigns it to the second instance **opnfv-vping-2**. The purpose of this is to establish a SSH connection to that instance and SCP a script that will ping the first instance. This script is located in the repository under -*$repos_dir/functest/testcases/OpenStack/vPing/ping.sh* and takes an IP as +*$REPOS_DIR/functest/functest/opnfv_tests/OpenStack/vPing/ping.sh* and takes an IP as a parameter. When the SCP is completed, the test will do an SSH call to that script inside the second instance. Some problems can happen here:: @@ -263,7 +263,7 @@ lead to errors in Rally as well. It is possible to run only one Rally scenario, instead of the whole suite. To do that, call the alternative python script as follows:: - python $repos_dir/functest/testcases/OpenStack/rally/run_rally-cert.py -h + python $REPOS_DIR/functest/functest/opnfv_tests/OpenStack/rally/run_rally-cert.py -h usage: run_rally-cert.py [-h] [-d] [-r] [-s] [-v] [-n] test_name positional arguments: @@ -282,7 +282,7 @@ To do that, call the alternative python script as follows:: For example, to run the Glance scenario with debug information:: - python $repos_dir/functest/testcases/OpenStack/rally/run_rally-cert.py -d glance + python $REPOS_DIR/functest/functest/opnfv_tests/OpenStack/rally/run_rally-cert.py -d glance Possible scenarios are: * authenticate @@ -297,7 +297,7 @@ Possible scenarios are: * vm To know more about what those scenarios are doing, they are defined in directory: -*$repos_dir/functest/testcases/OpenStack/rally/scenario* +*$REPOS_DIR/functest/functest/opnfv_tests/OpenStack/rally/scenario* For more info about Rally scenario definition please refer to the Rally official documentation. `[3]`_ -- cgit 1.2.3-korg