...
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| # | Use Case Functional Requirement Nonfunctional Requirement | Test Cases | Lab | Integration Test Lead | Status (remaining days of effort) | Video URL | Detailed Test Status | Quick Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Model Driven Control Loop Design | (vDNS is part of scale out use case below #10) | Intel / Windriver |
on both SNAPSHOT and Release versions | Instantiate working for both. Closed Loop in progress vFW to VES : PASS VES to TCA : PASS TCA to Policy : Default policy needs to be changed : targetType: VM Policy to APPC: PASS with SNAPSHOT APPC to vPNG: PASS with SNAPSHOT. vFW: PASS. Waiting to regression test release containers
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | Use Case: Residential Broadband vCPE (Approved) | vCPE Integration Test Case | Intel / Windriver |
| vCPE (Heat) - Dublin Test Status | Done VNF onboarding, service design for infra and rescust, model distribution, infra and customer services instantiation Closed loop tests have done VNF event generation, vescollector, DCAE(TCA), Policy and APPC
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | vCPE with TOSCA | vCPE(tosca) with HPA - Integration test cases | Intel / Windriver |
|
|
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 4 | 5G - Realtime PM and High Volume Stream Data Collection | 5G - Real Time PM and High Volume Stream Data Collection - Integration Test Cases | Intel / Windriver |
| 5G - Real Time PM and High Volume Stream Data Collection - Test Status Dublin | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 5 | 5G - PNF PnP | 5G - PNF PnP - Integration Test Cases | Intel / Windriver | 20.05.2019
03.06.2019
| Dublin Release Integration Testing Status | There is no possibility to distribute model for PNF due SDNC issues (lack of one table in SDNC db)
After applying WO from
Failed on Release lab WindRiver SB02 bug
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| 6 |
| 5G - Bulk PM | 5G - Bulk PM - Test Status | Intel / Windriver SB-02 |
| |||||||||||
| 7 | 5G - Configuration with NETCONF | 5G - PNF Configuration via Netconf - Test Status | Intel/ Windriver |
|
|
|
E2E done in Ericsson lab.
E2E ongoing in windriver.This test is in continuity of PNF PnP test case which is at no. 5. Completed this test in Ericsson Local Lab with PnP PNF on-boarding. Starting to test it in Windriver Lab. Few Issues impacting this test are:
Root cause of the exception is handled in jira,
Due to this issue SDNC-756 not able to deploy service using VID, using a WA to do that stated in the below bug.
Unable to distribute the service.
Existing Blueprints failing due to a bug in CDS Config Deploy
|
| 8 | 5G - Preonboarding/Onboarding - Test Status | Intel / Windriver | PNF Preonboarding (VNF SDK): PNF Onboarding (SDC): | PNF Onboarding (SDC)
PNF Preonboarding (VNF SDK):
|
|
logged medium level bug | 5G - PNF E2E Pre-Onboarding & Onboarding Integration Test Status | Successfully completed PNF Onboarding testing in Ericsson and WindRiver labs. Manually applied workaround to db for
Very old images used for VNFSDK and CLI in ONAP DUBLIN:
Instruction in read the docks fro offline VTP platform setup is not correct
Preonborading bugs for validation rules found by Dermot Melia
|
5G - OOF and PCI - Integration Test Cases
| Status | ||||
|---|---|---|---|---|
|
Integration testing in Windriver lab
|
|
|
|
|
|
| 9 | 5G - OOF and PCI | 5G - OOF and PCI - Integration Test Cases | Windriver |
| Integration Testing | Integration testing in Windriver lab. IT#017 test case will be performed again as soon as CCSDK-1399 and CCSDK-1400 are delivered
|
|
1 test case involving SDN-R could not be completed (IT#017). The following Jiras were raised related to this test case, and the code fixes are delivered.
|
|
|
|
1 test case involving SDN-R could not be completed (IT#017). The following Jiras were raised related to this test case, and the code fixes are delivered.
The DMaaP listener docker with the code fix is not yet deployed in SB-00 where the testing is done. The code, fix however, is already merged on to Dublin and Master branches. So, once the latest docker is deployed, we will continue and complete the test case either at Windriver.
| ||||||||||||||||||||||
| 10 | Scale Out | Scale Out - Integration Test Cases and Status | Intel / Windriver |
|
| colour | Red |
|---|---|
| title | Progressing 90% |
Still having a problem with VID for manual Scale Out.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Scale Out with manual trigger has been tested by directly calling SO instead of using VID | ||||||||||
| 11 | CCVPN | CCVPN Integration Test Cases | CMCC |
|
Dublin Scope to be reviewed in alignment with what it is currently certified REDEFINED to match the scope of completed testing - Former user (Deleted) | CCVPN Test Status |
The CMCC lab had a relocation plan at the beginning of this year. But for special reasons, the plan is now ahead of schedule. this week all equipment has to be powered off. For this particular reason, we can't continue our tests. so we plan to test the remaining test cases in the next release, | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 12 | HPA vFW/vDNS | vFW/vDNS HPA Testing(Test Plan 1 inHPA & Cloud Agnostic Intent - R3 Test Plan) | Intel / Windriver |
| vFW/vDNS with HPA Integration Test Status (Dublin) |
need to remove oof_directives from the user_directives parameter | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 | Change Management - Flexible Designer & Orchestrator | Steps: 1) Designing custom workflows with Workflow Designer 2) Distributing custom workflows to SO 3) Deploying the custom workflow in SO 4) Sending workflow metadata to VID 5) Triggering custom workflow execution from VID 6) Executing custom workflows in SO | Intel / Windriver |
|
|
| SDC build discrepancy where Workflow Designer does not work in ONAP env. but does in SDC local env.
Distribution of BPMN from SDC to SO is now resolved!!! We now have an issue on auto deploy of activity specs to SDC - SO-1996 (the specs get created, but SDC returns 201 instead of 200 specified in the Wiki, SO made a change to accept 201 too), it is merged and is in today's daily build (6/6/19) Testing complete on the user-defined workflow with setting/unsetting in-maint flag. Testing for in-place software upgrade would be done in El Alto | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 | Steps: 1) Creating VNF profile using CDT 2) Designing custom workflows with Workflow Designer 3) Distributing custom workflows to SO 4) Deploying the custom workflow in SO 5) Sending workflow metadata to VID 6) Triggering custom workflow execution from VID 7) Executing custom workflows in SO | Intel / Windriver |
|
Note: SO workflow cannot be build with WorkFlow designer - we need it for workflow development. It is taken decision to move building workflow in SO/WorkFlow designer in El Alto and to build DT workflow in Dublin outside of SO - with REST APIs of OOF, APPC and AAI. As a consequence we built use case workflow in Python | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 15 | Change Management - 5G PNG Software Upgrade | Change Management - 5G PNF Software Upgrade Integration Test Status | Intel / Windriver |
| Completed this test in Huawei Local Lab. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 16 | Change Management - Schedule Optimization | Intel / Windriver |
| Completed!! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 17 | BBS Broadband Service Use Case (Dublin) | BBS Use Case Tracking (Dublin Release)#Testing | BBS Swisscom Lab |
- Phase 1: Service creation and activation + Nomadic ONT (Test cases #[A-D])
- Phase 2 (moved to El Alto): E2E Service Termination (Test cases #[E]). Jira SO-1994 Note: POLICY-1835 and POLICY-1831 |
should be |
included in Dublin | BBS Integration Test Cases |
https://gerrit.onap.org/r/#/c/87497/ https://gerrit.onap.org/r/#/c/so/+/88935/
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 18 | VSP Compliance Check within SDC (Dublin) - Phase 1 | VSP Compliance Check within SDC - Integration Test Plan | Vodafone |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 19 | K8S based Cloud Region Support - vFW Use case | Deploy vFW Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud | intel / Windriver |
|
Work around is found for R4. Actual fix will be made in R5. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 20 | K8S based Cloud Region Support - EdgeXFoundry Use case | Deploy EdgeXFoundry Helm Chart using Multicloud K8s Plugin in Kubernetes Cloud | Intel/ Windriver |
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 | 5G: Network Slicing Modeling | Amdocs | Borislav Glozman |
| No integration testing is expected. A potential model of network slice was presented using SDC features. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 | Consistent ID of a Cloud Region | Windriver | Bin Yang |
|
|
| Use Case Tracking in Dublin Release |
Creating VF Moduel failed with GR-API and selecting CloudRegion3(CloudOwner3) (other than the default one): I am not sure which project (VID/SO/SDNC) should take care of this issue, sent email to discuss email list and wait for response Details can be found: Deploy vLB to Multiple Cloud Regions | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 23 | Modularity |
| |||||||||||||||||||||||||||||||||||||||||||||||||||
| 24 | ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM |
|
Create+instantiation is completed Note: Termination+Deletion is almost but has a minor issue, it will be done in El Alto | Due to lack of SDC SOL004 VNF support in Dublin, automated CSIT testing has been deferred to El Alto under
In Dublin, manual-based (sending REST requests) test has been done for SO/VNFM Adapter to test VNFM Adapter functionalities. Currently, VNFM Adapter API function testing with VNFM Simulator is completed, and the team is working on the SO workflows (which invoking VNFM Adapter) testing. VNF creation+ instantiation testing is 100% Terminate+Delete integration testing will be done in El Alto Dublin test cases, SO VNFM Adapter Test Case | |||||||||||||||
| 25 | Improve our E2E Process Automation |
|
|
| VIDEO URL: |
E2E Automation vDNS w/ CDS Use Case - ONAP-03-Run Time- Video Demo for vDNS CDS Dublin | E2E Automation Testing Status with CDS | Dublin Highest Bugs:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 26 | S3P - Footprint Optimization (Integration with Alpine) |
| No specific tests. Default containers used in OOM are optimized. |
Arm testing on
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 | Component/memory optimization: Ongoing Assessment |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 28 | Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB |
AAI - PASS SDC - PASS SO - PASS SDNC - PASS | Integration testing underway to validate. | AAI and SDC using Shared Cassandra delivered. SO and SDNC using Shared Mariadb-Galera delivered. PASS if application installs and functions on shared datastores. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 29 | S3P- Geo-Redundancy |
| Basically the update is both OOF and Portal are successfully using MUSIC in Dublin (E2E testing has no MUSIC-related issue now) and their code exercise MUSIC geo-redundancy across the US more or less every day in production. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 | SOL 004 (VNF Package Security) | 5G - Preonboarding/Onboarding - Test Status | Ericsson, Intel / Windriver | SDC: COMPLETED
|
|
logged medium level bug | 5G - PNF E2E Pre-Onboarding & Onboarding Integration Test Status | Note: SOL004 test cases are an integral part of the 5G PNF pre-onboarding/onboarding test cases. For both SDC and VNF SDK following applies: VNF SDK:
Another bug has been found:
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| 31 | xNF communication security enhancements. | xNF communication security enhancements - Tests Description and Status |
| xNF communication security enhancements - Tests Description and Status |
| |||||||||||||||||||||||||||||||||||||||||||||||
| 32 | Locale/Internationalization language support | Tao Shen |
|
|
|
| |||||||||||||||||||||||||||
| 33 | Angular 6 Upgrade of ONAP Portal and SDK | Portal R4 Dublin Functional Test Cases (includes Angular 6 upgrade tests) | Intel / Windriver |
| Angular 6 Upgrade tests are run locally by the test lead (Sireesh Chintamani (Deactivated) ) on the portal/sdk screens after pairwise testing is passed on SDK - Portal Pair Wise Testing for Dublin Release |
| ||||||||||||||||||||||
| 34 | HPA vIPsec | vIPsec HPA testing | Intel / Windriver | ruoyu.ying |
| Need double check for last step on vf module creation | ||||||||||||||||||||||
| 35 | Health Checks for PODS | Percentage coverage of Health Checks for Running PODS | Integration | Reporting only for Dublin
| 55% Yes 22% No 23% Still being researched |
| ||||||||||||||||||||||
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...