Versions Compared

Old Version 25

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version Current

changes.mady.by.user Swaminathan Seetharaman

Saved on

Key

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

Notes

  1. These test cases are for the POC. Only OOF-SDNR pairwsie test is part of integration testing for Casablanca and that has been competed.
  2. Policy pairwise testing status for Casablanca is tracked at Policy Pair Wise Testing for Casablanca Release.
  3. OOF testing status for Casablanca is tracked at https://wiki

Pair-wise Testing

1. Policy↔OOF Pair-wise testing

...

  1. .onap.org/

...

  1. pages/viewpage.action?pageId=41420882.

Pair-wise Testing

1. 

Anchor
Policy-OOF-pairwise-testing
Policy-OOF-pairwise-testing
Policy↔OOF Pair-wise

...

testing

S.No.Test case IDOther component involvedTest caseStatusRemarks
1.POLICY_PCIMSOOF_PAIRWISE_001PCI-MSOOF(Initial) Configuration of PCI-MSIn progress2.POLICY_PCIMS_PAIRWISE_002PCI-MSSending PCI changes to Policy (control loop)Not tested

...

OOFTestedTested with templates for PCI based policies, there is an issue with policy portal to upload the config policies (https://jira.onap.org/browse/POLICY-1206)

2.
Anchor
Policy-PCIMS-pairwise-testing
Policy-PCIMS-pairwise-testing
Policy↔PCI-MS pairwise testing

SDNRSDNRNot tested
S.No.Test case IDOther component involvedTest caseStatusRemarks
1.POLICY_PCIMS_PAIRWISE_001PCI-Sending PCI changes to SDN-R (control loop)MS(Initial) Configuration of PCI-MSTested
2.POLICY_SDNRPCIMS_PAIRWISE_002SDNPCI-RHandling response to PCI change recommendationNot tested

...

MSSending PCI changes to Policy (control loop)Tested

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

S.No.Test case IDComponentsOther component involvedTest caseStatusRemarks
1.OOFPOLICY_SDNR_PAIRWISE_001OOF, SDN-RSending PCI changes to SDN-R (control loop)In ProgressSDN-R implementation to receive DMaaP message tbd
2.POLICY_SDNR_PAIRWISE_002SDN-RHandling response to PCI change recommendationConfig DB API access (for getNbrList)Not tested

...

Dependent on previous test case

4. OOF↔SDN-R pairwise testing

PCIMS PCI
S.No.Test case IDComponentsTest caseStatusRemarks
1.OOF_SDNR_PAIRWISE_001OOF, SDN-RConfig DB API access (for getNbrList)TestedIn Windriver lab against ConfigDB API, using simulated ConfigDB

5. OOF↔PCI-MS pairwise testing

MS
S.No.Test case IDComponentsTest caseStatusRemarks
1.OOF_PCIMS_PAIRWISE_001OOF, PCI-MSRequest for PCI optimizationTestedRequest for PCI optimizationNot tested
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)Not testedTested
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

...

Test Case ID

Anchor
SDNR_RAN_PAIRWISE_004
SDNR_RAN_PAIRWISE_004
SDNR_RAN_PAIRWISE_004

Test Case Name

Acknowledgement of successful update of PCI values.


Description

RAN-Sim sending success response to netconf (edit-config) message(s) to SDN-R.

Release

Casablanca

Pre-conditions

(a) SDN-R is initialized, configured and connected to the RAN-Sim (netconf servers).

(b) RAN-Sim is initialized and configured properly.

(d) SDNR_RAN_PAIRWISE_003 has been completed.

Testing Steps


Steps

Expected Result

  1. RAN-Sim sends a success response to SDN-R upon receipt of netconf edit-config message from SDN-R.
  2. Upon receipt of this response, SDN-R prepares a DMaaP message (Topic: SDNR-CL-RSP)
  1. Policy receives the DMaaP message, and the Control Loop status can be viewed in the logs.


Conclusion (Pass /Fail)


Testing Lab

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


Integration Testing

...

  1. Initialization (RAN-Sim, GUI, OOF, PCI-MS, Policy, SDN-R, Config DB)
  2. Neighbor list change notification handling (via RAN-Sim GUI)
  3. Application Successful application of PCI changes
  4. Advance Advanced scenarios
    1. More than 1 notification required for triggering OOF
    2. Neighbor list change when OOF is executing PCI optimization algorithm
    3. Neighbor list change for more than 1 cluster (is this relevant for PoC?)
    4. ???

...

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)

...