Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 46 Next »

Overview:

The E2E integration test consists of three main parts:




Deployment:

Test environment requirements for the test cases:

  • xNF simulator for test cases:  PNF Simulator with TLS & YANG support.
  • SO with Config-Assign and Configure steps implemented in workflows.
  • CDS Blueprint processor enhanced so that it can send mount, configure and un-mount rest request to SDNC.
  • SDNC enhanced with ODL flourine SR2 and also capable to import client and trusted certificate and private key at deployment time.

This environment can be set up by following the steps below.

  1. Repo : Yet to update
  2. RUN : Yet to update

Use Case preconditions:

    • xNF simulator.

High Level End-to-End feature integration Test cases :


#Test CaseDescriptionReferenceTester
1Create and distribute service which contains PNFVerify distribution and ingestion of PNF service csar to VID, AAI & SO.5G - PNF Onboarding Test Cases and Status : PNF-OB-5Andy Walshe
2Waiting for PNFReadyVerification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH.5G - PNF PnP -WaitingforPNFReady

Rahul Tyagi

Eric Moore

3

PNF registration accepted

Verification if PNF resource registration is done properly

5G : Configuration with NETCONF - E2E test case for Netconf over TLS

Rahul Tyagi

Eric Moore

4Send Configuration with NETCONF over TLSVerify the configuration is sent to the PNF with NETCONF5G : Configuration with NETCONF - Success Flow

Rahul Tyagi

Eric Moore

Detailed Description End-to-End Feature Integration Testcases :


Test Case ID

Netconf_TLS_E2E_03

Test Case Name

E2E test case for NETCONF over TLS

DescriptionEnsure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API
ReleaseDublin
Pre-conditionsSO should be waiting for PNF_READY notification after registration process and fully configured as per registration process. Blueprint archive should be configured for correct blueprint. SDNC should be installed successfully and PNF simulator should be running with TLS support.
Testing Steps
StepsExpected Result
  1. Send PNF_READY to SO(This step will trigger a run to SS-API, BP component, SDNC and PNF simulator)
  2. Send SSH mount/connect request to SDNC/ODL using rest client.
  3. Send GET request for configuration to get configuration, set in step 1.
  4. Verify received configuration is correct.
Get response should give correct result for configure


Conclusion (Pass /Fail)
Testing Lab



Test Case ID

Netconf_TLS_E2E_04
Test Case Name

Successful flow

DescriptionSteps assignConfig and deployConfig will conclude as expected, and the desired configuration will be applied to the PNF
Release

Dublin

Pre-conditions

Valid PNF
Valid blueprint
SO is primed and post PNF registration stage
ODL instance is installed and available

Testing Steps



StepsExpected Result

1. SO sends a request to perform action assignConfig

blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String

2. SS-API forwards the request to BP, that will load the blueprint, execute the action specified, prepare the configlet, persist it and return a successful message to SO

3. SO recognizes the success message and sends a request to perfom action deployConfig

blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String

4. SS-API forwards the request to Blueprint Processor, that will load the blueprint, execute the action specified, retrieve the configlet from the persistence, connect to ODL, send the configlet(s) to the PNF and return a successful message to SO


Conclusion (Pass /Fail)
Testing Lab

Information:


Next Step(s):


  • No labels