...
...
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 | 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 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. AAI entries shall not be created by PRH. |
T06 | PNF registration accepted when AAI entry is created using AAI API (without SO instantiation) |
Id. | Test Case Name | Test Case Description |
---|
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.- created using AAI API Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based |
on pnfRegistration message contentsT04 | 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. |
T05 | 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. |
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. |
Test Case ID | T01 |
Test Case Name | Create and distribute service which contains PNF |
Description | Verification if in VID is present PNF enabled service. Test case covers following steps from message flow in 5G - PNF Plug and Play: - STEP 1 RESOURCE DEFINITION
- STEP 2 SERVICE DEFINITION
- STEP 3 ARTIFACTS DISTRIBUTION
|
Release | Casablanca |
Preconditions | - PNF license has been created
- Users with roles: Designer, Tester, Governance Rep, Ops, Admin should be available
|
Testing Steps | Step | Expected Result |
- Login to ONAP portal as a designer user
- Navigate to SDC application
- Click on ADD + button and select Add PNF
Image Removed - In HOME > Create new resource > General page fill all mandatory fields and press Create button in right top corner
- Next press Submit for Testing button, fill Message field and press OK button
- Re-login as a tester user
- Navigate to SDC tab / HOME menu
- From main view select PNF submitted for testing
- Press Start Testing button in left top corner and next Accept button.
- Put comment message in Certification confirmation pop-up and press OK button
- Re-login as a a designer user
- Navigate to SDC tab / HOME menu
- Click on ADD + button and select Add Service
- In HOME > Create new service > General page fill all mandatory fields and press Create button in right top corner
- Go to Composition in left menu
- In search box find crated PNF using its name
- Drag ad drop it to main view
- Next press Submit for Testing button, fill Message field and press OK button
- Re-login as a a tester user
- Navigate to SDC tab / HOME menu
- From main view select Service submitted for testing
- Press Start Testing button in left top corner and next Accept button.
- Put comment message in Certification confirmation pop-up and press OK button
- Re-login as a a governance user
- Navigate to SDC tab / HOME menu
- From main view select previously created Service
- Press Approve button in left top corner and put comment message in Certification confirmation pop-up and press OK button
- Re-login as a l as a ops user
- Navigate to SDC tab / HOME menu
- From main view select previously created Service
- Press Distribute button in left top corner
- Press Monitor button in left top corner and verify distribution status, use refresh button
- Re-login as a a demo user
- VID Navigate to application
- From left menu select Browse SDC Service Models
| - User is logged in
- SDC application is open
- Page HOME > Create new resource > General page with fields that must be filled out is open
- Create/Update saved successfully message is present in left top corner
- Submitted For Testing Submitted successfully for testing message is present in left top corner
- User is re-logged
- SDC application is open and newly created PNF is visible in main view
- Page with PNF configuration is open
- Start Testing Tested successfully message is present in left top corner
- Accept Accepted successfully message is present in left top corner
- User is re-logged
- SDC application is open
- Page HOME > Create new service > General with fields that must be filled out is open
- Create/Update saved successfully message is present in left top corner
- Composition main view is open
- PNF is visible
- PNF is added to service
Image Removed - Submitted For Testing Submitted successfully for testing message is present in left top corner
- User is re-logged
- SDC application is open and newly created Service is visible in main view
- Page with Service configuration is open
- Start Testing Tested successfully message is present in left top corner
- Accept Accepted successfully message is present in left top corner
- User is re-logged
- SDC application is open and newly created Service is visible in main view
- Page with Service configuration is open
- Approve Approved successfully message is present in left top corner
- User is re-logged
- SDC application is open and newly created Service is visible in main view
- Page with Service configuration is open
- Distribute Distribute successfully message is present in left top corner
- Monitor main view is opened with information about distribution
Image Removed - User is re-logged
- VID application is open
- in Browse SDC Service Models main view is present entry about newly created service
Image Removed
|
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: - STEP 16 – SERVICE INSTANTIATION
- STEP 18 – RESOURCE LEVEL FLOW STEP 20 – PNF A&AI ENTRY MISSING
- STEP 21 – SUBSCRIBE
- STEP 22 – RESOURCE LEVEL FLOW (RLF) TERMINATES
|
Release | Casablanca |
Preconditions | - Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
|
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. 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
|
Release | Casablanca |
Preconditions | - 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
|
Testing Steps | Step | Expected Result |
- 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" "http://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" "http://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,
- SO audit log
- AAI registry
|
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. 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
|
Release | Casablanca |
Preconditions | - Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
- Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
|
Testing Steps | Step | Expected Result |
- 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" "http://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 that will be used during service instantiation in step no. 7
- fill pnfOamIpv4Address, pnfOamIpv6Address with some value
- set testDuration (amount of registration requests) to value that allows incinerate SO service during period of time when messages are send to ONAP
- set messageInterval interval with which messages are send to ONAP
- 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.
- Instantiated service for PNF using Test Case T02 (Waiting for PNFReady) - use corelationID from step no. 3
- 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" "http://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 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 in:
- VID,
- SO audit log
- AAI registry
|
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. 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
|
Release | Casablanca |
Preconditions | - Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
|
Testing Steps | Step | Expected Result |
- 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" "http://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" "http://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
| Command should return HTTP 400 codeUser is logged inconfig.json file is updated accordinglyPnP PNF simulator sends registration requestIn PRH log should appear following message:
"org.onap.dcaegen2.services.prh.exceptions.AAINotFoundException: Incorrect response code for continuation of tasks workflow"Command should return HTTP 400 codeActual Results | PNF registration is rejected and AAI entries has not be created.
|
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 |
T06Parallel 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:
STEP 26 PNF SENDS PNF REGISTRATIONSTEP 26A pnfREGISTRATION EVENT ONTO DMAAPSTEP 26B pnfREGISTRATION EVENT RETRIEVED BY PRHSTEP 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 OSSDelete pnf service instance and reassign pnf resource to another service instance
|
Description |
|
Release | Guilin |
Preconditions |
|
Testing Steps | Step | Expected Result |
|
|
Actual Results |
|
Conclusion (Pass/Fail) |
|
Testing Lab |
|
Tester Name | Krzysztof Kuzmicki |