| Test Case Name | Test Case Description | Status |
|---|
| 1. | AAI entry creation from SO side | Verification if AAI entry is created properly using VID. Entry contains pnf-name and pnf-id equal to correlationID. | |
| 2. | SO awaiting for PNF to be readyAAI entry ip address check by SO | Verification if PNF PnP functionality within SO is waiting for PNFReady in case there's no any ip address in related AAI entry to be published by PRH. | |
| 3. | AAI entry update from PRH side | Verification if AAI entry is updated properly with pnfOamIpv4Address / pnfOamIpv6Address based on correlationID. | |
| 4. | PNF rejection when no entry in AAI present | Verification if PNF resource instantiation is not done when there is no related AAI entry.PRH drops the PnfRegistration request when no AAI entry exists for the correlationID.
AAI entries shall not be created by PRH. | |
| 5. | PNF PnP when AAI entry created in advance | Verification if PNF resource instantiation is done properly when correct AAI record (based on correlationID) is present before first InventoryQuery is done by PRH. | |
| 6. | PNF PnP when AAI entry created with delay | Verification if PNF resource instantiation is done properly when correct AAI entry is created after first InventoryQuery is done by PRH. | |
| 7. | Parallel PNF PnP flowsVerification of scenario containing four | Four parallel PNF PnP flows where one PNF is not connected to OAM networkare hibernated, PNFRegistration event is received in ONAP, proper PNF PnP instance is re-hydrated. | |
| 8. | SO waiting for PNF max timeout | Verification if SO max PNF waiting can be set up to 2 weeks. | |
