Functional Testing

The testing shall be performed at Winlab, Rutgers University.

1. SON-Handler MS (DCAE)

Note: For the tests involving DMaaP, DMaaP should be set up. For API calls/responses, if the real components (e.g., OOF) are not available, stubs shall be used.

S.No.	Description	Status
1.	SON Handler MS successfully on-boarded on to DCAE and comes online	NOT YET TESTED
2.	SON Handler MS is able to successfully fetch configuration policies using CBS API	NOT YET TESTED
3.	SON Handler MS is able to subscribe to DMaaP messages	NOT YET TESTED
4.	SON Handler MS is able to receive messages on DMaaP (e.g., from SDN-R, VES-Collector)	NOT YET TESTED
5.	SON Handler MS is able to post messages on DMaaP (e.g., to Policy)	NOT YET TESTED
6.	SON Handler MS is able to read/write into PostgreSQL DB	NOT YET TESTED
7.	SON Handler is able to invoke API call(s) to ConfigDB and handle the response	NOT YET TESTED
7.	SON Handler MS is able to invoke API call(s) towards OOF for PCI optimization	NOT YET TESTED
8.	SON Handler MS is able to handle callbackURL call (async response) from OOF, process it, and send out a DMaaP message (to Policy)	NOT YET TESTED
9.	SON Handler MS log message formats are compliant to the ONAP logging specifications	NOT YET TESTED

2. Policy

S.No.	Description	Status
1.	Policy Handler (DCAE) is able to fetch the SON-Handler MS config policies	NOT YET TESTED
2.	SON Control Loop to be extended to include handling of DMaaP message (response) from SDN-R	NOT YET TESTED
3.	Policy is able to receive the new DMaaP message from SDN-R to notify the result of changes in RAN	NOT YET TESTED
4.	Policy is able to send the new DMaaP message to SON-Handler MS to notify the result of changes in RAN (upon reception of DMaaP message from SDN-R)	NOT YET TESTED

3. SDN-R and Config DB

S.No.	Description	Status
1.	New API to update single cell's details in DB works successfully	NOT YET TESTED
2.