aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCédric Ollivier <cedric.ollivier@orange.com>2019-10-13 15:32:08 +0200
committerCédric Ollivier <cedric.ollivier@orange.com>2019-10-13 15:32:08 +0200
commitda2260251a5de3ee0d8fcc345fea3d9eb97ebeb2 (patch)
treeb7e44883492f62cb0e524afcfa966c58a55b1357
parent37251af62ca89b55f09dfd6ddce15ee179c580f3 (diff)
Update python dirs in docs
master is now leveraging on python3.7. Change-Id: I7076e143f162a6aacd2e8d8d8f38524aea71e365 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
-rw-r--r--docs/testing/user/configguide/configguide.rst6
-rw-r--r--docs/testing/user/userguide/test_results.rst2
-rw-r--r--docs/testing/user/userguide/troubleshooting.rst14
3 files changed, 11 insertions, 11 deletions
diff --git a/docs/testing/user/configguide/configguide.rst b/docs/testing/user/configguide/configguide.rst
index 25aa7cd26..88f728cb0 100644
--- a/docs/testing/user/configguide/configguide.rst
+++ b/docs/testing/user/configguide/configguide.rst
@@ -353,7 +353,7 @@ By default all the logs are put un /home/opnfv/functest/results/functest.log.
If you want to have more logs in console, you may edit the logging.ini file
manually.
Connect on the docker then edit the file located in
-/usr/lib/python3.6/site-packages/xtesting/ci/logging.ini
+/usr/lib/python3.7/site-packages/xtesting/ci/logging.ini
Change wconsole to console in the desired module to get more traces.
@@ -363,8 +363,8 @@ Configuration
You may also directly modify the python code or the configuration file (e.g.
testcases.yaml used to declare test constraints) under
-/usr/lib/python3.6/site-packages/xtesting and
-/usr/lib/python3.6/site-packages/functest
+/usr/lib/python3.7/site-packages/xtesting and
+/usr/lib/python3.7/site-packages/functest
Tips
diff --git a/docs/testing/user/userguide/test_results.rst b/docs/testing/user/userguide/test_results.rst
index 511b0b4cb..a1d4dfb59 100644
--- a/docs/testing/user/userguide/test_results.rst
+++ b/docs/testing/user/userguide/test_results.rst
@@ -10,7 +10,7 @@ In manual mode test results are displayed in the console and result files
are put in /home/opnfv/functest/results.
If you want additional logs, you may configure the logging.ini under
-/usr/lib/python3.6/site-packages/xtesting/ci.
+/usr/lib/python3.7/site-packages/xtesting/ci.
Automated testing
-----------------
diff --git a/docs/testing/user/userguide/troubleshooting.rst b/docs/testing/user/userguide/troubleshooting.rst
index 279a47398..fb534376d 100644
--- a/docs/testing/user/userguide/troubleshooting.rst
+++ b/docs/testing/user/userguide/troubleshooting.rst
@@ -44,8 +44,8 @@ follows::
The Functest CLI is designed to route a call to the corresponding internal
python scripts, located in paths::
- /usr/lib/python3.6/site-packages/functest/opnfv_tests/openstack/vping/vping_ssh.py
- /usr/lib/python3.6/site-packages/functest/opnfv_tests/openstack/vping/vping_userdata.py
+ /usr/lib/python3.7/site-packages/functest/opnfv_tests/openstack/vping/vping_ssh.py
+ /usr/lib/python3.7/site-packages/functest/opnfv_tests/openstack/vping/vping_userdata.py
Notes:
@@ -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
-/usr/lib/python3.6/site-packages/functest/opnfv_tests/openstack/vping/ping.sh
+/usr/lib/python3.7/site-packages/functest/opnfv_tests/openstack/vping/ping.sh
and takes an IP as a parameter. When the SCP is completed, the test will do a
SSH call to that script inside the second instance. Some problems can happen
here::
@@ -278,7 +278,7 @@ To enable that, add a new entry in docker/smoke/testcases.yaml on the
Also, a list of the Tempest test cases must be provided to the container or
modify the existing one in
-/usr/lib/python3.6/site-packages/functest/opnfv_tests/openstack/tempest/custom_tests/test_list.txt
+/usr/lib/python3.7/site-packages/functest/opnfv_tests/openstack/tempest/custom_tests/test_list.txt
Example of custom list of tests 'my-custom-tempest-tests.txt'::
@@ -290,8 +290,8 @@ This is an example of running a customized list of Tempest tests in Functest::
sudo docker run --env-file env \
-v $(pwd)/openstack.creds:/home/opnfv/functest/conf/env_file \
-v $(pwd)/images:/home/opnfv/functest/images \
- -v $(pwd)/my-custom-testcases.yaml:/usr/lib/python3.6/site-packages/functest/ci/testcases.yaml \
- -v $(pwd)/my-custom-tempest-tests.txt:/usr/lib/python3.6/site-packages/functest/opnfv_tests/openstack/tempest/custom_tests/test_list.txt \
+ -v $(pwd)/my-custom-testcases.yaml:/usr/lib/python3.7/site-packages/functest/ci/testcases.yaml \
+ -v $(pwd)/my-custom-tempest-tests.txt:/usr/lib/python3.7/site-packages/functest/opnfv_tests/openstack/tempest/custom_tests/test_list.txt \
opnfv/functest-smoke run_tests -t tempest_custom
@@ -314,7 +314,7 @@ Possible scenarios are:
To know more about what those scenarios are doing, they are defined in
directory:
-/usr/lib/python3.6/site-packages/functest/opnfv_tests/openstack/rally/scenario
+/usr/lib/python3.7/site-packages/functest/opnfv_tests/openstack/rally/scenario
For more info about Rally scenario definition please refer to the Rally
official documentation. `[3]`_