Versions Compared

Old Version 59

changes.mady.by.user Krzysztof Kuzmicki

Saved on

compared with

New Version 60

changes.mady.by.user Krzysztof Kuzmicki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In order to successfully run whole flow including SO service instantiation there is need to execute manual steps in SO Maria DB during test time being.
After test activities there is need to revert all changes.
Those changes need to be executed due to fact that in Casablanca release is no present dedicated BPMN workflow for PNF instantiation.
For testing activities there has been introduced adapted CreateVcpeResCustService_simplified bpmn workflow.
There is need to replace all one /mso/async/services/CreateGenericALaCarteServiceInstance to /mso/async/services/CreateVcpeResCustService_simplified values in ORCHESTRATION_URI column in service_recipe table  in catalogdb data base (there should be only 3 entries).
In same entry ther is need also to update service_recipe table SERVICE_MODEL_UUID to UUID of distrubuted PNF SDC Service Model.
After testing above changes need to be reverted to original state.

...

Test Case IDT01
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
ReleaseCasablanca
Preconditions
  1. PNF license has been created
  2. Users with roles: Designer, Tester, Governance Rep, Ops, Admin should be available
Testing StepsStepExpected Result
  1. Login to ONAP portal as a designer user
  2. Navigate to SDC application
  3. Click on ADD + button and select  Add PNF
    Image Removed
  4. In HOME > Create new resource > General page fill all mandatory fields and press Create button in right top corner
  5. Next press Submit for Testing button, fill Message field Certify button. Put comment message in Certification confirmation pop-up and press OK button
  6. Re-login as a tester user
  7. Navigate to SDC tab / HOME menu
  8. From main view select PNF submitted for testing
  9. Press Start Testing button in left top corner and next Accept button.
  10. Put comment message in Certification confirmation pop-up and press OK button
  11. Re-login as a a designer user
  12. Navigate to SDC tab / HOME menu
  13. Click on ADD + button and select  Add Service
  14. In HOME > Create new service > General page fill all mandatory fields (change service type from defautl a'lacarte to macro) and press Create button in right top corner
  15. Go to Composition in left menu
  16. In search box find crated PNF using its name
  17. Drag ad drop it to main view
  18. Next press Submit for Testing button, fill Message field and press OK button
  19. Re-login as a a tester user
  20. Navigate to SDC tab / HOME menu
  21. From main view select Service submitted for testing
  22. Press Start Testing button in left top corner and next Accept button.
  23. Put comment message in Certification confirmation pop-up and press OK button
  24. Re-login as a a governance user
  25. Navigate to SDC tab / HOME menu
  26. From main view select previously created Service
  27. Press Approve button in left top corner and put comment message in Certification confirmation pop-up and press OK button
  28. Re-login as a l as a ops user
  29. Navigate to SDC tab / HOME menu
  30. From main view select previously created Service
  31. Press Distribute button in left top corner
  32. Press Monitor button in left top corner and verify distribution status, use refresh button
  33. Re-login as a a demo user
  34. VID Navigate to  application
  35. From left menu select Browse SDC Service Models
  1. User is logged in
  2. SDC application is open
  3. Page HOME > Create new resource > General page with fields that must be filled out is open
  4. Create/Update saved successfully message is present in left top corner
  5. Submitted For Testing Submitted successfully for testing message is present in left top corner
  6. User is re-logged
  7. SDC application is open and newly created PNF is visible in main view
  8. Page with PNF configuration is open
  9. Start Testing Tested successfully message is present in left top corner
  10. Accept Accepted successfully message is present in left top corner
  11. User is re-loggedPNF is sucesfully Certified
  12. SDC application is open
  13. Page HOME > Create new service > General with fields that must be filled out is open
  14. Create/Update saved successfully message is present in left top corner
  15. Composition main view is open
  16. PNF is visible
  17. PNF is added to serviceImage Removed
  18. Submitted For Testing Submitted successfully for testing message is present in left top corner
  19. User is re-logged
  20. SDC application is open and newly created Service is visible in main view
  21. Page with Service configuration is open
  22. Start Testing Tested successfully message is present in left top corner
  23. Accept Accepted successfully message is present in left top corner
  24. User is re-logged
  25. SDC application is open and newly created Service is visible in main view
  26. Page with Service configuration is open
  27. Approve Approved successfully message is present in left top corner
  28. User is re-logged
  29. SDC application is open and newly created Service is visible in main view
  30. Page with Service configuration is open
  31. Distribute Distribute successfully message is present in left top corner
  32. Monitor main view is opened with information about distribution
    Image Removed
  33. User is re-logged
  34. VID application is open
  35. in Browse SDC Service Models main view is present entry about newly created serviceImage Removed
Actual Actual ResultsIn VID is present PNF enabled service.
Conclusion (Pass/Fail)
Testing Lab
Tester NameKrzysztof Kuzmicki
Testing StepsStepExpected Result[Currently under specification]

...

Test Case IDT02
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
ReleaseCasablanca
Preconditions
  1. Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
  2. Robot init test case has been successfully executed
  3. Changes described in Release notes applied to SO-MARIADB.
Testing StepsStepExpected Result
  1. Login to ONAP portal as a demo user
  2. Navigate to VID application
  3. Navigate to Browse SDC Service Models in left menu
  4. Deploy distributed SDC Service Model for PNF
  5. Fill all mandatory parameters. To "PNF (Correlation) ID" field put correlationId that will be setup in PNF simulator. Press "Confirm" button.
  6. Close " In Progress" pop-up window
  7. Login to so-so-bpmn-infra pod via rancher console:
    kubectl exec -it dev-so-so-bpmn-infra-7584f4f887-p9tmn -n onap /bin/sh
    open debug.log
    vi logs/bpmn/debug.log
  8. 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>"
  1. User is logged in
  2. VID application is open
  3. Distributed SDC Service Model for PNF is present
  4. Create Service Instance -- Macro pop-up is present
  5. All fields are filled. Pop-up window " In Progress" is visible
  6. Window is closed. Service is still not instantiated. Is not visible in "  Search for Existing Service Instances" left menu
  7. In debug.log should be present folloing message:
    2018-11-08T23:15:04.765Z|bbc8bfee-debb-4960-b9a3-f799623f7285| o.o.s.b.i.pnf.dmaap.PnfEventReadyDmaapClient - registering for pnf ready dmaap event for correlation id: <correlationId>

  8. Command should return JSON with empty value for IPv4 and IPv6 address
    {"pnf-name":"<correlationID>"","pnf-id":"testtest","in-maint":true,"resource-version":"1541720264047"}

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 NameKrzysztof Kuzmicki
Test Case IDT03
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
ReleaseCasablanca
Preconditions
  1. Created PNF and Service using Test Case T01 (Create and distribute service which contains PNF)
  2. Instantiated service for PNF using Test Case T02 (Waiting for PNFReady)
  3. Up and running PnP PNF Simualtor according to https://wiki.onap.org/display/DW/PnP+PNF+Simulator
Testing StepsStepExpected Result
  1. 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" "httphttps://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
  2. Login to virtual machine with simulator
  3. In config.json file :
    1. fill value for sourceName key - use correlationId value used during service instantiation in prerequisite no. 3
    2. fill pnfOamIpv4Address, pnfOamIpv6Address with some value
  4. Run script ./simulator.sh start-dev in order to start simulator
  5. Run script ./simulator.sh run simulator in order to start sending registration request messages 
  6. 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" "httphttps://AAI:AAI@<kubernetes noed ip address>:<aai service port>/aai/v11/network/pnfs/pnf/<correlationID>"
  7. Verify if SO service has reacted on PNFReady message from PRH and has ended
  1. Command should return JSON with empty value for IPv4 and IPv6 address
  2. User is logged in
  3. config.json file is updated accordingly
  4. PnP PNF simulator sends registration request
  5. Command should return JSON with  IPv4 and IPv6 address filled accordingly with inputs from simulator's config.json 
  6. Instantiated SO service has been ended. Verification can be done:
    1. VID,
    2. SO audit log
    3. 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 NameKrzysztof Kuzmicki

...