Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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

Guilin Release Requirements


key summary assignee integration test plan status integration test status integration test time to complete epic link
Loading...
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)






















  • No labels