Content Comparison

...

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

Test Case ID

 Anchor
P1
P1
POLICY_OOF_PAIRWISE_001

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

Steps

Expected Result

Bring up the OOF using the installation steps.
Check the OOF database to see the contents of the OOF config policy for PCI optimization use case.

OOF comes online and the database and local datastructures for PCI optimization use case are initialized correctly.
Config-policy is correctly fetched and stored in the OOF DB.
Sample config policy contents are given below:
ALGO_CATEGORY:OOF-PCI-OPTIMIZATION
PCI_OPTMIZATION_ALGO_NAME:OOF-PCI-OPTIMIZATION-LEVEL1
PCI_OPTIMIZATION_NW_CONSTRAINT:MAX5PCICHANGESONLY
PCI_OPTIMIZATION_PRIORITY: 2
PCI_OPTIMIZATION_TIME_CONSTRAINT:NONE

Conclusion (Pass /Fail)

Testing Lab

...

Versions Compared