Overview:

The E2E integration test consists of three main parts:

Gliffy Diagram is only supported by the cloud editor

Because Forge macros arent supported by the legacy editor, you'll need to convert this content to the cloud editor to display this macro properly. Find out more about converting to the cloud editor

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.

Repo : Yet to update
RUN : Yet to update

Use Case preconditions:

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

#	Test Case	Description	Reference	Tester

#	Test Case	Description	Reference	Tester
1	Create and distribute service which contains PNF	Verify distribution and ingestion of PNF service csar to VID, AAI & SO.	5G - PNF Onboarding Test Cases and Status : PNF-OB-5	@Andy Walshe
2	Waiting for PNFReady	Verification 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
4	Send Configuration with NETCONF over TLS	Verify the configuration is sent to the PNF with NETCONF	5G : Configuration with NETCONF - Success Flow	@Rahul Tyagi @Eric Moore

Detailed Description End-to-End Feature Integration Testcases :

Test Case ID	NETCONF_CONFIGURATION_TLS_E2E

Test Case ID

NETCONF_CONFIGURATION_TLS_E2E

Test Case Name

E2E test case for NETCONF over TLS

Description

Ensure that PNF_READY notification is received by SO from PRH then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API, to configure the xNF

Release

Dublin

Pre-conditions

SO 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 with keystore preconfigured with certificates of PNF-SIM.
Certificates for PNF simulator can be picked up from here. Copy these certs in /dockerdatanfs/sdnc/certs and install sdnc.
PNF-SIM should be running with TLS support.

Install pnf simulator from here using ./simulator.sh start. It will start simulator in TLS/SSH mode at 6503/830 port. Send VES message by changing config/config.json.

Testing Steps

Steps

Expected Result

Send PNF_READY to SO(This step will trigger a run to SS-API, BP component, SDNC and PNF simulator)
SO sends CONFIG-ASSIGN request to CDS.
SO receives the response from CDS for CONFIG-ASSIGN as success.
SO sends CONFIG-DEPLOY async request to CDS.
CDS sends patch(includes mount, configure and unmount request) to SDNC.
SDNC sends mount request to PNF-SIM using TLS connection.
CDS send connection status to SDNC for PNF-SIM.
SDNC sends configuration request to PNF-SIM.
SDNC sends unmount request to PNF-SIM.
Verify received configuration is correct on PNF-SIM (Manual verification).

Get response should give correct result for configuration on PNF-SIM

Conclusion (Pass /Fail)

Passed

Testing Lab

Ericsson Lab, Windriver Lab

Information:

Next Step(s):