From f108ea3ed6501aca2583026056bc98cc9a2a0fbd Mon Sep 17 00:00:00 2001 From: Morgan Richomme Date: Mon, 24 Aug 2015 09:34:55 +0200 Subject: README for vIMS testcase Note that vIMS shall be also documented in the global functest rst guideline. JIRA: FUNCTEST-38 Change-Id: Ifebcbcdad5231283afd8ad721daa60fa13ced15e Signed-off-by: Morgan Richomme --- commons/traffic-profile-guidelines.rst | 10 +++++++--- testcases/vIMS/vIMS.md | 3 +++ 2 files changed, 10 insertions(+), 3 deletions(-) create mode 100644 testcases/vIMS/vIMS.md diff --git a/commons/traffic-profile-guidelines.rst b/commons/traffic-profile-guidelines.rst index ffef50fe3..0b965b156 100644 --- a/commons/traffic-profile-guidelines.rst +++ b/commons/traffic-profile-guidelines.rst @@ -10,9 +10,13 @@ OPNFV traffic profile guidelines Introduction ------------ -In order to have consistent profiles for testing, it has been suggested to define and store traffic profiles based on operator representative scenario. +In order to have consistent testing profiles, it has been suggested to define and store traffic profiles. +These profiles shall be based on operator representative scenario. -These reference profiles may be used by any test projects, unitary, functional or performance tests. It is possible to adapt them to specific testcases. It is recommended to use them in order to avoid getting as many profiles as tests. It should be helpful to compare the results of test scenario. +These reference profiles may be used by any test projects, unitary, functional or performance tests. +It is possible to adapt them to specific testcases. +It is recommended to use them in order to avoid getting as many profiles as tests. +It should be helpful to compare the results of test scenario. .. _howto: @@ -21,7 +25,7 @@ How to use these profiles ------------------------- The directory of the traffic profiles may be described as follow:: - + ├── commons ├── ims │ └── readme.rst diff --git a/testcases/vIMS/vIMS.md b/testcases/vIMS/vIMS.md new file mode 100644 index 000000000..68f86d9fa --- /dev/null +++ b/testcases/vIMS/vIMS.md @@ -0,0 +1,3 @@ +# vIMS README + + -- cgit 1.2.3-korg From 75124a19a187242f57b4b4e0267e40a0b11cbfdf Mon Sep 17 00:00:00 2001 From: Morgan Richomme Date: Mon, 24 Aug 2015 11:04:42 +0200 Subject: workaround order of env settings to all ODL tests to be run JIRA: FUNCTEST-39 Change-Id: I9d9ad0d9916da7927dace7b968c975c99032738a Signed-off-by: Morgan Richomme --- testcases/config_functest.py | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/testcases/config_functest.py b/testcases/config_functest.py index 3c608344a..9268aa611 100644 --- a/testcases/config_functest.py +++ b/testcases/config_functest.py @@ -90,6 +90,12 @@ def action_start(): logger.debug("Cleaning possible functest environment leftovers.") action_clean() + logger.info("Installing ODL environment...") + if not install_odl(): + logger.error("There has been a problem while installing Robot.") + action_clean() + exit(-1) + logger.info("Starting installation of functest environment") logger.info("Installing Rally...") if not install_rally(): @@ -97,12 +103,6 @@ def action_start(): action_clean() exit(-1) - logger.info("Installing ODL environment...") - if not install_odl(): - logger.error("There has been a problem while installing Robot.") - action_clean() - exit(-1) - # Create result folder under functest if necessary if not os.path.exists(RALLY_RESULT_DIR): os.makedirs(RALLY_RESULT_DIR) -- cgit 1.2.3-korg