Notes
- These test cases are for the POC. Only OOF-SDNR pairwsie test is part of integration testing for Casablanca and that has been competed.
- Policy pairwise testing status for Casablanca is tracked at Policy Pair Wise Testing for Casablanca Release.
- OOF testing status for Casablanca is tracked at https://wiki.onap.org/pages/viewpage.action?pageId=41420882.
Pair-wise Testing
1.
Anchor | ||||
---|---|---|---|---|
|
S.No. | Test case ID | Other component involved | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | POLICY_OOF_PAIRWISE_001 | OOF | (Initial) Configuration of OOF | Tested | Tested with templates for PCI based policies, there is an issue with policy portal to upload the config policies (https://jira.onap.org/browse/POLICY-1206) |
2.
Anchor | ||||
---|---|---|---|---|
|
S.No. | Test case ID | Other component involved | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | POLICY_PCIMS_PAIRWISE_001 | PCI-MS | (Initial) Configuration of PCI-MS | Tested | |
2. | POLICY_PCIMS_PAIRWISE_002 | PCI-MS | Sending PCI changes to Policy (control loop) | Tested |
3.
Anchor | ||||
---|---|---|---|---|
|
S.No. | Test case ID | Other component involved | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | POLICY_SDNR_PAIRWISE_001 | SDN-R | Sending PCI changes to SDN-R (control loop) | In Progress | SDN-R implementation to receive DMaaP message tbd |
2. | POLICY_SDNR_PAIRWISE_002 | SDN-R | Handling response to PCI change recommendation | Not tested | Dependent on previous test case |
4. OOF↔SDN-R pairwise testing
S.No. | Test case ID | Components | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | OOF_SDNR_PAIRWISE_001 | OOF, SDN-R | Config DB API access (for getNbrList) | Tested | In Windriver lab against ConfigDB API, using simulated ConfigDB |
5. OOF↔PCI-MS pairwise testing
S.No. | Test case ID | Components | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | OOF_PCIMS_PAIRWISE_001 | OOF, PCI-MS | Request for PCI optimization | Tested | |
2. | OOF_PCIMS_PAIRWISE_002 | OOF, PCI-MS | PCI optimization result | Tested |
6. SDN-R↔PCI-MS pairwise testing
S.No. | Test case ID | Components | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | SDNR_PCIMS_PAIRWISE_001 | SDN-R, PCI-MS | Handle neighbor list change notification from SDN-R | In progress | Generated a DMaaP notification and testing PCI-MS, real SDN-R not yet integrated |
2. | SDNR_PCIMS_PAIRWISE_002 | SDN-R, PCI-MS | Config DB API access (for getNbrList) | Tested | |
3. | SDNR_PCIMS_PAIRWISE_003 | SDN-R, PCI-MS | Config DB API access (for pnfName) | Tested |
7. SDN-R↔RAN pairwise testing
S.No. | Test case ID | Components | Test case | Status | Remarks |
---|---|---|---|---|---|
1. | SDNR_RAN_PAIRWISE_001 | SDN-R, RAN (Sim) | Connecting SDN-R with RAN (Sim) (netconf servers) | In progress | Testing with a netconf client, not yet started with real SDN-R instance due to netconf notification handling issues |
2. | SDNR_RAN_PAIRWISE_002 | SDN-R, RAN (Sim) | Receiving neighbor list change notification from RAN | Not tested | SDN-R notification handling tbd |
3. | SDNR_RAN_PAIRWISE_003 | SDN-R, RAN (Sim) | Send netconf message(s) to RAN-Sim with the PCI changes | Not tested | SDN-R notification handling tbd |
4. | SDNR_RAN_PAIRWISE_004 | SDN-R, RAN (Sim) | Successful update of PCI values | Not tested | SDN-R notification handling tbd |
Test Case ID |
| ||||||
Test Case Name | Configuration of OOF | ||||||
Description | Test if the OOF is onboarded and configuration policies are fetched and loaded correctly (Step 1c of flow) | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) Policy module is onboarded. (b) Config policies related to OOF are provisioned properly in Policy module. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Configuration of PCI-MS | ||||||
Description | Test if the PCI-MS is onboarded and configuration policies are fetched and loaded correctly (Step 1b of flow) | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) Policy module is onboarded. (b) Config policies related to PCI-MS are provisioned properly in Policy module. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Sending DMaaP message to Policy module with the PCI changes. | ||||||
Description | Sending of DMaaP message (Topic: DCAE_EVENT_OUTPUT) by PCI-MS to Policy with the PCI changes | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) PCI-MS has fetched the config policies successfully from the Policy module. (b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file. (c) SDNR_PCIMS_PAIRWISE_003 has been completed (if not, write some stub code in PCI-MS to send the DMaaP message). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Invoking the control loop in Policy | ||||||
Description | Invoking the control loop and sending DMaaP message to SDN-R with the PCI changes. | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) Control Loop Policy is successfully loaded and configured in Policy module. (b) SDN-R is initialized, configured and connected to the RAN-Sim (netconf servers). (c) POLICY_PCIMS_PAIRWISE_002 has been completed. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Acknowledgement of successful update of PCI values. | ||||||
Description | RAN-Sim sending success response to netconf (edit-config) message(s) to SDN-R. | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) SDN-R is initialized, configured and connected to the RAN-Sim (netconf servers). (b) RAN-Sim is initialized and configured properly. (d) POLICY_SDNR_PAIRWISE_001 has been completed (also preferably, SDNR_RAN_PAIRWISE_004 should be completed). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker M |
Test Case ID |
| ||||||
Test Case Name | Config DB API access by OOF | ||||||
Description | Accessing Config DB APIs by OOF for PCI optimization algorithm execution | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) OOF has fetched the config policies successfully from the Policy module. (b) OOF_PCIMS_PAIRWISE_001 has been completed successfully (otherwise some dummy code for REST API call to Config DB to be written in OOF). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Request for PCI optimization | ||||||
Description | Request for PCI optimization algorithm to be executed by OOF to address PCI collision/confusion | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) PCI-MS has fetched the config policies successfully from the Policy module. (b) (SDN-R) Config DB should be populated with the details of the cells in the network. (c) SDNR_PCIMS_PAIRWISE_002 has been completed (otherwise some dummy code for REST API call to OOF to be written in PCI-MS). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | PCI optimization result reported by OOF to PCI-MS | ||||||
Description | PCI optimization result sent by OOF to PCI-MS via REST call. | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) OOF has fetched the config policies successfully from the Policy module. (b) (SDN-R) Config DB should be populated with the details of the cells in the network. (c) OOF_PCIMS_PAIRWISE_001 has been completed (otherwise some dummy code for REST API call to PCI-MS to be written in OOF). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Handle neighbor list change notification from SDN-R | ||||||
Description | Handle neighbor list change notification from SDN-R and form a cell cluster. | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) PCI-MS has fetched the config policies successfully from the Policy module. (b) SDNR_RAN_PAIRWISE_002 has been completed, and neighbor list change notification has been received by SDN-R. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Config DB API access | ||||||
Description | Test the working of Config DB APIs | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) PCI-MS has fetched the config policies successfully from the Policy module. (b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file. (c) SDNR_PCIMS_PAIRWISE_001 has been completed (if not, write some stub code in PCI-MS to do the ConfigDB query after initialization). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Config DB API access | ||||||
Description | Test the working of Config DB APIs (getPnfName) | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) PCI-MS has fetched the config policies successfully from the Policy module. (b) (SDN-R) Config DB should be populated with the details of the cells in the network using the RAN initialization file. (c) OOF_PCIMS_PAIRWISE_002 has been completed (if not, write some stub code in PCI-MS to do the ConfigDB query). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Connecting SDN-R with RAN (netconf servers) | ||||||
Description | Establish connection between SDN-R and RAN | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) SDN-R is up and running (b) RAN initialization file is available | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Receiving neighbor list change notification from RAN | ||||||
Description | Receive a neighbor list change notification from RAN and act upon it by sending a DMaaP notification to PCI-MS (after storing relevant info in Config DB). | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) SDN-R is up and running (b) RAN is connected to SDN-R (c) GUI shows RAN topology view properly, GUI is able to show the details of a particular cell (PCI, neighbor list, CellId). | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID |
| ||||||
Test Case Name | Sending message(s) to RAN-Sim to update PCI values | ||||||
Description | SDN-R sending netconf (edit-config) message(s) to RAN-Sim to update the PCI values | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) SDN-R is initialized, configured and connected to the RAN-Sim (netconf servers). (b) RAN-Sim is initialized and configured properly. (c) POLICY_SDNR_PAIRWISE_001 has been completed. (d) SDNR_RAN_PAIRWISE_002 has been completed. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker M |
Test Case ID |
| ||||||
Test Case Name | Acknowledgement of successful update of PCI values. | ||||||
Description | RAN-Sim sending success response to netconf (edit-config) message(s) to SDN-R. | ||||||
Release | Casablanca | ||||||
Pre-conditions | (a) SDN-R is initialized, configured and connected to the RAN-Sim (netconf servers). (b) RAN-Sim is initialized and configured properly. (d) SDNR_RAN_PAIRWISE_003 has been completed. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker M |
Integration Testing
Integration Testing
...
Ensure that PCI-Handler-MS applies configuration policies, processes configuration changes in steps 4a,4b, and sends a message to OO
(Pre-requisite is step 2 is tested)
...
#
...
Test Case
...
Status
...
1
...
Perform necessary initialization of RAN Simulator, OOF, PCI-MS and SDN-R
...
...
2
...
Ensure that the unauthenticated.VES_NOTIFICATION_OUTPUTtopic is present once it received "File Ready" VES notification from VES Collector.
...
...
3
...
Ensure that the Data File Collector starts to download the xml PM file(s) from the simulated xNF once it receives the 'FileReady' VES event via the VES collector.
...
...
4
...
Ensure that the PM xml file(s) are published to the Data Router.
...
...
5
...
Ensure that a simulated File Consumer is able to subscribe and consume the PM file(s) from the Data Router.
...
- Initialization (RAN-Sim, GUI, OOF, PCI-MS, Policy, SDN-R, Config DB)
- Neighbor list change notification handling (via RAN-Sim GUI)
- Successful application of PCI changes
- Advanced scenarios
- More than 1 notification required for triggering OOF
- Neighbor list change when OOF is executing PCI optimization algorithm
- Neighbor list change for more than 1 cluster (is this relevant for PoC?)
- ???