Page tree
Skip to end of metadata
Go to start of metadata

Preparation & useful links


Test strategy release C (Morgan):

Proposal Tiers (Jose):

Espoo Meetup minutes:

Introduction for Flash test (Nikolas):


Post mortem

Global Testing post-mortem:

Some graphs based on the validated scenarios (stored from reporting)

Colorado Release Time plan

Please Note

  • the dates have been modified by Functest and have not been validated. They correspond to what something reasonable according to Functest contributors 
  • OPNFV Plugfest 9-13/5
  • OPNFV Summit 20-23/6

See Colorado for more details

Summer vacation planning

CG_Nokia1/7 - 31/7

In Ireland 1st July -> 7th July
Back in Finland 8th July

viktor_t11/7 - 31/7, 8/8 - 10/8 
Jose1-25/8Summer vacation in Spain.
juhak11/7 - 7/8


JuhaHaapa11/7 - 7/8 
lhinds22/7 - 08/8 

Colorado Functest test cases

Colorado test cases are declared in and in the Test DB (

TierTest caseProjectCI loop



0: healthcheckhealthcheckfunctestmerge/daily/weekly2
1: smoke

2: sdn_suiteodlfunctestdaily/weekly1
3: featurespromisepromisedaily/weekly1

We introduced the notion of Tiers in order to assign a category to the test cases and ultimately save time in CI.

Project management

Coordinated schedules with other projects and captured cross project dependencies in JIRA

  • Dependencies to SDNVPN project:  FUNCTEST-181 - Getting issue details... STATUS   SDNVPN-19 - Getting issue details... STATUS   SDNVPN-38 - Getting issue details... STATUS
  • Dependencies to Promise project:  FUNCTEST-162 - Getting issue details... STATUS   PROMISE-35 - Getting issue details... STATUS
  • Dependencies to ONOSFW project:  FUNCTEST-182 - Getting issue details... STATUS  (still needed linked dependencies)
  • Dependencies to OVNO project:  FUNCTEST-183 - Getting issue details... STATUS  (still needed linked dependencies)
  • Dependencies to Doctor project: not defined yet
  • Additional projects to be discussed (Copper? Policy?) 


Established a concrete project time plan in place that accommodates dependencies and resource availability

Described in the tables above and below.


Clarified dependencies, must include upstream dependencies, impacting ability to execute on future milestones

The only upstream tools used in Functest are Openstack/Tempest and OpenStack/Rally projects and they do not impact any milestone as we use fixed stable versions that are always in line with the continuous OpenStack releases.


In addition:  please include a link to a JIRA filter and/or dashboard that includes your documented JIRA issues.


List of JIRA issues:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution


Colorado content for Functest

Note: most of the task have only 1 owner and can be done in parallel. 

test evolutionnew testframework evolution
ODL (Colum, Cedric, Ragha, Juha)Security Group (David)Dashboard evolution to Kibana (Juraj) changed DB backend from Mongo DB to Elastic search to include native analytics functions (Juraj)
vIMS (Valentin)security suites (Luke)Test management refactoring - slicing the test suites from Health to VNFs (Jose)

Tempest evoution (2 levels smoke and advanced)

back to upstream / upstream contribution

new VNFs (Bertand)Add trust indicator to optimize test runs (Morgan)

Rally evolution

back to upstream / upstream contribution

ARM suite (Ciprian)new unit test on API (Serena)
Onos evolutionFlashtest (Nikolas)

Add swagger for automatic documentation of the API (Serena)

 Opencontrail / Ovno (with OVNO contributor)Generate automatic test reporting (Morgan)
  Refactoring of Jenkins page (May)
  API evolution (include version, scenario, success criteria, trust indicator.. (Morgan)
  Add web admin frontal to declare/modify/remove new test cases/pods/projects in DB (Mongo then Elasticsearch) (Ragha)


Feature project Matrix


ProjectProject declared in test DB

Test cases declared

in test DB

JIRA createdHistory

Link to test dir

in project repo

Test duration

evaluation (min)

success criteriaPart of release criteria



promiseyesyesyes> Brahmaputrayes1PASSYesinstaller: fuel, joid
doctoryesyesno> Brahmaputrayes5PASSYesinstaller: apex
sdnvpnyesyesyes*> Brahmaputrayes1PASSYesscenario: bgpvpn
copperyesyesyesColoradotests10PASSYesinstaller: all scenarios of JOID, APEX
modelsnononoColorado?10PASSYesinstaller: all
moonyesyesyesColorado?5?PASSYesscenario: moon
movienononoColorado?5?PASSTo be decidedscenerio:os-odl_l2-*, Installer:tbd
multisiteno (Not yet)no

Test cases ready in OpenStack repository,

provide plugin to tempest

tempest can discover the test cases

yesColorado?10?PASSTo be decided

Use preconfigured multisite testbed

for no installer support multisite installation automation yet.

parsernonoyesColorado?5PASSTo be decidedscenerio:os-onos-nofeatue-ha, installer:compass
dominoyesyesyesColorado?5PASSTo be decidedscenerio:os-onos-nofeatue-ha, installer:compass
Parser + Open-O
ONOSFW yesyesyes> Brahmaputrayes (in 1-2 weeks)~ 10PASSYes

installer: all

scenario: os-onos-sfc (vnffg)


How to Functest

Why did we create tiers?

How to know which test I can run?

How to manually start Functest test?

How to select my list of tests for CI?

How test constraints are defined?

How do I declare my project in the Test DB?

How do I push my results in the database?

Where can I find the documentation on the test API?

How to exclude Tempest case from default Tempest smoke suite?

How do I know the Functest status of a scenario for Colorado?


  • No labels