Versions Compared

Key

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


Warning

Test update in progress for Guilin release and SO building block flow

...

  • Login to ONAP portal as a designer user
  • Navigate to SDC application
  • Navigate to ONBOARD tab
  • Click on
    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
    ReleaseFrankfurt/Guilin
    Preconditions
    1. Users with roles: Designer (Carlos Santana - cs0008),  Admin (demo) should be available
    Testing StepsStepExpected Result
    1. Robot init sucesfully executed. In intsalation server followin script shoulkd be sucesfully ececuted.

      Code Block
      languagetext
      ubuntu@onap-5915-rke-node:~$ ~/oom/kubernetes/robot/demo-k8s.sh onap init
      Number of parameters:
      2
      KEY:
      init
      ++ kubectl --namespace onap get pods
      ++ sed 's/ .*//'
      ++ grep robot
      + POD=dev-robot-6d67844b64-pgbx5
      ++ dirname ./demo-k8s.sh
      + DIR=.
      + SCRIPTDIR=scripts/demoscript
      + ETEHOME=/var/opt/ONAP
      + '[' ']'
      ++ kubectl --namespace onap exec dev-robot-6d67844b64-pgbx5 -- bash -c 'ls -1q /share/logs/ | wc -l'
      + export GLOBAL_BUILD_NUMBER=0
      + GLOBAL_BUILD_NUMBER=0
      ++ printf %04d 0
      + OUTPUT_FOLDER=0000_demo_init
      + DISPLAY_NUM=90
      + VARIABLEFILES='-V /share/config/robot_properties.py'
      + kubectl --namespace onap exec dev-robot-6d67844b64-pgbx5 -- /var/opt/ONAP/runTags.sh -V /share/config/robot_properties.py -d /share/logs/0000_demo_init -i InitDemo --display 90
      Starting Xvfb on display :90 with res 1280x1024x24
      Executing robot tests at log level TRACE
      ==============================================================================
      Testsuites                                                                    
      ==============================================================================
      Testsuites.Demo :: Executes the VNF Orchestration Test cases including setu...
      ==============================================================================
      Initialize Customer And Models                                        | PASS |
      ------------------------------------------------------------------------------
      Initialize SO Openstack Identity For V3                               | PASS |
      ------------------------------------------------------------------------------
      Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | PASS |
      2 critical tests, 2 passed, 0 failed
      2 tests total, 2 passed, 0 failed
      ==============================================================================
      Testsuites                                                            | PASS |
      2 critical tests, 2 passed, 0 failed
      2 tests total, 2 passed, 0 failed
      ==============================================================================
      Output:  /share/logs/0000_demo_init/output.xml
      Log:     /share/logs/0000_demo_init/log.html
      Report:  /share/logs/0000_demo_init/report.html
      
      


    Testing StepsStepExpected Result
    1. Login to ONAP portal as a designer user
    2. Navigate to SDC application
    3. Navigate to ONBOARD tab
    4. Click on CREATE NEW VLM

    5. Fill all mandatory parameters

    6. Add License Key Group and fill all mandatory parameters

    7. Add Entitlement Pool and fill all mandatory parameters

    8. Add  Feature Group fill all mandatory parameters and add already created Entitlement Pool and License Key Group

    9. Add License Agreement fill mandatory parameters and add already created Feature Group

    10. Press Submit button and next COMMIT & SUBMIT button
    11. Navigate to ONBOARD tab
    12. Click on CREATE NEW VSP

    13. Fill all mandatory parameters:

      1. select Vendor defined in already created VLM
      2. Name will be used in next steps
      3. in ONBOARDING PROCEDURE select Network Package
    14. Click on warning under License Agreement
    15. Fill Licensing Version, License Agreement and Feature Groups from already created VLM
    16. Click on Overview from left menu and press SELECT FILE button.
    17. Select attached pNF.csar file from your PC
    18. Press Submit button and next COMMIT & SUBMIT button
    19. Navigate to Home tab
    20. Click on IMPORT button and select  IMPORT VSP
    21. Select previously created VSP and press IMPORT VSP button
    22. In newly opened window yoiu can moduify PNF name.
    23. Next click Create and Certify button
    24. Next press Certify button. Put comment message in Certification confirmation pop-up and press OK button
    25. Navigate to SDC tab / HOME menu
    26. Click on ADD + button and select  Add Service
    27. In HOME > Create new service > General page fill all mandatory fields (change service type from default a'lacarte to macro) and press Create button in right top corner
    28. Go to Composition in left menu
    29. In search box find crated PNF using its name
    30. Drag ad drop it to main view
    31. Next click Certify button
    32. Next Press Distribute button in left top corner
    33. Press Monitor button in left top corner and verify distribution status, use refresh button
    34. Re-login as a a demo user
    35. VID Navigate to  application
    36. From left menu select Browse SDC Service Models
    1. User is logged in
    2. SDC application is open
    3. ONBOARD CATALOG is visblevisible
    4. New License Model window is present
    5. All mandatory paremetsr parameters are fulfilled
    6. License Key Group is added
    7. Entitlement Pool is added
    8. Feature Group is added
    9. License Agreement isa dded is added
    10. VLM is submited submitted sucesfully
    11. VLM is visblevisible
    12. New Software Product window is present

    13. All mandatory paremetsr parameters are fulfilled

    14. Licensing Version, License Agreement and Feature Groups and warniong warning is not present
    15. Licensing Version, License Agreement and Feature Groups are defined
    16. Select fiel file window is opened
    17. File is selected
    18. File uis is sucesfully uploaded and VSP is submited
    19. Home tab is opnedopened
    20. IMport Import VSP window is presnet with list of dubmited VSPs
    21. Previously create VSP is imported as VSP and Create windo wi window is opened
    22. All modyficatuions modifications are present
    23. PNF is successfully Certified
    24. SDC application is open
    25. Page HOME Page HOME > Create new service > General with fields that must be filled out is open
    26. Create/Update saved successfully message is present in left top corner
    27. Composition main view is open
    28. PNF is visible
    29. PNF is added to service
    30. Service is Cerified and ready for Distribution
    31. Distribute Distribute successfully message is present in left top corner
    32. Monitor main view is opened with information about distribution. Thesr should not be any errors.
    33. User is re-logged
    34. VID application is open
    35. In Browse SDC Service Models main view is present entry about newly created service - it can take couple of minutes ~ 15 minutes
      Image Added
    Actual ResultsIn VID is present PNF enabled service.
    Conclusion (Pass/Fail)
    Testing Lab
    Tester NameKrzysztof Kuzmicki

    ...

    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

    ...