summaryrefslogtreecommitdiffstats
path: root/testcases
AgeCommit message (Collapse)AuthorFilesLines
2016-09-06Merge "[Promise] Fix bug opening the json result file"jose.lausuch1-2/+2
2016-09-06[Promise] Fix bug opening the json result filejose.lausuch1-2/+2
Change-Id: I8882ffc8139095a79b6542c508a6293ae231f232 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-06Merge "Add support of arm for doctor"Jose Lausuch1-2/+9
2016-09-06Add support of arm for doctorcristinapauna1-2/+9
This is half of the fix to make the doctor suite run on arm. The other half is at https://gerrit.opnfv.org/gerrit/#/c/20369/ In this fix I set an enviroment variable, to be used by the doctor suite when ran with functest. The variable is set only when present in config_functest.yaml, which we use as a custom file when running functest on arm. Change-Id: If34d3e7734a194bf9fe8b525a362e029767caa4f Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-09-06Merge "[Promise test case] Use proper way to get parameters from yaml"jose.lausuch1-37/+38
2016-09-06Merge "Add blacklist handling for rally test cases"Morgan Richomme3-17/+79
2016-09-05[Promise test case] Use proper way to get parameters from yamljose.lausuch1-37/+38
Since there is a function in functest_utils to get a value from the config_functest.yaml directly, there is no need to load again that file. Better to use common functions that are designed for that. Also, Replace location of the results json file to the results directory. It will be also pushed to artifacts repository. Change-Id: Ic6422ed78ccd0f8b40b519342a7dcf38c502924e Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-05Add blacklist handling for rally test casesJuha Kosonen3-17/+79
Test cases can be excluded from execution based on installer/scenario via blacklist file. JIRA: FUNCTEST-451 Change-Id: I17bbd5f1364a890b88bc196cbc5f49c492df1cb1 Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
2016-09-05Redirect dominio's output to a log fileCarlos Goncalves1-2/+7
Change-Id: Ic4daa57ddbf6587660f982acd915cd4363d3ccbc Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
2016-09-05Merge "[Doctor test case] Redirect output to a log file"jose.lausuch1-5/+12
2016-09-05Merge "Switch print to logging.info"Morgan Richomme4-31/+43
2016-09-05[Doctor test case] Redirect output to a log filejose.lausuch1-5/+12
The output shown in the Jenkins console will now be redirected to a file which will be available and linked to the artifacts repository. Change-Id: I2e9b5c2ab681a787aa0fc249844cc13feb581764 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-05Revert excluding floating IP cases from odl_l3vitikkan1-19/+0
Only restrictions table in release notes is updated. Change-Id: I8f27a876058eabe1c490fc5980de5626aed665a3 Signed-off-by: vitikkan <viktor.tikkanen@nokia.com>
2016-09-02Merge "Exclude test cases that use floating IP from odl_l3 scenarios"Morgan Richomme1-0/+19
2016-09-02Exclude test cases that use floating IP from odl_l3 scenariosvitikkan1-0/+19
All the tempest_smoke_serial test cases that use floating IP addresses for accessing instances are excluded because of ODL bug https://bugs.opendaylight.org/show_bug.cgi?id=5586 JIRA: FUNCTEST-445 Change-Id: I19468be108a25e989c0cfef031bbe5f2b9db0964 Signed-off-by: vitikkan <viktor.tikkanen@nokia.com>
2016-09-02Merge "Print all the Copper test output to a log file"jose.lausuch1-6/+10
2016-09-02Print all the Copper test output to a log filejose.lausuch1-6/+10
To keep the jenkins console clean and readable, dump all the output that the Copper test case generates to a log file and push it to artifact repository at the end. Change-Id: If4812c7e92b4d050757ca07333f7c353a0220056 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-02Merge "Print all the Parser test output to a log file"jose.lausuch1-6/+9
2016-09-02Print all the Parser test output to a log filejose.lausuch1-6/+9
To keep the jenkins console clean and readable, dump all the output that the Parser test case generates to a log file and push it to artifact repository at the end. Change-Id: I04c8507fda535c7bcb0919fc3bc5877336664942 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-01Change debug mode for commands that generate too much output in sec_scanjose.lausuch1-6/+7
The security scan test case generates sometimes too much output messages and makes Jenkins unreadable. For example: https://build.opnfv.org/ci/job/functest-apex-apex-daily-colorado-daily-colorado/65/console 80% of the output belongs to this test case. This patch will reduce it since debug information is not showed in Jenkins but it is pushed as part of functest.log to artifacts. Change-Id: I56b3adf87d302d118ee5c15eb86bc10237a7cc4e Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-01Fix some bugsboucherv1-1/+1
Change-Id: Iaf0859775933ba09cbbe170af3ce4ed1e6d3e9a1 Signed-off-by: boucherv <valentin.boucher@orange.com>
2016-09-01Switch print to logging.infoCédric Ollivier4-31/+43
It follows the recommendations described in the next review [1]. [1] https://gerrit.opnfv.org/gerrit/#/c/19795/ Change-Id: Ie7ce28451122c554f135caad068844c0303deaeb Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2016-09-01stop hardcoded FUNCTEST_REPO path everywhereSerenaFeng9-41/+32
functest repo is used by almost every testcase, each place we get it like: REPOS_DIR = os.getenv('repos_dir') FUNCTEST_REPO = ("%s/functest" % REPOS_DIR) provide a common interface in functest_util.py JIRA: FUNCTEST-453 Change-Id: Ie0635dacc761ed2d05b7e606530368844f32ebaf Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-09-01Merge "unify functest_yaml obtain process"Jose Lausuch9-51/+24
2016-09-01Merge "Add a specific logger for orchestrator class"Jose Lausuch2-60/+45
2016-08-31Refactor SFC testcaseGeorge Paraskevopoulos1-49/+54
- Change the way the test checks if the vxlan_tool has started. Now the vxlan_tool is detected even if another python process is up. - Log the exceptions in the vxlan_tool check block. The exceptions that occur are not destructive for the testcase but it's better to be visible. - Add a 60 seconds sleep before the testcase starts to give plenty of time to ODL to add the correct flows. - Move the testcase success/fail check blocks inside the try blocks. The checks are performed on the stdout variable which is in scope only inside the try blocks. Change-Id: I49dec176fb83117e9896ac1d19e8a5bd95e3d7cf Signed-off-by: George Paraskevopoulos <geopar@intracom-telecom.com>
2016-08-31Add a specific logger for orchestrator classboucherv2-60/+45
JIRA: FUNCTEST-428 Change-Id: I1aab08f8f92df3b5527e6f8121cdf45aec2f5c17 Signed-off-by: boucherv <valentin.boucher@orange.com>
2016-08-31unify functest_yaml obtain processSerenaFeng9-51/+24
functest_yaml is needed in almost all of the testcases, the obtain process is the same: with open(os.environ["CONFIG_FUNCTEST_YAML"]) as f: functest_yaml = yaml.safe_load(f) f.close() abstract a method to unify the process, and provide the interface JIRA: FUNCTEST-447 Change-Id: I96a9a9962d7b466f10bbd3b5ab2495957524e22a Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-31Remove all logers as utils method args.Cédric Ollivier14-31/+15
As it modifies method params, it could break the testcases. JIRA: FUNCTEST-428 Change-Id: I4263d9bd812f1803e513464e3c321cc4a7281958 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2016-08-31Merge "delete useless FUNCTEST_REPO variable"Morgan Richomme5-5/+0
2016-08-31Fix problem with SFC testBrady Johnson1-0/+5
- If its not possible to get the IPs, then exit - Patch Set 2: addressed code review comments Change-Id: I16e22513b32e2b0da311ebcc280f3611570634a3 Signed-off-by: Brady Johnson <brady.allen.johnson@ericsson.com>
2016-08-31delete useless FUNCTEST_REPO variableSerenaFeng5-5/+0
FUNCTEST_REPO appears in lots of feature testcases, but never be used, delete it clean the code JIRA: FUNCTEST-448 Change-Id: I4a9a10eac29e09b481563ed2c33f4122dd9ee3de Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-30disable test case does not make sense for LXD.Narinder Gupta1-0/+11
This patch will disable the test cases which does not make sense to run on LXD deployments. Change-Id: I683b3714aa5af3c750ca57fab9fceff907b7d646 Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
2016-08-30update fuel ref in tacker setup scriptFerenc Cserepkei1-1/+1
Since the poc script is fixed it's fuel commit hash in the setup script have to be updated to select the fixed poc script. Change-Id: I1fd22e4dc216fd2889adea0c9889df1d4a1bf476 Signed-off-by: Ferenc Cserepkei <ferenc.cserepkei@ericsson.com>
2016-08-30Exclude floating-ip related tempest tests to blacklist for bgpvpn scenariojose.lausuch1-0/+2
Change-Id: I7115018e64a2413209313b9a432d3d1b59e841d1 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-08-26refactor create shared network process to eliminate reduplicateSerenaFeng2-32/+11
Some places shared network is created through create_network_full first, then update it to shared, abstract a uniformed method to eliminate reduplicate JIRA: FUNCTEST-437 Change-Id: I13c20ab061323188c5eb3b8c861674df38083c62 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-26Merge "refactor create or get image process to eliminate reduplicate"Morgan Richomme3-56/+15
2016-08-26Merge "Stop calling exec_test.sh in the middle of python scripts"Morgan Richomme3-3/+42
2016-08-26Merge "[Fuel] Skip test_server_basic_ops tempest test"Morgan Richomme1-0/+14
2016-08-26refactor create or get image process to eliminate reduplicateSerenaFeng3-56/+15
Some places when create image is referred, they check if image exist, if exist use it directly, else create a new one. Abstract a method to integrate the process JIRA: FUNCTEST-432 Change-Id: I83d1112aa5cb0d3cdfab92fd49cd5f2c1cceff82 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-24Stop calling exec_test.sh in the middle of python scriptsCédric Ollivier3-3/+42
Now run_tests.py calls directly OpenDaylightTesting.functest_run(). It mainly reads env vars as exec_test.sh does. Change-Id: Ibb44a7ca67e9218d34d13b8dd539e772902fe5b8 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2016-08-24Fixing commit f1054f8fFerenc Cserepkei1-1/+1
fix missed the apt-get action Change-Id: Iac94576a2f712133eee92e4b5460f85d59e90e94 Signed-off-by: Ferenc Cserepkei <ferenc.cserepkei@ericsson.com>
2016-08-24[SFC] Fixing CINikolas Hermanns1-0/+1
The fix https://gerrit.opnfv.org/gerrit/#/c/19351 will need more time for dicussion. In the meanwhile we can use this one so that CI does not break anymore. Change-Id: Icbd54200bd62e5019c2a556699ceb41afdb229ca Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
2016-08-23Merge "when create/get/update failed return None rather than False"Morgan Richomme3-7/+7
2016-08-23Merge "delete useless image_exists in vping"Morgan Richomme2-7/+2
2016-08-23when create/get/update failed return None rather than FalseSerenaFeng3-7/+7
In openstack_util.py, when create/get/update network or other resources failed, False is returned, which is incompatible with success return value such as id, network_nic. JIRA: FUNCTEST-427 Change-Id: Id2f55d8524e5aff150ba6bfb799085377a63baa4 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-23[Fuel] Skip test_server_basic_ops tempest testMichael Polenchuk1-0/+14
Skip TestServerBasicOps which fails when deleting server and floating ip almost at the same time. JIRA: FUEL-173 JIRA: FUEL-176 Change-Id: I24f3397096757028bed9d32d6353aa689e8eaa9a Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-08-23Create tempest resources before generating tempest.confvitikkan1-1/+1
During generating tempest.conf file rally tries to download cirros image from the internet if no suitable images exist in the configuration. This change ensures that cirros image is created before generating tempest.conf file. JIRA: FUNCTEST-195 Change-Id: I9e2df8af40bd02db9b78b8b6b730b4f4168a8b2d Signed-off-by: vitikkan <viktor.tikkanen@nokia.com>
2016-08-23Add logger to push_results_to_db argsCédric Ollivier1-1/+1
It conforms to the current implementation of functest_utils Change-Id: I50fa05fbf81a7c76cf4a6e3ef906fffe8aec15bf Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2016-08-23delete useless image_exists in vpingSerenaFeng2-7/+2
In rally, image_exists is used to decide whether the image resource should be cleaned or not. But unlike rally, image_exists in vping is only assigned but not never be actually used. JIRA: FUNCTEST-426 Change-Id: Id2089dd2a9734ba957cc1c80d4dc31bc27907b0a Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>