Gliffy Diagram | ||||
---|---|---|---|---|
|
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 |
---|---|---|---|
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 |
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 - SO triggers Configuration |
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_TLS_E2E_03 | ||||||
---|---|---|---|---|---|---|---|
Test Case Name | E2E test case for NETCONF over TLS | ||||||
Description | Ensure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API | ||||||
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 and PNF simulator should be running with TLS support. | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | |||||||
Testing Lab |
Test Case ID
| Netconf_TLS_E2E_04 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Test Case Name | Successful flow | ||||||||||||||
Description | Steps assignConfig and deployConfig will conclude as expected, and the desired configuration will be applied to the PNF | ||||||||||||||
Release | Dublin | ||||||||||||||
Pre-conditions | Valid PNF | ||||||||||||||
Testing Steps |
| ||||||||||||||
Conclusion (Pass /Fail) | |||||||||||||||
Testing Lab | ? |
Information:
Next Step(s):