Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Integration Testing

Note: The OOF-PCI use case implementation and testing will be done at the Rutgers University Winlab ONAP Wireless Lab. Access is available to interested ONAP members.
Please see this page for details: Open Wireless Laboratory (OWL) at Wireless Information Network Laboratory (WINLAB)


Note: DMaaP should be setup for most of the test cases below.

#

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 and receives response from OOF

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


IT#016DCAE (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#017

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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED


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

NOT YET TESTED



Test Case ID

IT#001

Test Case Name

SON Handler Micro-service on-boarding

Description

SON Handler Micro-service is successfully on-boarded on to DCAE

Release

Dublin

Pre-conditions

(a) DCAE up and running

(b) DCAE CLI available

Testing Steps

Steps

Expected Result

  1. SON-Handler component spec validated.
  2. SON-Handler is brought up manually on DCAE.
  3. SON-Handler Blueprint validated successfully.
  4. DCAE is brought online.
  1. SON-Handler comes up online and is stable.

Conclusion (Pass /Fail)


Testing Lab

Winlab

Test Case ID

IT#002

Test Case Name

SON-Handler Micro-service DB on-boarding

Description

SON-Handler Micro-service's PG DB is up, and SON-Handler Micro-service is able to write data e.g., local configuration data and read it.

Release

Dublin

Pre-conditions

(a) SON-Handler MS is up and running

Testing Steps

Steps

Expected Result

  1. SON-Handler component and its DB is on-boarded on to DCAE.
  2. Local configurable attributes are written/read by SON-Handler MS (verified by viewing logs)
  1. Verify DB working by viewing SON-Handler MS logs.

Conclusion (Pass /Fail)


Testing Lab

Winlab

Test Case ID

IT#003

Test Case Name

Policy fetch by SON-Handler MS

Description

SON Handler Micro-service is able to successfully fetch config policies from Consul.

Release

Dublin

Pre-conditions

(a) SON-Handler MS is up and running

(b) DCAE Platform including Consul is up and running

Testing Steps

Steps

Expected Result

  1. Upload config policies for SON-Handler MS.
  2. SON-Handler MS should fetch the policies from Consul
  1. Verify Policy fetch and store via logs and checking in PG DB

Conclusion (Pass /Fail)


Testing Lab

Winlab

Test Case ID

IT#004

Test Case Name

Policy fetch by OOF

Description

OOF is able to successfully fetch the config policies from Policy

Release

Dublin

Pre-conditions

(a) Policy component is up and running

(b) Config policies related to OOF are provisioned in Policy component

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 (i.e., OOF should invoke Policy API to fetch the config policies).
  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

Winlab


Test Case ID

IT#005

Test Case Name

VES (DMaaP) interaction with SON-Handler MS

Description

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

Release

Dublin

Pre-conditions

(a) DCAE platform is up and running, VES is online

(b) SON-Handler MS is online

(c) DMaaP is up

Testing Steps

Steps

Expected Result

  1. Ensure relevant DMaaP topics are created (SEC_FAULT_OUTPUT, SEC_MEASUREMENT_OUTPUT), along with producer and consumers (using unauthenticated mode)
  2. Post a fault message (REST) to VES Collector. If feasible, use the RAN-Simulator to post the fault message.
  3. Post a performance measurements message (REST) to VES Collector. If feasible, use the RAN-Simulator to post the fault message.
  1. VES Collector posts the received fault message on to DMaaP using the topic SEC_FAULT_OUTPUT.
  2. SON-Handler MS receives the DMaaP SEC_FAULT_OUTPUT message and processes it - verified via logs.
  3. VES Collector posts the received PM message on to DMaaP using the topic SEC_MEASUREMENT_OUTPUT.
  4. SON-Handler MS receives the DMaaP SEC_MEASUREMENT_OUTPUT message and processes it - verified via logs.

Conclusion (Pass /Fail)


Testing Lab

Winlab


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 and RAN-Simulator (or) using SDN-R 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#007

Test Case Name

Config DB interaction

Description

SON Handler Micro-service is able to successfully fetch neighbor list details from Config DB.

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 and RAN-Simulator (or) using SDN-R 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

  • No labels