End to End flow to be Tested: DCAE 3GPP PM Mapper:
Gliffy Diagram | ||||
---|---|---|---|---|
|
High Level Test Cases and Status: DCAE 3GPP PM Mapper:
# | Test Cases | Positive/Negative | Status | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | Confirm that PM Mapper is able to query config data from Config Binding Service |
| |||||||||
2 | Confirm that PM Mapper is able subscribe to expected DR feed. |
| |||||||||
3 | Confirm that PM mapper is able to retrieve PM data. |
| |||||||||
4 | Confirm that mapper can validate the data using schema (e.g. 3gpp xml format). |
| |||||||||
5 | Confirm any file validation errors are logged. |
| |||||||||
6 | Confirm that mapper creates expected VES PM events for the mapped data. |
| |||||||||
7 | Confirm that any mapping errors are logged. |
| |||||||||
8 | Confirm that mapped events are publish on Message Router. |
| |||||||||
9 | Confirm that PM Mapper send delete request for corresponding PM files to Data Router once events are published in Message Router. |
| |||||||||
10 | Verify 3GPP PM Mapper Responds appropriately when no metadata is provided. | Negative |
| ||||||||
11 | Verify 3GPP PM Mapper responds appropriately when invalid metadata is provided. | Negative |
|
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
Detailed Description PM Mapper Feature Testcases:
< To - Do > - In progress
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) | PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/ | ||||||
Testing Lab | Ericsson Lab / CSIT |
Test Case ID | PM_Mapper_02 | ||||||
---|---|---|---|---|---|---|---|
Test Case Name | Confirm that PM Mapper is able subscribe to expected DR feed. | ||||||
Description | PM Mapper subscribes to Data Router through bus controller after receiving config data from config_binding_service. | ||||||
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) | PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/ | ||||||
Testing Lab | Ericsson Lab / CSIT |
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 | Verify 3GPP PM Mapper Responds appropriately when no metadata is provided | ||||
Description | Verify 3GPP PM Mapper responds 400 with the message "Missing Metadata." when no metadata is provided. | ||||
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/CSIT |
Test Case ID | PM_Mapper_11 | ||||
---|---|---|---|---|---|
Test Case Name | Verify 3GPP PM Mapper responds appropriately when invalid metadata is provided | ||||
Description | Verify 3GPP PM Mapper responds 400 with the message "Malformed Metadata." when invalid metadata is provided | ||||
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/CSIT |
Test Case ID | PM_Mapper_12 | ||||
---|---|---|---|---|---|
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 |