2: Guilin Release Integration Testing Status

Owned by David McBride
Last updated: Nov 06, 2020 by Byung-Woo Jun
1 min read

Note:  Beginning with Guilin, we will use a Jira table to track integration test tasks.  See instructions here.

Link to: Guilin Release Requirements



key summary assignee integration test plan status integration test status integration test time to complete epic link issuelinks
Refresh



*: CI integration: the goal is to introduce the use case in CI daily chains for Frankfurt. Ths table could be completed with a CI dashboard where the use cases will be run every day.

As it should be runnable in any lab, some constraints need to be considered:

  • no proprietary VNFs                                            

  • use cases must be self-content , third party equiments may not be present in all labs.

  • infrastructure setup/teardown shall be clear: the use case must be runnable from a clean ONAP installation. These resources must be cleaned at the end of the test ,

  • results shall be pushed to a common DB. It is recommended ot use xtesting to run the tests (robotframework, python, bash, unit test drivers)