...
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 | |
Test Case ID |
POLICY_ |
PCIMS_PAIRWISE_001 | |
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 | SDNR_RAN_PAIRWISE_002 | ||||||
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 | SDNR_RAN_PAIRWISE_002 | ||||||
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 | SDNR_PCIMSOOF_PCI_PAIRWISE_002 | ||||||
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. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
...