Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
JIRA: DOVETAIL-366
JIRA: FUNCTEST-758
usage:
1,functest testcase run refstack_defcore, will run the
default testcases in defcore_201608.txt
2,cd <path>/functest/functest/opnfv_tests/openstack/refstack_client
python refstack_client.py -c <tempest-conf-file-path> --testlist <testlist-path>
this has been worked with openstack-refstack experts, etc.
tested workedi.
result see http://paste.openstack.org/show/602173/
Change-Id: I1aaffea01dec9dc8d1c572885bdf516614a16894
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: I774d3625d35e3d264d609ba9aa7538a723923bcf
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Actually attach_detach_volume must be skipped because the device name
ain't reliable and that's using a hard-coded device name in config.
This test should just get the device info after the attach and use
that rather than the hard-coded config option in Tempest that ain't
likely to work - the test should have been written more dynamically.
However, set volume device name to "vdc" since "vdb" is used for config
drive when force_config_drive=True is in action.
Change-Id: Ic70de93a609df932c7749a94f71505e927df1b79
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
JIRA: FUNCTEST-747
Change-Id: I85f15188315136cc44876914325e3693f7973af8
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
JIRA: FUNCTEST-742
Change-Id: I5de8ed22932250c542751e38eae3185c4a263cd0
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
This commit sends the aarch64 custom config to the snaps integration
tests. Since these are the same as the snaps healthcheck, no additional
values were added to config_aarch64_patch.yaml
Change-Id: I5f2302a3c65d47ec8fca661888268489e2c6ba35
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
As certain scenarios such as, DPDK, FDIO, and OVS use cases
require special 'hw:' settings to flavors, SNAPS-OO has just
implemented the ability to take in these configuration values
to apply to its integration tests. This change checks the
scenario and should be configuring the flavor metadata accordingly.
Also see SNAPS-38
Used this as an opportunity to refactor the SNAPS test classes as well...
JIRA: FUNCTEST-746
Change-Id: I63535776acde088a7461f602966a324b6207592d
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
This commit is half of the fix for adapting the snaps healthcheck
to run on an aarch64 POD. The fix consists in reading the custom
parameters and passing them to the snaps test
The snaps part that uses this info is
https://gerrit.opnfv.org/gerrit/29853
JIRA: ARMBAND-222
Change-Id: I2027f2ef3afe0caddef781771f2190fc173aff8c
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
_parse_verification_id method is removed
as it is not used anywhere
Change-Id: Ia2bc75ffbc2527b04cbe2428e2a3822803bde215
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
|
|
|
|
Change-Id: I81424c3670b6a6e03a38da83dc93c998bf8c2f5e
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: Ia468b9c9ab9f74a3255aa3647916d1018cef2902
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
Some users need to run a specific list of
tempest test cases. This patch allows them
to do that by running the command:
functest testcase run tempest_custom
Change-Id: If8e7726b98c3a71398c7abdf80aea79f10653ebf
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
|
|
Refstack is the OpenStack project that provides the tooling
to run the approved specific tempest test cases (Defcore guidelines)
by the Interop working group and by the OpenStack board
for OpenStack certification purposes.
For more info: https://refstack.openstack.org/
This adds the possibility for a Functest user to run this list
of tempest test cases by just issuing the command:
functest testcase run tempest_defcore
The test will be run on daily loops with the scenario nosdn-nofeature
on any installer.
Change-Id: I920b2a44cff418116008fdf514425e69dc959412
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
With the recent changes in Cirros image default password, we
need to support configuring these credentials.
JIRA: ARMBAND-218
Change-Id: I5962ec2aeee4ffecefdd8b7e70bdb7ed88457553
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Add multisite parameters into tempest config file after the file have
been (re)configured by rally verifier.
JIRA: FUNCTEST-721
Change-Id: I95fd7e29b5a7d1d9f82e84e383eb23e8fa813d19
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
|
|
* changes:
Add can_dump_request_to_file decorator
Revert "write test results to a local file"
|
|
JIRA: FUNCTEST-725
Change-Id: Ic1e6a54c2dbfb1dee5f8f6e6afd60382749bcd09
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
This reverts commit ee21af78fbfc93e888acda121f08d2b216dd0159.
Change-Id: If7c8d3b645073574862eb67225b1e11b0dd7a021
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Checking Return status code after each step can be wrapped by Exception
catching
Also, the return code is not as informative as exception
Change-Id: Ic15791d1b8ee47e10cbae8bad46a2cb90ac2b46e
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
Create two new functions: configure_tempest_update_params and
configure_verifier, distinguishing between tempest.conf
configure verification and add/updating parameters into it
this update is useful and it will be used by sdnvpn/tempest
Change-Id: I76e0bc00e33492252cdecab224380ecca2ce275a
Signed-off-by: tomsou <soth@intracom-telecom.com>
|
|
bash healthcheck.
JIRA: FUNCTEST-570
Change-Id: Ia90dc152d48144c9c53967d5c30256389793ce91
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
|
|
Replaced 'kingbird' with 'multisite' as kingbird
installation scripts register 'multisite'.
JIRA: MULTISITE-720
Change-Id: Ib53bab46a1fa225e371912d74eecb929d84dff3a
Signed-off-by: Dimitri Mazmanov <dimitri.mazmanov@ericsson.com>
|
|
|
|
JIRA: FUNCTEST-719
1.in new tempest version, FAILED-->fail
see log https://build.opnfv.org/ci/view/dovetail/job/dovetail-compass-virtual-debug-master/163/artifact/results/tempest/tempest.log
2.there is a need to show the skipped testcase in tempest
Change-Id: If753c59971362625ae0797a0161e07b1e4ff94c8
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
There is currently a bug with glance in newton which is causing Apex
healthchecks to fail:
https://bugs.launchpad.net/python-glanceclient/+bug/1661089
I have created a fix and tested it upstream:
https://review.openstack.org/#/c/427929/
That fix should eventually end up in functest, but in addition it is a
good idea to move to the universal CLI (this patch).
Change-Id: Ie71b301ff856f2d50fd889ff36f634911e616b38
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Few bug fix in rally code along with unit tests.
Change-Id: Id39a5089ca6fce8aac5ba89eb61d31b02a5e9a98
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
Ensure the target directory for tempest config file exists.
JIRA: FUNCTEST-715
Change-Id: I7bfaab1faa3e664d84813cdbf9a830b0b56a1f60
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
JIRA: FUNCTEST-711
Change-Id: Ib89ad63f0f97ff27e62fd6af200a15b9eed646c6
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
the return shall only deal with test executed or not
it shall not return the criteria through a return statement
the criteria is managed with the criteria field
previous patch https://gerrit.opnfv.org/gerrit/#/c/27807
corrected the fact that we should not return the status of the test
which was preventing Failed results to be pushed
but it removed the return needed statement
JIRA: FUNCTEST-714
Change-Id: I3d4c609467837e4ce2353c67c0b8ea95e21ebd84
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-685
Change-Id: Id0d0bcf55451832d9aeb22c3e6b9c21aea4e0911
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
These functions are useful for other test cases trying
to run tempest. For example BGPVPN tests cases located
in SDNVPN repo.
Change-Id: I67e671f4e9b0a2d81a3ab0d1957ce144fb1a0432
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
this problem was due to the fact that we add exit condition
EX_ERROR when the result was FAIL
EX_ERROR shall be used as exit condition when there is an
execution error, i.e the test case cannot be run
if it can be run, there is no execution error
the result can be PASS or FAIL, but from the CI, execution is OK
JIRA: FUNCTEST-714
Change-Id: Id434bb9aa88b50277c40c717259304f26f7b3966
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
* newton release support is started from 13.0.0
* set swift operator role to existing one
* unblacklist server_basic_ops test
JIRA: FUNCTEST-712
Change-Id: Ieb3d9477db3dfa98f940c3732b64f6eb7515f6e6
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
JIRA: FUNCTEST-541
Change-Id: Ife04f58dc31ca9ba6316cc31577f81a6bf0e0405
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
|
|
Write test result to a file or push it to DB depends
on the value format of test_db_url which is defined in
config_functest.yaml. Meanwhile, test_db_url can be set
by os envrion value "RESULT_STORE".
If test_db_url is a url, e.g. http:// or https://, then
push result to DB. If test_db_url is a file location,
e.g. file:///, then write results to a file with json data.
One result record, one line.
JIRA: FUNCTEST-657
Change-Id: I579087cd2c24d61a79142b5d67003fb486b6c723
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
JIRA: FUNCTEST-652
1. Updated the Rally repository to master
the keystone test scenarios of TAG= 0.7.0 cannot run on Newton
also, 0.7.0 is the last tag that exists
2. Update the Tempest installation with updated rally command
Rally team said "there was no possibility to do it in backward
compatible way(rally verify re-design)"
3. The `rally show` was deprecated[1] in the master and corresponding
logic is updated
4. Update rally commands
[1]
https://github.com/openstack/rally/commit/f2fc3015beb4cfd8053db728765714500db6eeb2
Change-Id: Ief9e36a16dd92e4449c0f76579e7191a93aa3e21
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
JIRA: FUNCTEST-503
Change-Id: Ie92051ec128ad4857862e6125628dac24ce99a2a
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|