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

Compare with Current View Page History

« Previous Version 15 Next »

  • There are two onap instances set up in the WindRiver lab with tenant names: Integration-Onboarding and Integration-ClosedLoop
    • Integration-onboarding should be used for model onboarding , distribution and instantiation pair wise tests: aaf, dmapp, sdc, portal, aai, so, sdnc, vid, multi-vim, etc.
    • Integration-closedloop should be used for closed loop (vfwcl is deployed)  : aaf,  dmaap, aai, clamp , dcae, policy , appc, etc
  • This page should be filled by PTLs as "self-grade" check list.


Project NameProject Tech. Lead

Health Check

(OOM)

Health Check rating

(to identify which health check tests need to be upgraded)

Pair Wise Testing ChecklistMaturity

Ready For Test

(Integration Team)


1A & AIWilliam Reehil


A&AI Pairwise Testing for Guilin Release


2







3







4







5Common Controller SDK Dan Timoney

N/A - CCSDK does not have direct interfaces of its own. It is tested as part of its clients (APP-C and SDNC)


6







7







8







9ONAP CLI

CLI Pair Wise Testing for G Release


10VNFSDK

VNFSDK Pair Wise Testing for G Release


11







12







13







14







15ModelingHui Deng

Modeling Pair Wise Testing for Guilin Release


16







17







18Microservices BusHuabingZhao

As an infrastructure for microservice communication, MSB has been tested in other pair wise tests.


19Optimization Framework Projectkrishna moorthy

OOF Pair Wise Testing for Guilin Release


20ONAP Usecase UI Project Proposal

Usecase UI Pair Wise Testing for Guilin Release


21Policy Framework Project ProposalJim Hahn

POLICY Pair Wise Testing for Guilin Release


22







23







24







25







26VF-C: Virtual Function ControllerYuanhong Deng

VFC Pair Wise Testing for Guilin Release


27







28







29







30










  • No labels