Gliffy Diagram | ||||
---|---|---|---|---|
|
Table of Contents |
---|
Link to specification:
5G - PNF Plug and Play
PNF PNP message flow diagram
Rainy day scenario - PNF is sending registration request to ONAP where required AAI entry is not present:
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
Sunny day scenario - PNF is sending registration request to ONAP where required AAI entry is prepared by SO workflow:
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
PNF PNP deployment diagram
Gliffy Diagram | ||||
---|---|---|---|---|
|
PNF PNP hardware requirements
- ONAP - standard ONAP instance located in Wind River lab
- 4 Virtual machines dedicated for PNF Simulator:
- 2 VCPU
- 8 GB of RAM
- 32 GB of HDD
PNF PNP test cases
High-Level descriptions
Id. | Test Case Name | Test Case Description | Status | ||||
---|---|---|---|---|---|---|---|
T01 | Create and distribute service which contains PNF | Verification if in VID is present PNF enabled service. |
| ||||
T02 | Waiting for PNFReady | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. |
| ||||
T03 | PNF registration accepted when AAI entry created in advance | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present before first InventoryQuery is done by PRH. |
| ||||
T04 | PNF registration accepted when AAI entry created with delay | Verification if PNF resource registration is done properly when correct AAI entry is created after first InventoryQuery is done by PRH. |
| ||||
T05 | PNF registration rejected | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. |
| ||||
T06 | Parallel PNF PnP flows | Four parallel PNF PnP flows are hibernated, PNFRegistration event is received in ONAP, proper PNF PnP enabled workflow instance is re-hydrated. |
|
Detailed descriptions
Test Case ID | T01 | |
Test Case Name | Create and distribute service which contains PNF | |
Description | Verification if in VID is present PNF enabled service.
| |
Release | Casablanca | |
Preconditions |
| |
Testing Steps | Step | Expected Result |
|
| |
Actual Results | In VID is present PNF enabled service. | |
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T02 | |
Test Case Name | Waiting for PNFReady | |
Description | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. Test case covers following steps from message flow in 5G - PNF Plug and Play:
| |
Release | Casablanca | |
Preconditions |
| |
Testing Steps | Step | Expected Result |
[Currently under specification] | ... | |
Actual Results | Correct entry is present in AAI. Entry contains pnf-name equal to correlationID. SO service is waiting for PNFReady to be published by PRH | |
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T03 | |
Test Case Name | PNF registration accepting when AAI entry created in advance | |
Description | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present before first InventoryQuery is done by PRH. Test case covers following steps from message flow in 5G - PNF Plug and Play:
| |
Release | Casablanca | |
Preconditions |
| |
Testing Steps | Step | Expected Result |
|
| |
Actual Results | PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID. | |
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T04 | |
Test Case Name | PNF registration accepted when AAI entry created with delay | |
Description | Verification if PNF resource registration is done properly when correct AAI entry is created after first InventoryQuery is done by PRH. Test case covers following steps from message flow in 5G - PNF Plug and Play:
| |
Release | Casablanca | |
Preconditions |
| |
Testing Steps | Step | Expected Result |
|
| |
Actual Results | PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID even AAI entry has been created after first InventoryQuery is done by PRH | |
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T05 | |
Test Case Name | PNF registration rejected | |
Description | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. Test case covers following steps from message flow in 5G - PNF Plug and Play:
| |
Release | Casablanca | |
Preconditions |
| |
Testing Steps | Step | Expected Result |
|
| |
Actual Results | PNF registration is rejected and AAI entries has not be created. | |
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T06 | |
Test Case Name | Parallel PNF PnP flows | |
Description | Four parallel PNF PnP flows are hibernated, PNFRegistration event is received in ONAP, proper PNF PnP enabled workflow instance is re-hydrated. Test case covers following steps from message flow in 5G - PNF Plug and Play:
| |
Release | Casablanca | |
Preconditions |
| |
Testing Steps | Step | Expected Result |
|
| |
Actual Results | ||
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |