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.onap.org/pages/viewpage.action?pageId=41420882.

Pair-wise Testing

1.  Policy↔OOF Pair-wise testing

S.No.Test case IDOther component involvedTest caseStatusRemarks
1.POLICY_OOF_PAIRWISE_001OOF(Initial) Configuration of 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. Policy↔PCI-MS pairwise testing

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

3. 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 tbd
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_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

S.No.Test case IDComponentsTest caseStatusRemarks
1.OOF_PCIMS_PAIRWISE_001OOF, PCI-MSRequest for PCI optimizationTested
2.OOF_PCIMS_PAIRWISE_002OOF, PCI-MSPCI optimization resultTested

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)Tested
3.SDNR_PCIMS_PAIRWISE_003SDN-R, PCI-MSConfig DB API access (for pnfName)Tested

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

 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

 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

Steps

Expected Result

  1. Bring up the PCI-MS using the intallation steps.
  2. Check the PCI-MS database to see the contents of the PCI-MS config policy.
  1. PCI-MS comes online and the database and local datastructures (e.g., thread pool) are initialized correctly.
  2. Config-policy is correctly fetched and stored in the PCI-MS DB.
    Sample config policy contents are given below:
    PCI_NEIGHBOR_CHANGE_CLUSTER_TIMEOUT_IN_SECS:60
    PCI_MODCONFIG_POLICY_NAME:ControlLoop-vPCI-fb41f388-a5f2-11e8-98d0-529269fb1459 PCI_OPTMIZATION_ALGO_CATEGORY_IN_OOF:OOF-PCI-OPTIMIZATION
    PCI_SDNR_TARGET_NAME:SDNR

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 POLICY_PCIMS_PAIRWISE_002

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

Steps

Expected Result

  1. PCI-MS prepares the DMaaP message (with payload layout corresponding to the yang model) to be sent to Policy. It sends 1 message for each PNF.
  1. DMaaP message(s) is successfully received by Policy.

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 POLICY_SDNR_PAIRWISE_001

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) Control Loop Policy is successfully loaded and configured in Policy module.

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

(c) POLICY_PCIMS_PAIRWISE_002 has been completed.

Testing Steps

Steps

Expected Result

  1. Policy executes the control loop for PCI use case, and prepares the DMaaP message (topic - SDNR-CL, and payload layout taken from the DMaaP message received from PCI-MS) to the yang model) to be sent to Policy. It sends 1 message for each PNF.
  1. DMaaP message(s) is successfully received by SDN-R.

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 POLICY_SDNR_PAIRWISE_002

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) POLICY_SDNR_PAIRWISE_001 has been completed (also preferably, SDNR_RAN_PAIRWISE_004 should be completed).

Testing Steps

Steps

Expected Result

  1. SDN-R sends a DMaaP message (Topic: SDNR-CL-RSP) to Policy.
  1. Policy receives the DMaaP message, logs the contents, 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

Test Case ID

 OOF_SDNR_PAIRWISE_001

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

Steps

Expected Result

  1. After receiving a request for PCI optimization, OOF does a Config DB API query for getting the cellList (for a given networkID) and nbrList (for the set of cells sent in the PCI optimization request by PCI-MS).
  2. API contents are available in SDN-R impacts document.


SDN-R accepts the API and sends a response with the requested details.

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 OOF_PCI_PAIRWISE_001

Test Case Name

Request for PCI optimization

Description

Request for PCI optimization algorithm to be executed by OOF to address PCI collision/confusion

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.

(c) SDNR_PCIMS_PAIRWISE_002 has been completed (otherwise some dummy code for REST API call to OOF to be written in PCI-MS).

Testing Steps

Steps

Expected Result

  1. After receiving neighbor list change notification from SDN-R, PCI-MS processes it and determines OOF to be called.
  2. PCI-MS invokes the OOF PCI API (https://{host}:{port}/api/oof/v1/pci) for executing the PCI optimization.
    An example of the API contents is available in PCI Optimization API


OOF accepts the API request and sends a 200 OK response. An example of the (synchronous) response contents is available in PCI Optimization API

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 OOF_PCIMS_PAIRWISE_002

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

Steps

Expected Result

  1. After executing the PCI optimization algorithm, OOF invokes the callback API provided by the PCI-MS in the PCI optimization request API call. This API contains the results of the PCI optimization, i.e., the cells whose PCI values should be modified.
  2. An example of the API contents is available in PCI Optimization API

PCI-MS accepts the API and sends a 200 OK response.


Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 SDNR_PCIMS_PAIRWISE_001

Test Case Name

Handle neighbor list change notification from SDN-R


Description

Handle neighbor list change notification from SDN-R and form a cell cluster.

Release

Casablanca

Pre-conditions

(a) PCI-MS has fetched the config policies successfully from the Policy module.

(b) SDNR_RAN_PAIRWISE_002 has been completed, and neighbor list change notification has been received by SDN-R.

Testing Steps

Steps

Expected Result

  1. SDN-R sends a DMaaP message to PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO.
  2. DMaaP client in PCI-MS receives the message and forwards it to the PCI-MS core for further processing.

DMaaP message is received by Main thread of PCI-MS (verify by viewing logs).

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 SDNR_PCIMS_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.

(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

Steps

Expected Result

  1. PCI-MS does a query to the configDB using the getNbrList API to get the neighbor list.
  1. API query is successful and results match with DB contents. API contents are provided in SDN-R impacts document.

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 SDNR_PCIMS_PAIRWISE_003

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

Steps

Expected Result

  1. For the list of cells (whose PCI values should be changed) received from OOF in the PCI-optimization result, PCI-MS does a query to the configDB using the getPnfName for obtaining the PNF names for those cells whose PNF names are not available in its local DB.
  1. API query is successful and results match with DB contents. API details are provided in SDN-R impacts document.

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 SDNR_RAN_PAIRWISE_001

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

Steps

Expected Result

  1. Bring up the RAN-Simulator using the installation steps.
  2. Observe the connection status between SDN-R and netconf server(s)
  1. RAN-Simulator is successfully instantiated. GUI also shows the appropriate topology view.
  2. SDN-R and netconf servers are connected (RAN-Simulator sends a mount request (REST) for each netconf server.


Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 SDNR_RAN_PAIRWISE_002

Test Case Name

Receiving neighbor list change notification from RAN

Description

Receive a neighbor list change notification from RAN and act upon it by sending a DMaaP notification to PCI-MS (after storing relevant info in Config DB).

Release

Casablanca

Pre-conditions

(a) SDN-R is up and running

(b) RAN is connected to SDN-R

(c) GUI shows RAN topology view properly, GUI is able to show the details of a particular cell (PCI, neighbor list, CellId).

Testing Steps

Steps

Expected Result

  1. Modify the neighbor list of a cell (via RAN simulator GUI)
  2. The netconf server to which the cell is connected to sends a netconf notification to SDN-R.
  1. SDN-R updates the Config DB (neighbor list of the cell).
  2. SDN-R sends a DMaaP message to the PCI-MS with the topic PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO.

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 SDNR_RAN_PAIRWISE_003

Test Case Name

Sending message(s) to RAN-Sim to update PCI values

Description

SDN-R sending netconf (edit-config) message(s) to RAN-Sim to update the PCI values

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.

(c) POLICY_SDNR_PAIRWISE_001 has been completed.

(d) SDNR_RAN_PAIRWISE_002 has been completed.

Testing Steps

Steps

Expected Result

  1. Upon reception of the DMaaP message from Policy (topic: SDNR-CL) with the PCI changes, SDN-R prepares a netconf message (edit-config) and sends it to the RAN-Sim.
  1. RAN-Sim receives the message, and makes necessary updates to the PCI values (GUI reflects these changes).

Conclusion (Pass /Fail)


Testing Lab

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

Test Case ID

 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. Successful application of PCI changes
  4. 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. ???

  • No labels