Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 26 Next »

High Level Test Cases and Status

#Test CaseTest TypeSummaryStatus
PNF-OB-1Test insecure vendor PNF csar packageSanity
-
PNF-OB-2Test secure vendor PNF csar packageSanity
-
PNF-OB-3Test creation of VSP using input PNF package through UIManualTest both secure & insecure package.-
PNF-OB-4Test creation of PNF by importing PNF VSP through UIManual

PNF-OB-5Test creation of PNF with artefacts through UIManual
-
PNF-OB-6Test creation of PNF service containing PNF through UIManual

PNF-OB-7Test distribution and ingestion of SDC generated PNF service csar packageManual + E2E
-

Test Types:
Sanity : automated docker based tests from SDC repo (SDC Sanity)
Manual : manual test in SDC UI (either local SDC or ONAP)
E2E : end to end test with other interested ONAP components

Diagram

Detailed Description

Test Case ID
PNF-OB-1
Test Case NameTest insecure vendor PNF csar package
DescriptionTake insecure/unsigned vendor created csar package and include it in SDC Sanity test cases
ReleaseDublin
Preconditions

Package structure and contents finalised.
SDC Sanity testing environment available.

Testing Steps
StepExpected Result

Add agreed/finalised 'Vendor-PNF-insecure.csar' file to SDC repository to be included in 'sanity-Onboard' test category

File exists.

Run SDC sanity tests:

  • Create VSP
  • Create PNF from VSP
  • Certify PNF
  • Create Service
  • Add PNF to Service
  • Certify Service
  • Run tosca validation on output service csar
'sanity-Onboard' test category report displays pass result for new csar package
Conclusion (Pass/Fail)
Testing LabEricsson Lab / SDC Sanity

.

Test Case ID
PNF-OB-2
Test Case NameTest secure vendor PNF csar package
DescriptionTake secure/signed vendor created csar package and include it in SDC Sanity test cases
ReleaseDublin
PreconditionsPackage structure and contents finalised.
SDC Sanity testing environment available.
Testing Steps
StepExpected Result

Add agreed/finalised 'Vendor-PNF-secure.csar' file to SDC repository to be included in 'sanity-Onboard' test category

File exists.

Run SDC sanity tests

  • Create VSP
  • Create PNF from VSP
  • Certify PNF
  • Create Service
  • Add PNF to Service
  • Certify Service
  • Run tosca validation on output service csar
'sanity-Onboard' test category report displays pass result for new csar package
Conclusion (Pass/Fail)
Testing LabEricsson Lab / SDC Sanity

 .

Test Case ID
PNF-OB-3
Test Case NameTest creation of VSP using input PNF package through UI
DescriptionRun through manual process of onboarding in SDC gui starting with creating vendor license model to then creating vendor software product using vendor supplied PNF csar package.
ReleaseDublin
PreconditionsLocal SDC or ONAP deployment available
Testing Steps
StepsExpected Result

  1. Login to ONAP portal as a Designer user

  2. Navigate to SDC application

  3. On ONBOARD page click on 'CREATE NEW VLM'

  4. Go through the steps of creating new Vendor License Manager with required and corresponding License Key Groups, Entitlement Pools, Feature Groups and License Agreement submitting the VLM at the end of the process.

  5. On ONBOARD page click on 'CREATE NEW VSP'

  6. In 'Vendor' drop down select license manager name created in step 3 above and select 'Network Package' as the onboarding procedure

  7. On 'Software Product Details' page add the missing license agreement using VLM created in step 3 above.

  8. Going back to 'Overview' in left menu and under Software Product Attachments choose SELECT FILE and upload vendor pnf csar input file.

  9. Submit the VSP for creation.

Vendor CSAR package parsed and loaded into SDC and used in VSP.

Conclusion (Pass/Fail)


Testing LabEricsson Lab / Local SDC or ONAP deployment

 .

Test Case ID
PNF-OB-4
Test Case NameTest creation of VF by importing PNF VSP through UI
Description

Building on PNF-OB-3 test that a VF can be created in the SDC gui using the PNF VSP

ReleaseDublin
PreconditionsLocal SDC or ONAP deployment available
Testing Steps
StepExpected Result
  1. Login to ONAP portal as a Designer user and open SDC application
  2. Select HOME in top menu and then click on 'Import VSP' selecting VSP output from PNF-OB-3 above. Click 'Create' button.
  3. Click on 'Certify' button entering message in pop up window to continue.

VF has been created in SDC gui and is certified.

Conclusion (Pass/Fail)


Testing LabEricsson Lab / Local SDC or ONAP deployment

.

Test Case ID
PNF-OB-5
Test Case NameTest creation of PNF with artefacts through UI
Description
ReleaseDublin
PreconditionsLocal SDC or ONAP deployment available
Testing Steps
StepExpected Result
  1. Login to ONAP portal as a Designer user and open SDC application
  2. On the HOME screen click on ADD button and select Add PNF, complete mandatory fields and press Create button
  3. Certify the PNF using button in top right corner of screen.
  4. Navigate to SDC -> HOME menu
  5. Click on ADD button and select Add Service, complete mandatory fields, add deployment artifacts and press Create button
  6. Go to Composition in left menu
  7. In search box find created PNF using its name, drag and drop it to main view and Submit for Testing
  8. Re-login as a a Tester user
  9. Navigate to SDC tab HOME menu and select service submitted for testing
  10. Press Start Testing button in right top corner and then Accept button adding comment.
  11. Re-login as a a Governor user
  12. Navigate to SDC tab CATALOG menu and select previously created service
  13. Press Approve button in right top corner, add comment and press OK button

The created service has been displayed as Distribution Approved in HOME menu.

Conclusion (Pass/Fail)
Testing LabEricsson Lab / Local SDC or ONAP deployment

.

Test Case ID
PNF-OB-6
Test Case NameTest creation of PNF service containing PNF through UI
DescriptionBuilding on PNF-OB-4 test that a PNF can be created in the SDC gui using the PNF VSP
ReleaseDublin
Preconditions

Local SDC or ONAP deployment available

Testing Steps
StepExpected Result
  1. Navigate to SDC -> HOME menu
  2. Click on ADD button and select Add Service, complete mandatory fields, add deployment artifacts and press Create button
  3. Go to Composition in left menu
  4. In search box find created PNF from PNF-OB-4 above using its name, drag and drop it to main view and Submit for Testing
  5. Re-login as a a Tester user
  6. Navigate to SDC tab HOME menu and select service submitted for testing
  7. Press Start Testing button in right top corner and then Accept button adding comment.
  8. Re-login as a a Governor user
  9. Navigate to SDC tab CATALOG menu and select previously created service
  10. Press Approve button in right top corner, add comment and press OK button

The created service has been displayed as Distribution Approved in HOME menu.

Conclusion (Pass/Fail)
Testing LabEricsson Lab / Local SDC or ONAP deployment

 .

Test Case ID
PNF-OB-7
Test Case NameTest distribution of SDC generated csar package to interested components, e.g. SO, AAI and SDNC
Description

Previous tests of SDC can be ran in both a full ONAP deployment environment or on the 'SDC Sanity' local test environment. This test case verifies the CSAR package and PNF onboarding package artifacts by distributing said package to other ONAP components at runtime.

Reference: 5G - E2E PNF Onboarding with PnP & Configuration with Netconf over TLS - Integration Test Cases

ReleaseDublin
PreconditionsONAP deployment available, SDC changes also deployed to ONAP.
Testing Steps
StepExpected Result
  1. Login to ONAP portal as an Ops user
  2. Navigate to SDC tab HOME menu and select previously created PNF Service
  3. Press Distribute button in right top corner
  4. Press Monitor button in left top corner and verify distribution status, you may need to refresh screen.

SDC UI indicates distribution of PNF service to VID, SO and AAI.

Follow test steps as documented on 5G - E2E PNF Onboarding with PnP & Configuration with Netconf over TLS - Integration Test CasesFull end-to-end flow verified successfully.
Conclusion (Pass/Fail)
Testing LabEricsson Lab / ONAP Lab

xc 342

  • No labels