Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

S.No.Test case IDOther component involvedTest caseStatusRemarks
1.POLICY_PCIMS_PAIRWISE_001PCI-MS(Initial) Configuration of PCI-MSIn progressTested
2.POLICY_PCIMS_PAIRWISE_002PCI-MSSending PCI changes to Policy (control loop)Not testedTested

3.
Anchor
Policy-SDNR-pairwise-testing
Policy-SDNR-pairwise-testing
Policy↔SDN-R pairwise testing

S.No.Test case IDOther component involvedTest caseStatusRemarks
1.POLICY_SDNR_PAIRWISE_001SDN-RSending PCI changes to SDN-R (control loop)In ProgressSDN-R implementation to receive DMaaP message tbdNot tested
2.POLICY_SDNR_PAIRWISE_002SDN-RHandling response to PCI change recommendationNot testedDependent on previous test case

4. OOF↔SDN-R pairwise testing

...

S.No.Test case IDComponentsTest caseStatusRemarks
1.OOF_PCIMS_PAIRWISE_001OOF, PCI-MSRequest for PCI optimizationNot testedTested
2.OOF_PCIMS_PAIRWISE_002OOF, PCI-MSPCI optimization resultNot testedTested

6. SDN-R↔PCI-MS pairwise testing

S.No.Test case IDComponentsTest caseStatusRemarks
1.SDNR_PCIMS_PAIRWISE_001SDN-R, PCI-MS

Handle neighbor list change notification from SDN-R

In progressGenerated a DMaaP notification and testing PCI-MS, real SDN-R not yet integrated
2.SDNR_PCIMS_PAIRWISE_002SDN-R, PCI-MSConfig DB API access (for getNbrList)In progressTested
3.SDNR_PCIMS_PAIRWISE_003SDN-R, PCI-MSConfig DB API access (for pnfName)Not testedTested

7. SDN-R↔RAN pairwise testing

S.No.Test case IDComponentsTest caseStatusRemarks
1.SDNR_RAN_PAIRWISE_001SDN-R, RAN (Sim)

Connecting SDN-R with RAN (Sim) (netconf servers)

In progressTesting with a netconf client, not yet started with real SDN-R instance due to netconf notification handling issues
2.SDNR_RAN_PAIRWISE_002SDN-R, RAN (Sim)

Receiving neighbor list change notification from RAN

Not testedSDN-R notification handling tbd
3.SDNR_RAN_PAIRWISE_003SDN-R, RAN (Sim)Send netconf message(s) to RAN-Sim with the PCI changesNot testedSDN-R notification handling tbd
4.SDNR_RAN_PAIRWISE_004SDN-R, RAN (Sim)Successful update of PCI valuesNot testedSDN-R notification handling tbd



Test Case ID

Anchor
POLICY_OOF_PAIRWISE_001
POLICY_OOF_PAIRWISE_001
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

  1. Bring up the OOF using the installation steps.
  2. Check the OOF database to see the contents of the OOF config policy for PCI optimization use case.
  1. OOF comes online and the database and local datastructures for PCI optimization use case are initialized correctly.
  2. 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

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

...