aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--ci/config_functest.yaml92
-rwxr-xr-xci/exec_test.sh3
2 files changed, 2 insertions, 93 deletions
diff --git a/ci/config_functest.yaml b/ci/config_functest.yaml
index 4c673fab6..dc0919bbf 100644
--- a/ci/config_functest.yaml
+++ b/ci/config_functest.yaml
@@ -156,95 +156,3 @@ promise:
results:
test_db_url: http://testresults.opnfv.org/test/api/v1
-
-# to be maintained...
-# the execution order is important as some tests may be more destructive than others
-# and if vPing is failing is usually not needed to continue...
-test_exec_priority:
- 1: healthcheck
- 2: vping_ssh
- 3: vping_userdata
- 4: tempest
- 5: odl
- 6: onos
- 7: ovno
- 8: doctor
- 9: promise
- 10: odl-vpnservice
- 11: bgpvpn
- #11: openstack-neutron-bgpvpn-api-extension-tests
- 12: vims
- 13: rally
-
-
-########################################################################
-# This part lists the dependencies of the tests
-#
-# it is used to manage the complexity of the possible combinations
-#
-# 17 projects have been declared for Brahmaputra (D Milestone)
-# 89 testcases are associated with these 17 projects
-#
-# in B-Release, Functest deals with 6 companion projects:
-# - congress
-# - doctor
-# - ovno
-# - policyTest
-# - promise
-# - sdnvpn
-#
-# constraints may be declared at the testcase or the test project level
-#
-# By default we consider that all the tests can be run on any configuration
-#
-# we defined 2 constraints
-# - installer (e.g. my test can be run only with installer Compass)
-# possible values: apex, compass, fuel, joid
-#
-# - the scenario: it described a specif installation
-# os-<controller>-<nfvfeature>-<mode>[-<extrastuff>]
-# With parameters:
-# controller=(nosdn|odl_l3|odl_l2|onos|ocl)
-# No odl_l3 today
-# nfvfeature=(kvm|ovs|dpdk|nofeature)
-# '_' list separated.
-# mode=(ha|noha)
-# extrastuff=(none)
-# Optional field - Not used today#
-#
-# ref:https://gerrit.opnfv.org/gerrit/#/c/6323/7/jjb/joid/joid-deploy.sh (L72-82)
-# e.g my test is only possible with OVS 2.3.2 on odl
-#
-# in functest, we indicate the regex pattern to be checked towards the scenario
-# e.g. odl-vpn_service-tests can be run if and only if
-# - installer is fuel
-# - scenario contains the name ovs and odl
-#
-#######################################################################
-test-dependencies:
- doctor:
- installer: 'apex'
- functest:
- vims:
- scenario: '(ocl)|(nosdn)|^(os-odl)((?!bgpvpn).)*$'
- healthcheck:
- vping_ssh:
- scenario: '^((?!bgpvpn).)*$'
- vping_userdata:
- tempest:
- rally:
- odl:
- scenario: 'odl'
- onos:
- scenario: 'onos'
- promise:
- installer: '(fuel)|(joid)'
- ovno:
- scenario: 'ocl'
- policy-test:
- scenario: 'odl'
- sdnvpn:
- bgpvpn:
- installer: '(fuel)|(apex)'
- scenario: 'bgpvpn'
- # this execute the tempest tests of networking-bgpvpn
diff --git a/ci/exec_test.sh b/ci/exec_test.sh
index 9d8d83d66..4a75bcbde 100755
--- a/ci/exec_test.sh
+++ b/ci/exec_test.sh
@@ -126,7 +126,8 @@ function run_test(){
sleep 10 # to let the instances terminate
;;
"doctor")
- python ${FUNCTEST_REPO_DIR}/testcases/features/doctor.py
+ # Comment Doctor until Green light from Doctor team
+ # python ${FUNCTEST_REPO_DIR}/testcases/features/doctor.py
;;
"ovno")
# suite under rewritting for colorado