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 14
Next »
Test Lab: Win Lab, Rutgers University
Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
JIRA:
REQ-1309
-
Getting issue details...
STATUS
UUI integration test
| S. No | Test Case | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details |
|---|
| 1. | KPI Computation_1 | Operator should be able to view new PDUSessionEstSR KPI within a given time range (a KPI that is computed by KPI MS) via UUI | 1 | KPI Computation should be configured properly, DES templates should be set up | | IN PROGRESS |
|
|
| 2. | KPI Computation_2 | Request from UUI to fetch the KPI within a given time range will be calling new API exposed in UUI server which inturn call the DES API to fetch the PDUSessionEstSR details | 1 | KPI Computation should be configured properly, DES templates should be set up | | IN PROGRESS |
|
|
| 3. | KPI Computation_3 | The Response from UUI server should be validated and the values should be displayed in a graph form in UUI | 1 |
| Deepika S | IN PROGRESS |
|
|
KPI-MS
| S.No | Testcase | Description | Priority | Dependency/Issue | Tester | Status | Remarks | Test Details |
|---|
| 1. | RANSIM_01 | RANSIM must send the initial data configuration to honeycomb | 1 |
| |
|
|
|
| 2. | RANSIM_02 | RANSIM must generate the Intelligent Slicing PM data when the API is triggered and send the data to the honeycomb servers | 1 |
| |
|
|
|
| 3. | HONEYCOMB_01 | Honeycomb should send the PM message to the VES collector | 1 |
| |
|
|
|
| 4. | VES_01 | VES collector must forward the incoming PM message to the Datafile collector via dmaap | 1 |
| |
|
|
|
| 5. | DFC_01 | The datafile collector should send the generated PM data file to the PM-mapper via the datarouter | 1 |
| |
|
|
|
| 6. | PM_MAPPER_01 | The PM mapper should receive the PM data file and post the generated PM data on the topic consumed by the KPI-MS | 1 |
| |
|
|
|
| 7. | KPI_1 | The required config policies should be fetched from the Policy module once the KPI microservice starts running | 1 |
| | IN PROGRESS |
|
|
| 8. | KPI_2 | KPI MS should receive PM data in VES Format from DMaaP published by PM-Mapper | 1 |
| | IN PROGRESS |
|
|
| 9. | KPI_3 | KPI Computation should be triggered once the PM data is received | 1 |
| | IN PROGRESS |
|
|
| 10. | KPI_4 | Once the computation is done, the KPI result has to generated | 1 |
| | IN PROGRESS |
|
|
| 11. | KPI_5 | KPI_MS should be able to publish the result back to DMaaP | 1 |
| | IN PROGRESS |
|
|