Test Case Summary
| Test Case Number | Test Case | Status |
|---|---|---|
| 1 | Physical network discovery | |
| 2(a) | Create single CLL instance which accesses single cloud. | |
| 2(b) | Repeat 2(a), and verify closed-loop actions: (1) SDNC establish yang-push SSE session with PNC; (2) SDNC receives bandwidth live updates from PNC; (3) SDNC updates bandwidth in AAI; (3) SDNC sends VES notification to DCAE; | |
| 2(c) | Repeat 2(b), and increase bandwidth and verify: (1) DCAE checks bandwidth received from SDNC against the threshold and calls Policy if needed; (5) Policy calls SO modify-bandwidth API; (6) SO calls SDNC for modify-bandwidth | |
| 2(d) | Delete single CLL instance which accesses single cloud. Verify that E-TRE is deleted on the PNCs. | |
| 2(e) | Repeat 2(d) and verify: SDNC calls terminate-subscription RPC to stop yang-push streaming | |
| 3(a) | Create single CLL instance which access multiple clouds. | |
| 3(b) | Repeat 3(a), and verify closed-loop actions: (1) SDNC establish yang-push SSE session with PNC; (2) SDNC receives bandwidth live updates from PNC; (3) SDNC updates bandwidth in AAI; (3) SDNC sends VES notification to DCAE; | |
| 3(c) | Repeat 3(b), and increase bandwidth and verify: (1) DCAE checks bandwidth received from SDNC against the threshold and calls Policy if needed; (5) Policy calls SO modify-bandwidth API; (6) SO calls SDNC for modify-bandwidth | |
| 3(d) | Delete single CLL instance which access multiple clouds. | |
| 3(e) | Repeat 3(d) and verify: SDNC calls terminate-subscription RPC to stop yang-push streaming | |
| 4 | Create and delete multiple CLL instances which access single cloud, and monitor if the closed-loop call flow is getting triggered. | |
| 5 | Create and delete multiple CLL instances which access multiple clouds, and monitor if the closed-loop call flow is getting triggered. | |
| 6 | Create a CLL instance which have connection links with different bandwidth, and monitor if the closed-loop call flow is getting triggered. | |
| 7 | Modify the bandwidth of a connection link of an existing CLL instance, and monitor if the closed-loop call flow is getting triggered. | |
| 8 | Modify an existing CLL instance by add a new connection link, and monitor if the closed-loop call flow is getting triggered. |
Test Plan
The Transport Slicing integration tests consist of eight (8) test cases. Each test case is broken down into a sequence of measurable checkpoints. These checkpoints are RESTful APIs, each of which has a specific set of input and output parameters that can be measured against. The checkpoints are illustrated below.
Test Case Details
The test procedures for the test cases are provided in the following table.
| # | Test case | SO-NBI | SO-AAI | SO-SDNC | SDNC-AAI | SDNC-PNC |
|---|---|---|---|---|---|---|
| 1 | topology discovery | N/A | N/A | N/A | Merge domain topologies and save in AAI | 1. Provide sample topology json -- design the topo for demo 2. Test PNC simulator topology against sample 3. Test PNC registration with ONAP and topology discovery |
| 2 | test case #2 - #8 |
| 1. provide sample SO-AAI restful API (input/output) 2. test CLL instance in AAI against sample | 1. provide sample SO-SDNC restful API (input/output) 2. Test SDNC DG input/output against sample | 1. provide sample AAI API and (CCVPN/ACTN) model content 2. Test AAI against sample 3. Test SDNC-AAI operation against sample | 1. Provide sample ACTN MPI json (input/output) 4. Check whether PNC is called to subscribe the user to receive performance monitoring events. 5. Check whether SDNC calls PNC to receive notification events via an SSE connection. 6. Check whether SDNC sends an "unsubscribe" request to PNC upon successful deletion of all CLL instances in a given cloud. |
| # | Test case | SDNC-DCAE | DCAE-POLICY | POLICY-SO |
|---|---|---|---|---|
| 1 | topology discovery | N/A | N/A | N/A |
| 2 | test case #2 - #8 |
| 1. Check whether DCAE calls POLICY to read the notification events data. |
|