End to End flow to be Tested: DCAE 3GPP PM Mapper:
High Level Test Cases and Status: DCAE 3GPP PM Mapper:
| # | Test Cases | Status |
|---|---|---|
| 1 | Confirm that PM Mapper is able to query config data from Config Binding Service | NOT YET TESTED |
| 2 | Confirm that PM Mapper is able subscribe to expected DR feed. | NOT YET TESTED |
| 3 | Confirm that PM mapper is able to retrieve PM data. | NOT YET TESTED |
| 4 | Confirm that mapper can validate the data using schema (e.g. 3gpp xml format). | NOT YET TESTED |
| 5 | Confirm any file validation errors are logged. | NOT YET TESTED |
| 6 | Confirm that mapper creates expected VES PM events for the mapped data. | NOT YET TESTED |
| 7 | Confirm that any mapping errors are logged. | NOT YET TESTED |
| 8 | Confirm that mapped events are publish on Message Router. | NOT YET TESTED |
| 9 | Confirm that PM Mapper send delete request for corresponding PM files to Data Router once events are published in Message Router. | NOT YET TESTED |
Test environment requirements for above test cases:
- sample data files available on DmaaP DR
- e.g. 3GPP PM files used in DCAE Data File Collector testing, or equivalent available in DR
- Test environment reqs:
- DMaaP R4, at minimum need DR running and configured for Bulk PM support
- DCAE 3GPP PM Mapper installed and configured for 3GPP data handling
- i.e. configured for 3GPP PM parsing and event creation
< To - Do > - In progress
Detailed Description PM Mapper Feature Testcases:
| Test Case ID | PM_Mapper_01 | ||||||
|---|---|---|---|---|---|---|---|
| Test Case Name | Confirm that PM Mapper is able to query config data from Config Binding Service | ||||||
| Description | PM Mapper is able to query config data from Config Binding Service once it is deployed. | ||||||
| Release | Dublin | ||||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||||
| Testing Steps |
| ||||||
| Conclusion (Pass /Fail) | |||||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_02 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that PM Mapper is able subscribe to expected DR feed. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_03 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that PM mapper is able to retrieve PM data. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_04 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that mapper can validate the data using schema (e.g. 3gpp xml format). | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_05 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm any file validation errors are logged. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_06 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that mapper creates expected VES PM events for the mapped data. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_07 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that any mapping errors are logged. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_08 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that mapped events are publish on Message Router. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_09 | ||||
|---|---|---|---|---|---|
| Test Case Name | Confirm that PM Mapper send delete request for corresponding PM files to Data Router once events are published in Message Router. | ||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |
| Test Case ID | PM_Mapper_10 | ||||
|---|---|---|---|---|---|
| Test Case Name | |||||
| Description | |||||
| Release | Dublin | ||||
| Pre-conditions | From the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service. | ||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Testing Lab | Ericsson Lab |