Versions Compared

Old Version 13

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version 14

changes.mady.by.user Swaminathan Seetharaman

Saved on

Key

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

...

#

Component(s)

Test Case

Status

Remarks

IT#001DCAE (SON Handler MS)SON Handler Micro-service successfully on-boarded on to DCAE

NOT YET TESTED


IT#002DCAE (SON Handler MS)SON Handler Micro-service's DB is up and the Micro-service is able to read/write data.

NOT YET TESTED


IT#003DCAE (SON Handler MS)SON Handler Micro-service is able to successfully fetch config policies from Consul.


NOT YET TESTED
IT#004OOF and PolicyOOF is able to successfully fetch config policy from Policy

NOT YET TESTED


IT#005DCAE (SON Handler MS)SON Handler Micro-service is able to successfully receive a message over DMaaP containing PM/FM data (from VES Collector)

NOT YET TESTED


IT#006

DCAE (SON Handler MS) and SDN-R

SON Handler Micro-service is able to successfully receive a message over DMaaP containing neighbor list update (from SDN-R)

NOT YET TESTED


IT#007DCAE (SON Handler MS) and Config DBSON Handler Micro-service is able to successfully fetch neighbor list details from Config DB.

NOT YET TESTED


IT#008DCAE (SON Handler MS) and OOFSON Handler Micro-service invokes REST API of OOF for PCI optimization

NOT YET TESTED


IT#009OOF and Config DBOOF is able to obtain relevant neighbor list information for optimization algorithm from ConfigDB (REST API)

NOT YET TESTED


IT#010DCAE (SON Handler MS) and OOFSON Handler Micro-service receives optimization result from OOF (via callback URL) and sends response

NOT YET TESTED


IT#011DCAE (SON Handler MS) and Config DBSON Handler Micro-service is able to successfully fetch PNF details from Config DB

NOT YET TESTED


IT#012DCAE (SON Handler MS) and PolicySON Handler Micro-service is able to send PCI/neighbor list updates via DMaaP to Policy

NOT YET TESTED


IT#013Policy and SDN-RPolicy is able to successfully send a DMaaP message (to SDN-R) with PCI/neighbor list updates.

NOT YET TESTED


IT#014Policy and SDN-RPolicy is able to successfully receive a DMaaP message (fromSDNfrom SDN-R) with PCI/neighbor list update response

NOT YET TESTED


IT#015DCAE (SON Handler MS) and PolicySON Handler Micro-service is able to receive PCI/neighbor list update response via DMaaP from Policy, process it and logs the results.

NOT YET TESTED


IT#016

DCAE (SON Handler MS)SON Handler Micro-service is able to process FM PM KPI data, store as needed, and apply rules to recommend removal of a neighbor relationship.

NOT YET TESTED


IT#017ConfigDBConfigDB established with Dublin enhancements (update single cell's details)

NOT YET TESTED


IT#018SDN-RSDN-R receives netconf notification, updates ConfigDB for neighbor list change

NOT YET TESTED


IT#019SDN-RUpon receiving message from Policy, SDN-R sends netconf message to RAN-Sim.

NOT YET TESTED


IT#020DCAE (VES Collector)VES Collector receives VES messages from RAN-Simulator

NOT YET TESTED


...

Test Case ID

IT#006

Test Case Name

SDN-R (DMaaP) interaction with SON-Handler MS

Description

SON Handler Micro-service is able to successfully receive a message over DMaaP containing neighbor list update from SDN-R

Release

Dublin

Pre-conditions

(a) DCAE platform is up and running

(b) SON-Handler MS is online

(c) DMaaP is up

Testing Steps


Steps

Expected Result

  1. Ensure relevant DMaaP topics are created (PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT), along with producer and consumers (using unauthenticated mode).
  2. Post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP either manually (or) using SDN-R (if online) and RAN-Simulator (or) using SDN-R (if online) and a netconf server
  1. SON-Handler MS receives the DMaaP PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT message and processes it - verified via logs and DB contents


Conclusion (Pass /Fail)


Testing Lab

Winlab

...

Test Case ID

IT#011

Test Case Name

Config DB interaction with SON-Handler MS for PNF details

Description


Release

Dublin

Pre-conditions

(a) DCAE platform is up and running

(b) SON-Handler MS is online

(c) OOF is online

(d) IT#010 is completed.

Testing Steps


Steps

Expected Result

  1. Post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP as done for IT#006 (or) post a DMaaP SEC_FAULT_OUTPUT message as done for IT#005. In either case, the message contents should be such that the number of resulting collisions/confusions should be more than the threshold for triggering OOF for PCI optimization.
    Note: In case this test case has to be done independent of OOF (i.e., IT#009 and IT#010), then upon completion of IT#008, the callback URL of SON-Handler MS can be invoked manually.
  1. SON-Handler MS receives PCI-optimization results via the callback URL (verified by SON-Handler MS triggers OOF for PCI optimization, and receives a response via the callback URL (verified by logs on OOF and SON-Handler MS sides).
  2. SON-Handler MS then invokes ConfigDB API for obtaining PNF names corresponding to the cells whose PCI values have been modified by OOF (verified by logs on Config DB and SON-Handler MS sides).


Conclusion (Pass /Fail)


Testing Lab

Winlab

...

Test Case ID

IT#012

Test Case Name

Config DB interaction with SON-Handler MS for PNF detailsinteraction with Policy (DMaaP) for PCI updates

Description

SON Handler Micro-service is able to send PCI/neighbor list updates via DMaaP to Policy

Release

Dublin

Pre-conditions

(a) DCAE platform is up and running

(b) SON-Handler MS is online

(c) OOF Policy is online

(d) IT#010 IT#011 is completed.

Testing Steps


Steps

Expected Result

  1. Ensure that the DMaaP topic DCAE_CL_OUTPUT is created, and producers/consumers are registered.
  2. Post a neighbor-list change notification message (topic: PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO_OUTPUT) on DMaaP as done for IT#006 (or) post a DMaaP SEC_FAULT_OUTPUT message as done for IT#005. In either case, the message contents should be such that the number of resulting collisions/confusions should be more than the threshold for triggering OOF for PCI optimization.
  1. SON-Handler MS triggers OOF for receives PCI optimization , and receives a response results via the callback URL (verified by logs on OOF and SON-Handler MS sides).
  2. SON-Handler MS then invokes ConfigDB API for obtaining PNF names corresponding to the cells whose PCI values have been modified by OOF (verified by logs on Config DB and SON-Handler MS sidesprepares and sends a DMaaP message (topic: DCAE_CL_OUTPUT) to Policy (verified by logs) for the required PCI changes.


Conclusion (Pass /Fail)


Testing Lab

Winlab


Test Case ID

IT#013

Test Case Name

Policy interaction with SDN-R (DMaaP) for PCI updates

Description

Policy is able to successfully send a DMaaP message (to SDN-R) with PCI/neighbor list updates.

Release

Dublin

Pre-conditions

(a) SON-Handler MS is online

(b) Policy is online


Testing Steps


Steps

Expected Result

  1. Ensure that the DMaaP topics DCAE_CL_OUTPUT and SDNR_CL is created, and producers/consumers are registered.
  2. Implement the steps for IT#012, if IT#012 is not completed, post a DMaaP message with topic DCAE_CL_OUTPUT containing details of PCI/neighbor list updates.
  1. Policy receives the DMaaP message with topic DCAE_CL_OUTPUT and invokes a control loop (verified by by checking active control loops).
  2. Policy then sends a DMaaP message to SDN-R with topic SDNR-CL containing the relevant contents received in the DCAE_CL_OUTPUT message (verified by logs).


Conclusion (Pass /Fail)


Testing Lab

Winlab


Test Case ID

IT#014

Test Case Name

Policy interaction with SDN-R (DMaaP) for PCI update response

Description

Policy is able to successfully receive a DMaaP message (from SDN-R) with PCI/neighbor list update response

Release

Dublin

Pre-conditions

(a) SON-Handler MS is online

(b) Policy is online


Testing Steps


Steps

Expected Result

  1. Ensure that the DMaaP topics DCAE_CL_OUTPUT and SDNR_CL is created, and producers/consumers are registered.
  2. Implement the steps for IT#012, if IT#012 is not completed, post a DMaaP message with topic DCAE_CL_OUTPUT containing details of PCI/neighbor list updates.
  1. Policy receives the DMaaP message with topic DCAE_CL_OUTPUT and invokes a control loop (verified by by checking active control loops).
  2. Policy then sends a DMaaP message to SDN-R with topic SDNR-CL containing the relevant contents received in the DCAE_CL_OUTPUT message (verified by logs).


Conclusion (Pass /Fail)


Testing Lab

Winlab

...