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 is able to query config data from Receive Configuration From Config Binding Service |
| ||||||||||
2 | Verify PM Mapper is able subscribe to expected DR feed. | |||||||||||
Status | ||||||||||||
colour | Green | |||||||||||
title | PASS | 3 | Verify health-check Health Check returns 200 when a REST GET request is sent to / healthcheck endpoint.url |
| ||||||||
43 | Verify 3GPP PM Mapper Responds responds appropriately when no metadata is provided. |
| ||||||||||
54 | Verify 3GPP PM Mapper responds appropriately when invalid metadata is provided. |
| 6||||||||||
5 | Verify | PM mapper is able to retrieve pushed PM data from Data Router.that PM Mapper logs successful when a file that contains no measdata is provided |
| 7 | Verify PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format). | |||||||
Status | ||||||||||||
colour | Green | |||||||||||
title | PASS | 86 | Verify that PM mapper Mapper throws Event Failed failed validation against schema error when no managed element content is provided. |
| ||||||||
97 | Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering.maps Type-C xml file and publish 3gpp perf VES events to message router |
| ||||||||||
108 | Verify PM mapper creates expected VES PM events for the mapped data.3GPP PM Mapper maps Type-A file based on counter filtering and publish 3gpp perf VES events to message router |
| ||||||||||
11 | Verify any mapping errors are logged. |
| ||||||||||
| ||||||||||||
9 | Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering | 12 | Verify mapped events are publish on Message Router. |
| Not yet tested
| |||||||
1310 | Verify PM Mapper send delete request for corresponding PM files to Data Router once events are published in Message Routerthat PM Mapper correctly identifies a non-xml file. |
title | 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
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 Receive Configuration 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 |
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 |
|
PM Mapper successfully subscribes to Data Router.
/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:
2019-02-14T14:28:11.348Z main INFO org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber Starting subscription to DataRouter ENTRY
2019-02-14T14:28:11.348Z main INFO org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber 39d38cfa-fa5b-4b2f-a3db-fbd19c01fedf INVOKE [ SYNCHRONOUS ]
2019-02-14T14:28:11.419Z main INFO org
| ||||
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) |
- Check subscriber info in Data Router.
Data Router has subscription entry in it's database.
curl -k https://172.18.0.6:8443/internal/prov
{
"feeds": [
{"suspend":false,"groupid":0,"description":"PM Mapper Feed","version":"1","authorization":{"endpoint_addrs":[],"classification":"unclassified","endpoint_ids":[{"password":"89qtolvgb6n7w5r","id":"tmp_ch389e2m9iu2bl7"}]},"last_mod":1550155491000,"deleted":false,"feedid":1,"name":"pmmapper","business_description":"","publisher":"bulkpm","links":{"subscribe":"https://dmaap-dr-prov/subscribe/1","log":"https://dmaap-dr-prov/feedlog/1","publish":"https://dmaap-dr-prov/publish/1","self":"https://dmaap-dr-prov/feed/1"},"created_date":1550155491000}
],
"groups": [
],
"subscriptions": [
{"subid":1,"suspend":false,"delivery":{"use100":false,"password":"password","user":"username","url":"3gpppmmapper"},"last_mod":1550155497000,"subscriber":"DGL","feedid":1,"groupid":0,"metadataOnly":false,"links":{"feed":"https://dmaap-dr-prov/feed/1","log":"https://dmaap-dr-prov/sublog/1","self":"https://dmaap-dr-prov/subs/1"},"created_date":1550155497000}
],
...
..
.
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 |
|
|
|
|
|
PM_Mapper_04
Verify 3GPP PM Mapper responds 400 with the message "Missing Metadata." when no metadata is provided.
No Format |
---|
curl -X PUT <PM Mapper IP>:8081/delivery
Missing Metadata. |
/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
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 |
|
PM_Mapper_05
Verify 3GPP PM Mapper responds 400 with the message "Malformed Metadata." when invalid metadata is provided
- Send a request to the pm-mapper with invalid metadata header.
No Format |
---|
curl -X PUT <PM Mapper IP>:8081/delivery -H 'X-ATT-DR-META: not metadata'
Malformed Metadata. |
/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
Conclusion (Pass /Fail) | ||
Testing Lab | Ericsson Lab |
Test Case ID | PM_Mapper_0607 | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify PM mapper is able to retrieve pushed PM data from data that PM Mapper maps Type-C xml file and publish 3gpp perf VES events to message router. | ||||||||||||||||||||||||||||||||
Description | |||||||||||||||||||||||||||||||||
Release | Dublin | ||||||||||||||||||||||||||||||||
Verifies that PM Mapper maps Type-C xml files correctly and publishes 3gpp perf VES events to message router | |||||||||||||||||||||||||||||||||
Release | Dublin | ||||||||||||||||||||||||||||||||
Pre-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 |
PM_Mapper_07
measdata
using schema (e.g. 3gpp xml format).measdata
validates using 3GPP xml format with a 200 response and "XML validation successful" is outputted to the pm-mapper_output.log- Send a request to the pm-mapper with valid pm data (no_measdata.xml)
No Format |
---|
curl -v -X PUT localhost:8081/delivery/pm -H "Content-Type:application/xml" -H 'X-DMAAP-DR-META:{"productName": "NrRadio","vendorName": "Ericsson","lastEpochMicrosec": "1538478000000","sourceName": "oteNB5309","startEpochMicrosec": "1538478900000","timeZoneOffset": "UTC+05:00","location": "ftpes://192.168.0.101:22/ftp/rop/A20161224.1045-1100.bin.gz","compression": "gzip","fileFormatType": "org.3GPP.32.435#measCollec","fileFormatVersion": "V9"}' --data @tests/dcaegen2-pmmapper/pmmapper/assets/no_measdata.xml -H 'X-DMAAP-DR-PUBLISH-ID: 2' -H 'X-ONAP-RequestID: 2'
HTTP/1.1 200 OK. |
/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:
| ||||||||
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_0809 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify that PM mapper throws Event Failed validation against schema error when no managed element content is provided..Mapper correctly identifies a file that should not be mapped based on metadata filtering. | ||||||||
DescriptionVerifies 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 | 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_0910 | |||||||
---|---|---|---|---|---|---|---|---|
Test Case Name | Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filteringnon-xml file. | |||||||
Description | Verify that PM Mapper correctly determines whether identifies a file should be mapped based on the metadata against the instantiated PM Mapper filter information.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) | ||||||||
Testing Lab | Ericsson Lab | |||||||
Test Case ID | PM_Mapper_10 | |||||||
Test Case Name | Verify PM 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 | ||||||
Steps | Expected Result | 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 | ||||||
Steps | Expected Result | 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 | ||||||
Steps | Expected Result | Conclusion (Pass /Fail) | ||||||
Testing Lab | Ericsson Lab |
PM_Mapper_13
Verify PM Mapper send delete request for corresponding PM files to Data Router once events are published in Message Router.
| |||
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:
PM Mapper Component Performance Stats- Time to process 700 XML ( 1.3 MB avg ) : ~10 min
- Adapt parallelism in PM Mapper.