diff options
| author |   jose.lausuch <jose.lausuch@ericsson.com> | 2016-02-10 14:38:08 +0100 |
|---|---|---|
| committer | jose.lausuch <jose.lausuch@ericsson.com> | 2016-02-10 17:01:27 +0100 |
| commit | efa03f2d578fbbf377d73e7a50d446d9cfb7714c (patch) | |
| tree | 120163151cb928d2f36379149f4284170033e677 /docs/userguide | |
| parent | 11abc6e4d60d7c391965e20f81dbc10d7ae5fae6 (diff) | |
Rename the vPing scripts proplery and adapt documentation
Change-Id: Idb498eb7cefd938006661f42f1bf1772395d9d47
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
Diffstat (limited to 'docs/userguide')
| -rw-r--r-- | docs/userguide/index.rst | 12 | ||||
| -rw-r--r-- | docs/userguide/runfunctest.rst | 7 |
2 files changed, 10 insertions, 9 deletions
diff --git a/docs/userguide/index.rst b/docs/userguide/index.rst index 89e3ef115..b33b3120c 100644 --- a/docs/userguide/index.rst +++ b/docs/userguide/index.rst @@ -24,8 +24,8 @@ The different scenarios are described in the section hereafter. VIM (Virtualized Infrastructure Manager) --- -vPing -^^^^^ +vPing_SSH +^^^^^^^^^ Given the script 'ping.sh':: @@ -371,8 +371,8 @@ Test results VIM --- -vPing -^^^^^ +vPing_SSH +^^^^^^^^^ vPing test case output is displayed in the console:: @@ -726,8 +726,8 @@ Troubleshooting VIM --- -vPing -^^^^^ +vPing_SSH +^^^^^^^^^ vPing should work on all the scenarios. In case of timeout, check your network connectivity. The test case creates its own security group to allow SSH access, diff --git a/docs/userguide/runfunctest.rst b/docs/userguide/runfunctest.rst index 94e11a63a..61511413c 100644 --- a/docs/userguide/runfunctest.rst +++ b/docs/userguide/runfunctest.rst @@ -27,7 +27,8 @@ several options:: -r|--report push results to database (false by default) -n|--no-clean do not clean up OpenStack resources after test run -t|--test run specific set of tests - <test_name> one or more of the following: vping,vping_userdata,odl,rally,tempest,vims,onos,promise. Separated by comma. + <test_name> one or more of the following separated by comma: + vping_ssh,vping_userdata,odl,rally,tempest,vims,onos,promise,ovno examples: run_tests.sh @@ -140,7 +141,7 @@ The order of execution is also described in the Functest configuration file:: test_exec_priority: - 1: vping + 1: vping_ssh 2: vping_userdata 3: tempest 4: odl @@ -156,7 +157,7 @@ The order of execution is also described in the Functest configuration file:: The tests are executed in the following order: - * Basic scenario (vPing, vPing_userdata, Tempest) + * Basic scenario (vPing_ssh, vPing_userdata, Tempest) * Controller suites: ODL or ONOS or OpenContrail * Feature projects (promise, vIMS) * Rally (benchmark scenario) |