...
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 access (for getNbrList) | Not tested |
OOF_PCIMS_PAIRWISE_001 | OOF, PCI-MS | Request for PCI optimization | Not tested |
OOF_SDNR_PAIRWISE_001 | OOF, SDN-R | Config DB API access (for getNbrList) | Not tested |
OOF_PCIMS_PAIRWISE_002 | OOF, PCI-MS | PCI optimization result | Not tested | Test Case ID | anchor
SDNR_PCIMS_PAIRWISE_003 | SDN-R, PCI-MS | Config DB API access (for pnfName) | Not tested |
POLICY_ | |||
PCIMS_PAIRWISE_ | |||
002 | Policy, PCI-MS | Sending DMaaP message by PCI-MS to Policy | Not tested |
POLICY_ | |||
SDNR_PAIRWISE_001 | Policy, SDN-R | Invoking control loop in Policy | Not tested |
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 | 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 | 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 | 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 | 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) 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 |