Integration Testing
| Use case Step | Component(s) | Functionality | Test case | Impacted API | Status |
|---|---|---|---|---|---|
| 5 | PCI-Handler MS, OOF | Request for PCI optimization for network region. PCI-Handler MS invokes OOF for pre-defined workflow for PCI Optimization via REST API.This call includes data for the cell and the network reqion involved. | 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) | <API details> | Not tested |
| 6 | OOF, Policy | Fetch PCI optimization policies OOF fetches policies that specify how OOF will execute PCI optimization in response to PCI request for optimization | Ensure that OOF can fetch optimization policies from Policy, and applies it to invoke the appropriate solver module | <Policy API details> | Not tested |
| 7 | OOF, SDN-C | Fetch Config data for cells in the region. OOF fetches data for cells in network region from SDN-C | Ensure that OOF can query SDN-C to get required data (e.g. cellids, nbr_list, pci, lat/lon) from SDN-C Config DB | <Config DB API details> | Not tested |
| 9 | PCI-Handler MS, Policy | Recommended PCI configuration. PCI-Handler-MS provides PCI recommendation to Policy | Ensure that PCI-Handler-MS sends a message to Policy with recommendation for new PCI values for set of cells, along with reason for oprimization computation (RAN config change) | Not tested | |
| 10 | Policy, SDN-C | PCI Configuration decisions Policy sends message to SDN-C with instruction for configuration changes | Ensure that Policy applies operational policies to PCI change recommendation, and if appropriate, sends a message to SDN-C with instruction to change PCI value to set of cells | Not tested | |
Pair-wise testing
| Test case ID | Components | Test case | Status |
|---|---|---|---|
| POLICY_OOF_PAIRWISE_001 | Policy, OOF | (Initial) Configuration of OOF | Not tested |
| POLICY_PCIMS_PAIRWISE_001 | Policy, PCI-MS | (Initial) Configuration of PCI-MS | Not tested |
| SDNR_RAN_PAIRWISE_001 | SDN-R, RAN (Sim) | Connecting SDN-R with RAN (Sim) (netconf servers) | Not tested |
| SDNR_RAN_PAIRWISE_002 | SDN-R, RAN (Sim) | Receiving neighbor list change notification from RAN | Not tested |
| SDNR_PCIMS_PAIRWISE_001 | SDN-R, PCI-MS | Handle neighbor list change notification from SDN-R | Not tested |
| SDNR_PCIMS_PAIRWISE_002 | SDN-R, PCI-MS | Config DB API acces | Not tested |
| OOF_PCIMS_PAIRWISE_001 | OOF, PCI-MS | Request for PCI optimization | Not tested |
| OOF_SDNR_PAIRWISE_001 | OOF, SDN-R | Not tested | |
| OOF_PCIMS_PAIRWISE_002 | OOF, PCI-MS | Not tested | |
| OOF_ |
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 | 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 | 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 | 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 | 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 |