Table of Contents |
---|
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 | Status | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | Verify PM Mapper is able to query config data from Config Binding Service |
| ||||||||
2 | Verify PM Mapper is able subscribe to expected DR feed. |
| ||||||||
3 | Verify health-check returns 200 when a GET request is sent to /healthcheck endpoint. |
| ||||||||
4 | Verify 3GPP PM Mapper Responds appropriately when no metadata is provided. |
| ||||||||
5 | Verify 3GPP PM Mapper responds appropriately when invalid metadata is provided. |
| ||||||||
6 | Verify PM mapper is able to retrieve pushed PM data from Data Router. |
| ||||||||
7 | Verify PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format). |
| ||||||||
8 | Verify that PM mapper throws Event Failed validation against schema error when no managed element content is provided. |
| ||||||||
9 | Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering. |
| ||||||||
10 | Verify PM mapper creates expected VES PM events for the mapped datathat PM Mapper correctly identifies a non-xml file. |
| ||||||||
11 | Verify any mapping errors are logged. |
| ||||||||
12 | Verify mapped events are publish on Message Router. |
| ||||||||
13 | Verify PM Mapper send delete request for corresponding PM files to Data Router once events are published in Message Router. |
|
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
Test Case ID | PM_Mapper_01 | ||||||
---|---|---|---|---|---|---|---|
Test Case Name | Verify 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 | Verify 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 | Verify Health Check returns 200 when a REST GET request to healthcheck url. | ||||||
Description | Verifies that when the healthcheck endpoint is called, 200 response is returned to indicate that pm-mapper micro-service is running. | ||||||
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 | 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_05 | ||||||||
---|---|---|---|---|---|---|---|---|---|
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_06 | ||||
---|---|---|---|---|---|
Test Case Name | Verify PM mapper is able to retrieve pushed PM data from data 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 and PM Mapper subscribe to Data Router feed. | ||||
Testing Steps |
| ||||
Conclusion (Pass /Fail) | PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/ | ||||
Testing Lab | Ericsson Lab |
Test Case ID | PM_Mapper_07 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format). | ||||||||
Description | Verifies that a pm xml file with no measdata validates using 3GPP xml format with a 200 response and "XML validation successful" is outputted to the pm-mapper_output.log | ||||||||
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 | Verify that PM mapper throws Event Failed validation against schema error when no managed element content is provided.. | ||||||||
Description | Verifies that when a invalid pm xml file is validated using 3GPP xml format then "XML validation failed" is outputted to the pm-mapper_output.log | ||||||||
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 | Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering. | ||||||||
Description | Verify that PM Mapper correctly determines whether a file should be mapped based on the metadata against the instantiated PM Mapper filter information. | ||||||||
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 PM mapper creates expected VES PM events for the mapped datathat PM Mapper correctly identifies a non-xml file. | ||||||||
Description | Verify that PM Mapper correctly identifies a non-xml file by correctly outputting the expected message | ||||||||
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/Conclusion (Pass /Fail) | ||||||||
Testing Lab | Ericsson Lab |
Test Case ID | PM_Mapper_11 | ||||
---|---|---|---|---|---|
Test Case Name | Verify 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_12 | ||||
---|---|---|---|---|---|
Test Case Name | Verify 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_13 | ||||
---|---|---|---|---|---|
Test Case Name | Verify 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 |
PM Mapper Component Performance Stats
Performance (Dublin recommendation 2 - cannot be committed due to Resource constraint)
- Level 0: no performance testing done
- Level 1: baseline performance criteria identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
- Level 2: performance improvement plan created
- Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)
Baseline Stats:
Performance Criteria | Measurement | Comments |
---|---|---|
XML to VES Message / Sec | 2 xml/sec | PM Mapper component can process concurrent request with 1.3 MB XML size successfully. Test Bed: 2 Concurrent user. 300 Iterations 1sec pause between request. |
response time | 0.018 | 100% success. |