Gliffy Diagram | ||||
---|---|---|---|---|
|
Gliffy Diagram | ||||
---|---|---|---|---|
|
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 |
Receive Configuration From Config Binding Service |
|
Status | ||
---|---|---|
|
Confirm that PM mapper is able to retrieve PM data.
Status | ||
---|---|---|
|
Confirm that mapper can validate the data using schema (e.g. 3gpp xml format).
Status | ||
---|---|---|
|
Confirm any file validation errors are logged.
Status | ||
---|---|---|
|
Confirm that mapper creates expected VES PM events for the mapped data.
Status | ||
---|---|---|
|
Confirm that any mapping errors are logged.
Status | ||
---|---|---|
|
Confirm that mapped events are forwarded on Message Router.
Status | ||
---|---|---|
|
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 R3, 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
- xNF instantiated at ONAP, e.g. in A&AI
| ||||||||
2 | Verify Health Check returns 200 when a REST GET request to healthcheck url |
| ||||||
3 | Verify 3GPP PM Mapper responds appropriately when no metadata is provided. |
| ||||||
4 | Verify 3GPP PM Mapper responds appropriately when invalid metadata is provided |
| ||||||
5 | Verify that PM Mapper logs successful when a file that contains no measdata is provided |
| ||||||
6 | Verify that PM Mapper throws Event failed validation against schema error when no managed element content is provided |
| ||||||
7 | Verify that PM Mapper maps Type-C xml file and publish 3gpp perf VES events to message router |
| ||||||
8 | Verify 3GPP PM Mapper maps Type-A file based on counter filtering and publish 3gpp perf VES events to message router |
| ||||||
9 | Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering. |
| ||||||
10 | Verify that PM Mapper correctly identifies a non-xml file. |
|
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
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 |
Steps | Expected Result |
---|---|
| PM Mapper successfully query it's config data from config_binding_service. |
| Log appropriate error message. |
PM_Mapper_0201
Steps | Expected Result |
---|
PM_Mapper_03
PM_Mapper_04
PM_Mapper_05
PM_Mapper_06
PM_Mapper_07
PM_Mapper_08
PM_Mapper_09
PM_Mapper_10
| PM Mapper successfully query it's config data from config_binding_service. /var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log: 2019-02-14T14:44:57.306Z main INFO org.onap.dcaegen2.services.pmmapper.config.ConfigHandler Received pm-mapper configuration from ConfigBinding Service:\n{"pm-mapper-filter": "{ \"filters\":[]}", "3GPP.schema.file": "{\"3GPP_Schema\":\"./etc/3GPP_relaxed_schema.xsd\"}", "streams_subscribes": {"dmaap_subscriber": {"type": "data_router", "aaf_username": null, "aaf_password": null, "dmaap_info": {"location": "csit-pmmapper", "delivery_url": "3gpppmmapper", "username": "username", "password": "password", "subscriber_id": "subsriber_id"}}}, "streams_publishes": {"pm_mapper_handle_out": {"type": "message_router", "aaf_password": null, "dmaap_info": {"topic_url": "https://message-router:3904/events/org.onap.dmaap.onapCSIT.pm_mapper", "client_role": "org.onap.dmaap.client.pub", "location": "csit-pmmapper", "client_id": null}, "aaf_username": null}}, "buscontroller_feed_id": "1", "buscontroller_feed_subscription_endpoint": "http://dmaap-bc:8080/webapi/dr_subs", "services_calls": {}} |
| Log appropriate error message. |
Test Case ID | PM_Mapper_02 | ||||||
---|---|---|---|---|---|---|---|
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_03 | ||||||||
---|---|---|---|---|---|---|---|---|---|
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_04 | ||||||||
---|---|---|---|---|---|---|---|---|---|
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_05 | ||||||||
---|---|---|---|---|---|---|---|---|---|
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_06 | ||||||||
---|---|---|---|---|---|---|---|---|---|
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_07 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify that PM Mapper maps Type-C xml file and publish 3gpp perf VES events to message router. | ||||||||||||||
Description | Verifies that PM Mapper maps Type-C xml files correctly and publishes 3gpp perf VES events to message router | ||||||||||||||
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_08 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify 3GPP PM Mapper maps Type-A file based on counter filtering and publish 3gpp perf VES evnets to message router | ||||||||||||||
Description | Verifies that PM Mapper maps Type-A xml files correctly and publishes 3gpp perf VES events to message router | ||||||||||||||
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_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 that 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/ | ||||||||
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 |
---|---|---|
Time to process 700 XML ( 1.3 MB ) files | 79 minutes | This time need to be improved . PM Mapper component can process concurrent request with 1.3 MB XML size successfully. Test Bed: 1 Concurrent user. 700 XML file. Standard dublin Full ONAP installation : vCPU: 16, RAM: 60GB, Disk Size:120 GB |
Avg response time | 0.034 | 100% success. |
Performance Improvement Plan:
- Time to process 700 XML ( 1.3 MB avg ) : ~10 min
- Adapt parallelism in PM Mapper.