From c348fa9a9dcd8fd4fb4d83b36d441e3c949af390 Mon Sep 17 00:00:00 2001 From: Morgan Richomme Date: Thu, 4 Feb 2016 18:34:36 +0100 Subject: update user guide - change vIMS logs - add Promise logs - modify section on OpenStack audit (now dynamic) - minor reformating of tables - typos - add troubleshooting section on vPing and vPing_userdata JIRA: FUNCTEST-113 Change-Id: Ib29c4d5e2c4f10f64de764491fc536495b39ea3d Signed-off-by: Morgan Richomme --- docs/userguide/runfunctest.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'docs/userguide/runfunctest.rst') diff --git a/docs/userguide/runfunctest.rst b/docs/userguide/runfunctest.rst index 8125e814..b186e539 100644 --- a/docs/userguide/runfunctest.rst +++ b/docs/userguide/runfunctest.rst @@ -128,13 +128,15 @@ The order of execution is also described in the Functest configuration file:: 12: vims 13: rally -The tests are executed as follow: +The tests are executed in the following order: * Basic scenario (vPing, vPing_userdata, Tempest) * Controller suites: ODL or ONOS or OpenContrail - * Feature projects - * vIMS + * Feature projects (promise, vIMS) * Rally (benchmark scenario) At the end of an automated execution, everything is cleaned. -We keep only the users/networks that have been statically declared in 'https://git.opnfv.org/cgit/functest/tree/testcases/VIM/OpenStack/CI/libraries/os_defaults.yaml'_ +Before running Functest, a snapshot of the OpenStack configuration (users, +tenants, networks, ....) is performed. After Functest, a clean mechanism is +launched to delete everything that would not have been properly deleted in order +to restitute the system as it was prior to the tests. -- cgit 1.2.3-korg