Overview:
The E2E integration test consists of three main parts:
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
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:
- xNF simulator.
High Level End-to-End feature integration Test cases :
# | 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 | |
3 | PNF registration accepted | Verification if PNF resource registration is done properly | 5G : Configuration with NETCONF - |
E2E test case for Netconf over TLS | ||||
4 | Send Configuration with NETCONF over TLS | Verify the configuration is sent to the PNF with NETCONF | 5G : Configuration with NETCONF - Success Flow |
Detailed Description End-to-End Feature Integration Testcases :
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 |
|
Successful flow
Dublin
Valid PNF
Valid blueprint
SO is primed and post PNF registration stage
ODL instance is installed and available
Testing Steps
1. SO sends a request to perform action assignConfig
Code Block | ||
---|---|---|
| ||
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
Code Block | ||
---|---|---|
| ||
blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String |
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 |
|
|
Conclusion (Pass /Fail) |
| ||||||
Testing Lab |
Ericsson Lab, Windriver Lab |
Information:
Next Step(s):