Age | Commit message (Collapse) | Author | Files | Lines |
|
refstack_defcore has been merged
the testcase is no more needed (duplication)
Change-Id: I287406b40cdd89ff2c4eadcde7e9d5a93e21953a
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
The criteria of refstack_defcore is supposed to be ">= 80%" rather
than "== 80%".
Change-Id: I9f9e38c84925c3725289e8b427e5735d131459f1
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
main and init functions in generate_reports"
|
|
|
|
|
|
|
|
|
|
|
|
JIRA: DOVETAIL-366
JIRA: FUNCTEST-758
Parse refstack_defcore results, including:
1. show number of tests passed, skipped and failed
2. record the detailed info about testcases passed, skipped and failed.
Change-Id: I355a907c5c9ea2739f845447144c62613ec3bb6a
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
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>
|
|
So far DB url was retrieved from configuration file
If you want to use the CI chain (jenkins, testapi, test DB,
functest, ..) then you have a problem
calling functest will systematically point to the configuration
from the repo
Supporting env variable allow to avoid post processing in the
configuration file and as a consequence offer the possibility
to create a local DB to host local results
Change-Id: Ie64b8b265827d7f5724c7066a8c173de8cf012e2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I66f43fb09472948bc71178cd8aeb14dc1ab5fa55
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
Change-Id: I0b1d7efcf44c0ad2c1e8d3163fe72a61883eb86a
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
Change-Id: I5cd900cee809b8fd935a5c8b862a9ecd6278bdf5
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
argument refactoring for main and init
functions in generate_reports
Change-Id: I291d04a9c0ed381f4b92e989270c0b9a37c15264
Signed-off-by: ashishk1994 <ashishk.iiit@gmail.com>
|
|
ovno has no danube branch and is not used
clean the ovno from functest to avoid side effect
when producing danube functest docker file
Change-Id: I5347111fc90a04ca9018679b5578ca30ae33b2f2
Signed-off-by: Morgan Richomme <morgan.richomme@orange.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>
|
|
|
|
until exceptions are better managed in abstraction
Currently it triggers an exit from the jenkins job
and prevent other tests to be run
Change-Id: Id3b18c1d6d3b786fc78456b3ad51963d2cbb2cc1
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
Change-Id: I43550b2062c69d7b4eb144057a90806f92328739
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
|
|
|
|
|
|
Change-Id: I25423cc3fbab54f81047fbebd0bc33895d826186
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
Doctor feature not available for Joid on Danube
Change-Id: I1d39ff15a1fe003689828f6923b92c7e7c7d716f
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
Change-Id: Ibf04adcaa0b14c4cdda8fba2ef2826a0c7f3b7d4
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
|
|
|
|
|
|
Change-Id: If92c7d402b88f59367564f7279d426eb8f3b582a
Signed-off-by: boucherv <valentin.boucher@orange.com>
|
|
currently the snaps healthcheck (dhcp) is tried first
it should be connectivity, api, dhcp
the reporting looks for scenario based on connectivity
testing dhcp first => scenarios ok on connectivy but
failed with DHCP are not considered, which could be
misleading
Change-Id: I0eb34b1f5ba163540281e5ef0dcb12c8cefa88bd
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: FUNCTEST-747
Change-Id: I85f15188315136cc44876914325e3693f7973af8
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
|
|
Added:
- fds repository to docker file
- fds test to smoke tier in testcases
- config values for fds tests
A new robot var OS_AUTH_URL is defined as expected by FDS robot files.
Method args switch from Keystone IP to OS_AUTH_URL which is more
precised. The argument parsing is changed too.
Co-Authored-By: Cédric Ollivier <cedric.ollivier@orange.com>
Change-Id: Ife27ab4a83f0110cbdcf7c9d47d9b3fb4c0ec705
Signed-off-by: Tomas Cechvala <tcechval@cisco.com>
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
This reverts commit 044de9eb0c74fb2ef9cb34b6487bf0536412058d.
Change-Id: I9179f4b5ce866456e8ec85cb8a730a5d7f2af16e
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
Change-Id: Id903683b12366c5a2f486c8b7d7ce6977d4448e0
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
JIRA: FUNCTEST-742
Change-Id: I5de8ed22932250c542751e38eae3185c4a263cd0
Signed-off-by: Juha Kosonen <juha.kosonen@nokia.com>
|
|
Change-Id: Ied92224bc80ab4e02611e7b1f4bf33f276914e89
Signed-off-by: boucherv <valentin.boucher@orange.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>
|
|
SNAPS healthcheck is already excluded due to the
use of QCOW2 images, not compatible with lxd
scenarios
2 JIRAs have been cretaed to adapt the SNAPS cases
to lxd in Euphrates
https://jira.opnfv.org/browse/FUNCTEST-752
https://jira.opnfv.org/browse/FUNCTEST-753
Additionnal cleaning done on testcases.yaml
- remove juju_epc case (no one from OAI available
for Danube)
- remove orchestra (as standalone test case of the
MANO stack, postponed to Euphrates)
- comment aaa (empty sample used to illustrate
the VNF abstraction but not completed for Danube)
Change-Id: Ibad6cad4c92ee9897b6665b29c09b62cb1986aae
Signed-off-by: Morgan Richomme <morgan.richomme@orange.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>
|
|
JIRA: FUNCTEST-750
1.Modification of repo path for vrouter in config_functest.yaml
Change-Id: I798e27df9667c3dea55dddba51c53f6ac0d13381
Signed-off-by: Hideyasu Hayashi <hideyasu.hayashi@okinawaopenlabs.org>
|