...
Id. | Test Case Name | Test Case Description | |||||
---|---|---|---|---|---|---|---|
T01 | Create and distribute service which contains PNF based on imported VSP | Verification if in VID is present PNF enabled service. | |||||
T02 | Waiting for PNF Ready | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. | T03 | PNF registration accepted accepting 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. Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on pnfRegistration message contents. | ||
T03 | Delete pnf service and pnf resource | ||||||
T04 | Delete pnf service instance and reasign pnf resource to another service instance | ||||||
T05 | PNF registration rejected | Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID. | |||||
T06 | PNF registration accepted when AAI entry is created using AAI API (without SO instantiation) | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present - created using AAI API | 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 thecorrelationID. | AAI entries shall not be created by PRH.
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. | |||||
T07 | PNF registration accepted when AAI entry is created using AAI API (without SO instantiation) | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present - created using AAI API |
Detailed descriptions
...
Detailed descriptions
Anchor | ||||
---|---|---|---|---|
|
Test Case ID | T01 | |
Test Case Name | Create and distribute service which contains PNF based on imported VSP | |
Description | Verification if in VID is present PNF |
...
Test Case ID | T01 | ||||||||||||
Test Case Name | Create and distribute service which contains PNF based on imported VSP | ||||||||||||
Description | Verification if in VID is present PNF enabled service.
| ||||||||||||
Release | Frankfurt/Guilin | ||||||||||||
Preconditions |
| ||||||||||||
Testing Steps | Step | Expected Result | |||||||||||
|
| ||||||||||||
Actual Results | In VID is present enabled PNF enabled service. | ||||||||||||
Conclusion (Pass/Fail) | |||||||||||||
Testing Lab | |||||||||||||
Tester Name | Krzysztof Kuzmicki |
Anchor | ||||
---|---|---|---|---|
|
Test Case ID | T02 | ||||
Test Case Name | Waiting for PNFReadyPNF 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:
Whole test case can be also executed using postman collection PNF_service_instantiation_v2.postman_collection.json. In order to execute it successfully there is need to set two variables in collection variables:
Also whole test case including T01 is automated in robot/xtesting robot smoke image - | ||||
Release | Frankfurt/Guilin | ||||
Preconditions |
| ||||
Testing Steps | Step | Expected Result | |||
|
| ||||
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 |
...
| ||
Actual Results | PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are |
...
PNF registration accepting 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.
Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID.
Test case covers following steps from message flow in 5G - PNF Plug and Play:
- STEP 26 PNF SENDS PNF REGISTRATION
- STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
- STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
- STEP 27 PRH DOES INVENTORY QUERY
- STEP 29 INVENTORY QUERY
- STEP 30 UPDATE PNF ENTRY
- STEP 31 PNF READY EVENT
- STEP 34 UPDATE PNF WORKFLOW
- STEP 43 INFORM OSS
- Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
- Instantiated service for PNF using Test Case T02 (Waiting for PNFReady)
- Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
- Verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Login to virtual machine with simulator
- In config.json file :
- fill value for sourceName key - use correlationId value used during service instantiation in prerequisite no. 3
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- Run script
./simulator.sh start-dev
in order to start simulator - Run script
./simulator.sh run simulator
in order to start sending registration request messages - Once again verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Verify if SO service has reacted on PNFReady message from PRH and has ended
- Command should return JSON with empty value for IPv4 and IPv6 address
- User is logged in
- config.json file is updated accordingly
- PnP PNF simulator sends registration request
- Command should return JSON with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
- Instantiated SO service has been ended. Verification can be done:
- VID,
Service is instantiated. It is visible in Search for Existing Service Instances menu - SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message:
o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - pnf ready event got from dmaap for correlationId: <correlationId>
- VID,
updated correctly based on correlationID. SO service is instantieted. | ||
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
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.
Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on pnfRegistration message contents.
Test case covers following steps from message flow in 5G - PNF Plug and Play:
- STEP 26 PNF SENDS PNF REGISTRATION
- STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
- STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
- STEP 27 PRH DOES INVENTORY QUERY
- STEP 28 PNF SENDS PNF REGISTRATION
- STEP 29 INVENTORY QUERY
- STEP 30 UPDATE PNF ENTRY
- STEP 31 PNF READY EVENT
- STEP 34 UPDATE PNF WORKFLOW
- STEP 43 INFORM OSS
Anchor | ||||
---|---|---|---|---|
|
Test Case ID | T03 | |
Test Case Name | Delete pnf service and pnf resource | |
Description | ||
Release | Guilin | |
Preconditions | ||
Testing Steps | Step | Expected Result |
Actual Results | ||
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Anchor | ||||
---|---|---|---|---|
|
Test Case ID | T04 | |
Test Case Name | Delete pnf service instance and reassign pnf resource to another service instance | |
Description | ||
Release | Guilin | |
Preconditions |
Testing Steps | Step | Expected Result |
curl -X GET -k -H "accept: application/json"
Actual Results | ||
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 |
- Command should return empty JSON
- User is logged in
- config.json file is updated accordingly
- PnP PNF simulator sends registration request
- Command should return JSON with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
- In PRH log should appear following message:
"org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow" - Command should return JSON with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json
- Instantiated SO service has been ended. Verification can be done:
- VID,
Service is instantiated. It is visible in Search for Existing Service Instances menu
PNF resource is assigned to Service - SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message:
o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - pnf ready event got from dmaap for correlationId: <correlationId>
- VID,
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. SO service is instantieted.
PNF registration rejected
Verification if PRH drops the PnfRegistration request when no AAI entry exists for the correlationID.
AAI entries shall not be created by PRH.
Test case covers following steps from message flow in 5G - PNF Plug and Play:
- STEP 26 PNF SENDS PNF REGISTRATION
- STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
- STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
- STEP 27 PRH DOES INVENTORY QUERY
- STEP 28 PNF SENDS PNF REGISTRATION
- STEP 29 INVENTORY QUERY
- Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
- Verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Login to virtual machine with simulator
- In config.json file :
- fill value for sourceName
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- Run script
./simulator.sh run simulator
in order to start sending registration request messages - Download PRH logs and check that registration requests has been rejected.
- Once again verify AAI entry created by SO service using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
"org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow"
PNF registration is rejected and AAI entries has not be created.
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.
Test case covers following steps from message flow in 5G - PNF Plug and Play:
- STEP 26 PNF SENDS PNF REGISTRATION
- STEP 26A pnfREGISTRATION EVENT ONTO DMAAP
- STEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRH
- STEP 27 PRH DOES INVENTORY QUERY
- STEP 28 PNF SENDS PNF REGISTRATION
- STEP 29 INVENTORY QUERY
- STEP 30 UPDATE PNF ENTRY
- STEP 31 PNF READY EVENT
- STEP 34 UPDATE PNF WORKFLOW
- STEP 43 INFORM OSS
- Up and running 3 PnP PNF Simualtors according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
- Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF) for 4 PNF
- Instantiated service for PNF using Test Case T02 (Waiting for PNFReady) for 4 PNF
- Verify AAI entry created by SO service for 4 PNFs using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Login to each virtual machine with simulator
- In config.json file :
- fill value for sourceName key - use correlationId value used during service instantiation in prerequisite no. 3
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- Run script
./simulator.sh run simulator
in order to start sending registration request messages - Once again verify AAI entry created by SO service 4 PNFs using command:
curl -X GET -k -H "accept: application/json" -H "Real-Time: true" -H "Content-Type: application/json" -H "X-FromAppId: dcae-curl" -H "x-transactionId: 9998" "https://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>" - Verify if SO service has reacted on PNFReady message from PRH and has ended
- Command should return JSONs with empty value for IPv4 and IPv6 address
- User is logged in
- config.json file is updated accordingly
- PnP PNF simulator sends registration request
- Command should return JSONs with IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json for 3 PNFs
For PNF which don't have working simulator command should return once again JSONs with empty value for IPv4 and IPv6 address - Instantiated SO service has been ended for 3 PNFs. Verification can be done:
- VID,
Service is instantiated. It is visible in Search for Existing Service Instances menu
PNF resource is assigned to Service - SO-BPMN pod in /app/logs/bpmn/debug.log should be present following message:
o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - pnf ready event got from dmaap for correlationId: <correlationId>
- VID,
PNF registration is accepted and AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID exept PNF which don't have working simulator.
SO service are intatntieted for PNF except PNF which don't have working simulator. For this PNF service is in progress state. | ||
Conclusion (Pass/Fail) | ||
Testing Lab | ||
Tester Name | Krzysztof Kuzmicki |
Test Case ID | T07T06 | |
Test Case Name | PNF registration accepted when AAI entry is created using AAI API (without SO instantiation) | |
Description | Verification if PNF resource registration is done properly when correct AAI record (based on correlationID) is present - created using AAI API 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 |
...