Versions Compared

Key

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

...

Id.Test Case NameTest Case Description
T01Create and distribute service which contains PNFVerification if in VID is present PNF enabled service.
T02Waiting for PNFReadyVerification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH.
T03PNF 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.
Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on pnfRegistration message contents.

T04PNF 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.

T05PNF 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.

T06Parallel PNF PnP flowsFour 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
Verification if AAI entries: ipaddress-v4-oam and ipaddress-v6-oam are updated correctly based on correlationID.

Detailed descriptions

Anchor
CreateanddistributeservicewhichcontainsPNF
CreateanddistributeservicewhichcontainsPNF

CreateanddistributeservicewhichcontainsPNF
Test Case IDT01
Test Case Name
Anchor
CreateanddistributeservicewhichcontainsPNF

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. 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
  4. In HOME > Create new resource > General page fill all mandatory fields and press Create button in right top corner
  5. Next press Certify button. Put comment message in Certification confirmation pop-up and press OK button
  6. Navigate to SDC tab / HOME menu
  7. Click on ADD + button and select  Add Service
  8. 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
  9. Go to Composition in left menu
  10. In search box find crated PNF using its name
  11. Drag ad drop it to main view
  12. Next press Submit for Testing button, fill Message field and press OK button
  13. Re-login as a a tester user
  14. Navigate to SDC tab / HOME menu
  15. From main view select Service submitted for testing
  16. Press Start Testing button in left top corner and next Accept button.
  17. Put comment message in Certification confirmation pop-up and press OK button
  18. Re-login as a a governance user
  19. Navigate to SDC tab / HOME menu
  20. From main view select previously created Service
  21. Press Approve button in left top corner and put comment message in Certification confirmation pop-up and press OK button
  22. Re-login as a l as a ops user
  23. Navigate to SDC tab / HOME menu
  24. From main view select previously created Service
  25. Press Distribute button in left top corner
  26. Press Monitor button in left top corner and verify distribution status, use refresh button
  27. Login to rancher node.
  28. Login to <dev>-so-so-mariadb-<576ccb887f-9v7q8> node. For example:

    Code Block
    collapsetrue
    kubectl exec -it dev-so-so-mariadb-576ccb887f-9v7q8 -n onap /bin/bash
  29. Login to mysql db

    Code Block
    collapsetrue
    root@mariadb:/# mysql -uroot -ppassword
  30. Use catalogdb database
  31. Add service rescipe for distrinuted service executing following command (replace UUID by UUID of created/distributed service):

    Code Block
    collapsetrue
    insert into service_recipe values (null, 'createInstance' , '1' , 'pnf service', '/mso/async/services/CreateVcpeResCustService_simplified', null , 180, null, 2017-10-05 , '<UUID>' );
  32. Re-login as a a demo user
  33. VID Navigate to  application
  34. 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. PNF is sucesfully Certified
  6. SDC application is open
  7. Page HOME > Create new service > General with fields that must be filled out is open
  8. Create/Update saved successfully message is present in left top corner
  9. Composition main view is open
  10. PNF is visible
  11. PNF is added to service
  12. Submitted For Testing Submitted successfully for testing message is present in left top corner
  13. User is re-logged
  14. SDC application is open and newly created Service is visible in main view
  15. Page with Service configuration is open
  16. Start Testing Tested successfully message is present in left top corner
  17. Accept Accepted successfully message is present in left top corner
  18. User is re-logged
  19. SDC application is open and newly created Service is visible in main view
  20. Page with Service configuration is open
  21. Approve Approved successfully message is present in left top corner
  22. User is re-logged
  23. SDC application is open and newly created Service is visible in main view
  24. Page with Service configuration is open
  25. Distribute Distribute successfully message is present in left top corner
  26. Monitor main view is opened with information about distribution
  27. User is looged to rancher node
  28. User is looged to mariadb pod
  29. User is looged to mysql
  30. Catalogdb is selected
  31. Service recipe is added to service recipe table:

    Code Block
    collapsetrue
    MariaDB [catalogdb]> insert into service_recipe values (null, 'createInstance' , '1' , 'pnf service', '/mso/async/services/CreateVcpeResCustService_simplified', null , 180, null, 2017-10-05 , '4ce6ffb8-30ed-4750-8b7e-e386eab142a4' );
    
    MariaDB [catalogdb]> select * from service_recipe;
    +----+--------------------+-------------+----------------+----------------------------------------------------------+-------------------+----------------+-------------------------+---------------------+--------------------------------------+
    | id | ACTION             | VERSION_STR | DESCRIPTION    | ORCHESTRATION_URI                                        | SERVICE_PARAM_XSD | RECIPE_TIMEOUT | SERVICE_TIMEOUT_INTERIM | CREATION_TIMESTAMP  | SERVICE_MODEL_UUID                   |
    +----+--------------------+-------------+----------------+----------------------------------------------------------+-------------------+----------------+-------------------------+---------------------+--------------------------------------+
    .
    .
    .
    | 92 | createInstance     | 1           | pnf service    | /mso/async/services/CreateVcpeResCustService_simplified  | NULL              |            180 |                    NULL | 0000-00-00 00:00:00 | 4ce6ffb8-30ed-4750-8b7e-e386eab142a4 |
    +----+--------------------+-------------+----------------+----------------------------------------------------------+-------------------+----------------+-------------------------+---------------------+--------------------------------------+


  32. User is re-logged
  33. VID application is open
  34. in Browse SDC Service Models main view is present entry about newly created service
Actual ResultsIn VID is present PNF enabled service.
Conclusion (Pass/Fail)
Testing Lab
Tester NameKrzysztof Kuzmicki

Anchor
PNF Ready
PNF Ready

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 at rancher node - ~/oom/kubernetes/robot/demo-k8s.sh onap init
  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 following message:
    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

...