aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-02-14Stop reading NODE_NAME in tempest and refstackCédric Ollivier2-22/+1
NODE_NAME should only be read by TestCase when publishing the results to the database. Other debug data are already printed by run_tests. INSTALLER_TYPE and DEPLOY_SCENARIO are also unused by refstack. Change-Id: Ib82d5c1512553beba2c56f4ec2860cb2593f801e Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-14Merge "Enable doctor-notification"Cedric Ollivier2-2/+0
2018-02-14Enable doctor-notificationCédric Ollivier2-2/+0
The testcase has been expected to work since the nova bug [1] was bypassed [2]. [1] https://bugs.launchpad.net/nova/+bug/1742827 [2] https://gerrit.opnfv.org/gerrit/#/c/52075/ Change-Id: If53da6313381cf69a0093a6677db3d9033fb8f48 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-14Merge "Only filter boot_server_from_volume_and_delete via scenario"Juha Kosonen1-1/+1
2018-02-13Merge "Remove INSTALLER_IP from Functest"Cedric Ollivier6-17/+1
2018-02-13Only filter boot_server_from_volume_and_delete via scenarioCédric Ollivier1-1/+1
It can be safely merged as only joid supports '^os-nosdn-lxd-(no)?ha$' scenarios. It aims at testing all installers in the same way which would have made much sense if another installer supported this scenarios. Change-Id: I145102df3f6394b6fff28590923100e0f1e6cb66 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Merge "Test vnf in all os-nosdn-nofeature scenarios"Juha Kosonen2-14/+14
2018-02-13Merge "Enhance variable manipulation in rally"Cedric Ollivier2-45/+30
2018-02-13Remove INSTALLER_IP from FunctestCédric Ollivier6-17/+1
It's mandatory for testcases which are out of Functest. Change-Id: Ia5f5134334ad9f69d44409d817616fa9033fae95 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Enhance variable manipulation in rallyJuha Kosonen2-45/+30
- utilize env vars directly via os module - use getattr to read CONST JIRA: FUNCTEST-931 Change-Id: I893a91331e26846f8effe2d3d58522950bd096fd Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
2018-02-13Test vnf in all os-nosdn-nofeature scenariosCédric Ollivier2-14/+14
It allows setting os-nosdn-nofeature-noha as default value if DEPLOY_SCENARIO is unset. As orchestra* testcases are already disabled, it's useless to ask a specific installer. All vnf testcases should work vs any installer. Change-Id: Ia388f96348f9d06745f8d1669962d7f1c4e47d84 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Temporarily disable doctor-notificationCédric Ollivier3-2/+2
It's currently forbidding gating all APEX' scenarios [1] (even os-nosdn-nofeature-* [2]). It will be enabled when it's fixed or when functest jobs are rewritten [3] [1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/772/console [2] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/770/console [3] https://gerrit.opnfv.org/gerrit/#/c/51853/ Change-Id: I571c464aabe02f67a9e98ca1ab42d8a7efc672ee Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Merge "Remove obsolote env var IS_CI_RUN"Cedric Ollivier1-7/+0
2018-02-13Merge "Read env vars instead of using CONST in API"Cedric Ollivier3-8/+8
2018-02-13Merge "Export env vars instead of CONST in refstack"Cedric Ollivier2-10/+9
2018-02-13Merge "Improve the way of getting env values"Cedric Ollivier4-5/+8
2018-02-13Merge "Improve the way of setting values in CONST"Cedric Ollivier3-5/+5
2018-02-13Merge "Fix the config of fixed_network_name in tempest"Cedric Ollivier4-18/+25
2018-02-13Remove obsolote env var IS_CI_RUNCédric Ollivier1-7/+0
Change-Id: I284e0ec97792620db08005a617f584b81a1eae63 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Improve the way of getting env valuesCédric Ollivier4-5/+8
It simply reads env vars instead of calling CONST.__getattribute__() Change-Id: If3137f3cfb9f3102388988a82393b9b2f4e99f60 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Improve the way of setting values in CONSTLinda Wang3-5/+5
Use setattr instead of internal method (__setattr__). It must be completed by patches fixing [1] [2] and [3]. [1] https://jira.opnfv.org/browse/FUNCTEST-930 [2] https://jira.opnfv.org/browse/FUNCTEST-931 [3] https://jira.opnfv.org/browse/FUNCTEST-932 Change-Id: I9558f33f5ed4559b6031d75951d5637c0c0ef8cb Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-02-13Simplify functest/cli/commands/cli_env.pyCédric Ollivier4-27/+8
CONST shouldn't be used for getting/setting env vars. It adds complexity and may raise side effects. It also removes the obsolete env var CI_DEBUG. Change-Id: I8a8fde0fa781351d5eabd2698ca8aae9dee76fb8 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-13Merge "Export env vars via os.environ in test_openstack_utils.py"Cedric Ollivier2-3/+3
2018-02-13Read env vars instead of using CONST in APILinda Wang3-8/+8
Also, improve the way of getting env values. JIRA: FUNCTEST-933 Change-Id: Ia66bbaf683df03c2874fafe578b84bb78a4f3fd1 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-02-13Export env vars instead of CONST in refstackLinda Wang2-10/+9
JIRA: FUNCTEST-930 Change-Id: I7f28ee0b9a55c53a11f03509c3f9e8eb37cc43a9 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-02-13Merge "Enable invalid-name warnings in tempest modules"Linda Wang2-55/+56
2018-02-13Fix the config of fixed_network_name in tempestLinda Wang4-18/+25
Change-Id: I58726d0fec5b2da4ea8ac1f9925fe56d2f9d7ce0 Signed-off-by: Linda Wang <wangwulin@huawei.com>
2018-02-12Merge "Export env vars via os.environ in test_cli_env.py"Cedric Ollivier1-7/+7
2018-02-12Enable invalid-name warnings in tempest modulesJuha Kosonen2-55/+56
Do not suppress pylint invalid-name warnings but conform the naming convention. Change-Id: I324d25b3081fe8a366249559b343c1b9cacadb21 Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
2018-02-12Merge "Fix pylint errors/warnings in tempest modules"Cedric Ollivier5-188/+226
2018-02-12Export env vars via os.environ in test_openstack_utils.pyCédric Ollivier2-3/+3
CONST shouldn't be used for getting/setting env vars. It adds complexity and may raise side effects. Change-Id: I8319748dd2f0abb95b82a2f65191cac8ccba7f5e Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-12Export env vars via os.environ in test_cli_env.pyCédric Ollivier1-7/+7
CONST shouldn't be used for getting/setting env vars. It adds complexity and may raise side effects. Change-Id: Id80a03aff6eb908a792f1d07addaad4770e8d0cb Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-12Decrease log level in Energy messagesCédric Ollivier1-13/+17
Energy could be safely disabled if one env var is missing. No error message should be printed in console [1]. It could be enhanced in a second step to print the reasons (missing or incorrect env vars) instead of the full stack. [1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/766/console Change-Id: I9c405edae16d186f02c632113de1317c89703991 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-10Run all daily testcases if CI_LOOP is unsetCédric Ollivier1-2/+2
Then CI_LOOP is no longer mandatory and it bypasses the current jenkins jobs's issue [1][2][3]. [1] https://gerrit.opnfv.org/gerrit/#/c/51981/ [2] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/763/console [3] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/764/console Change-Id: I73629079d70e0f43e609d3861490573e10fd216c Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Read the env file only if existsCédric Ollivier2-1/+6
Change-Id: I8e718e583a5a47a089755c31e623a44732e5ba1e Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Ensure logging is disabled when unit testing featureCédric Ollivier1-3/+6
Change-Id: Ibe08477a8b50a6c9b71ab4e5b0ebaaab36692b08 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Unlink robotframework from constantsCédric Ollivier1-3/+2
Change-Id: Ic2c6c84c3824ec3fa208824ae67f1769d4e18c4f Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Merge "Remove one obsolete var"Cedric Ollivier1-5/+0
2018-02-09Merge "Unlink feature from constants"Cedric Ollivier1-3/+2
2018-02-09Merge "Unlink vnf from constants"Cedric Ollivier2-38/+28
2018-02-09Merge "Unlink run_tests from constants"Cedric Ollivier2-18/+16
2018-02-09Fix pylint errors/warnings in tempest modulesJuha Kosonen5-188/+226
JIRA: FUNCTEST-913 Change-Id: I37b25bbcf43fb1d6f7de0c815ad49070d1e1af12 Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
2018-02-09Merge "Unlink Energy from functest utils and constants"Cedric Ollivier3-66/+42
2018-02-09Merge "Move get_dict_by_test() into run_tests.py"Cedric Ollivier4-58/+33
2018-02-09Merge "Conform with OpenStackUser.get_os_creds() in juju_epc"Cedric Ollivier1-8/+4
2018-02-09Merge "Get neutron endpoint via snaps in odl"Cedric Ollivier2-87/+76
2018-02-09Remove one obsolete varCédric Ollivier1-5/+0
Else it simply forces the config file into xtesting. Change-Id: I33153997f2aa422e50cea011f6a4e7eb567a83d7 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Unlink feature from constantsCédric Ollivier1-3/+2
Saving results dir as class attribute seems better in the context of xtesting. Change-Id: If40303d07d3be9bdc09d990f560cbeda429fd642 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Unlink vnf from constantsCédric Ollivier2-38/+28
It generates a default description which all testcases can easily override. Change-Id: I81b97c394cf064088767cc934295602f01a7f739 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-02-09Unlink run_tests from constantsCédric Ollivier2-18/+16
run_tests.py doesn't read any functest config file what is mandatory for xtesting. Change-Id: I49f672c54a606acead75f573d1ce496c81fb235a Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>