Versions Compared

Old Version 57

changes.mady.by.user user-3784d

Saved on

compared with

New Version 58

changes.mady.by.user Gerard Hickey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

End to End flow to be Tested:  DCAE 3GPP PM Mapper

Gliffy Diagram
namePM Mapper Sequence Diagram
pagePin7

High Level Test Cases and Status:  DCAE 3GPP PM Mapper

6 PM mapper is able to retrieve pushed PM data from Data Router.
#Test CasesStatus
1Verify PM Mapper is able to query config data from Receive Configuration From Config Binding Service

Status
colourGreen
titlePASS

2Verify PM Mapper is able subscribe to expected DR feed.
Status
colourGreen
titlePASS
3Verify health-check Health Check returns 200 when a REST GET request is sent to / healthcheck endpoint.url

Status
colourGreen
titlePASS

43Verify 3GPP PM Mapper Responds responds appropriately when no metadata is provided.

Status
colourGreen
titlePASS

54Verify 3GPP PM Mapper responds appropriately when invalid metadata is provided.

Status
colourGreen
titlePASS

5Verify that PM Mapper logs successful when a file that contains no measdata is provided

Status
colourGreen
titlePASS

7Verify PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format).
Status
colourGreen
titlePASS
86

Verify that PM mapper Mapper throws Event Failed failed validation against schema error when no managed element content is provided.

Status
colourGreen
titlePASS

97Verify 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

Status
colourGreen
titlePASS

108

Verify 3GPP PM Mapper maps Type-A file based on counter filtering and publish 3gpp perf VES events to message router

Status
colourGreen
titlePASS

9Verify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering.

Status
colourGreen
titlePASS

10

Verify that PM Mapper that PM Mapper correctly identifies a non-xml file.

Status
colourGreen
titlePASS


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 NameVerify PM Mapper is able to query config data from Receive Configuration From Config Binding Service
DescriptionPM Mapper is able to query config data from Config Binding Service once it is deployed.
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
  •  PM Mapper query to config_binding_service for config data.

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": {}}   

  • Upon failure, PM Mapper should log proper error message.
Log appropriate error message.


Conclusion (Pass /Fail)PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/
Testing LabEricsson Lab / CSIT


Test Case ID

PM_Mapper_02

Test Case NameVerify
PM Mapper is able subscribe to expected DR feed
Health Check returns 200 when a REST GET request to healthcheck url.
Description
PM Mapper subscribes to Data Router through bus controller after receiving config data from config_binding_service
Verifies that when the healthcheck endpoint is called, 200 response is returned to indicate that pm-mapper micro-service is running.
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
Once PM Mapper receive config data from config_binding_service, PM Mapper subscribing to Data Router through bus controller.

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
  • Send a GET request to pm-mapper healthcheck.



No Format
curl -v GET <PM Mapper IP>:8081/healthcheck


HTTP/1.1 200 OK



Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab


Test Case ID

PM_Mapper_03

Test Case NameVerify 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.

ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
  • Send a request to the pm-mapper without a metadata header.


No Format
curl -X PUT <PM Mapper IP>:8081/delivery
Missing Metadata.


/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:

No Format
2019-02-20T14:11:25.879Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	InstanceUUID=02bc37e3-4959-4ce5-b1fd-d93b21c7751d, RequestID=09012095-be25-4990-9e51-32701c6e3f1b, ServiceName=/delivery, InvocationID=430ede44-7fe5-4476-873a-e101ae65af73, InvokeTimestamp=2019-02-20T14:11:25.878Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost			ENTRY	
2019-02-20T14:11:25.881Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	InstanceUUID=02bc37e3-4959-4ce5-b1fd-d93b21c7751d, RequestID=09012095-be25-4990-9e51-32701c6e3f1b, ServiceName=/delivery, InvocationID=430ede44-7fe5-4476-873a-e101ae65af73, InvokeTimestamp=2019-02-20T14:11:25.878Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost	Bad Request: no metadata found under 'X-ATT-DR-META' header.	org.onap.dcaegen2.services.pmmapper.exceptions.NoMetadataException: Metadata Not found.
2019-02-20T14:11:25.889Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	ResponseCode=, InstanceUUID=02bc37e3-4959-4ce5-b1fd-d93b21c7751d, RequestID=09012095-be25-4990-9e51-32701c6e3f1b, ServiceName=/delivery, ResponseDescription=, InvocationID=430ede44-7fe5-4476-873a-e101ae65af73, Severity=, InvokeTimestamp=2019-02-20T14:11:25.878Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost, StatusCode=			EXIT




Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab/CSIT


Test Case ID

PM_Mapper_04

Test Case NameVerify 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

ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
  • 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:

No Format
2019-02-21T08:41:33.422Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	InstanceUUID=ea927d94-a91c-42f5-a145-138ee56259fe, RequestID=
DataRouterSubscriber        Request to bus controller executed with Response Code: '201' and Response Event: 'Created'.
  • 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}
],
...

..

.

Conclusion (Pass /Fail)PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/Testing LabEricsson Lab / CSITTest Case ID

PM_Mapper_03

Test Case NameVerify Health Check returns 200 when a REST GET request to healthcheck url.DescriptionVerifies that when the healthcheck endpoint is called, 200 response is returned to indicate that pm-mapper micro-service is running.ReleaseDublinPre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.Testing StepsStepsExpected Result
  • Send a GET request to pm-mapper healthcheck.
No Format
curl -v GET <PM Mapper IP>:8081/healthcheck


HTTP/1.1 200 OK
Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson LabTest Case ID

PM_Mapper_04

Test Case NameVerify 3GPP PM Mapper Responds appropriately when no metadata is providedDescription

Verify 3GPP PM Mapper responds 400 with the message "Missing Metadata." when no metadata is provided.

ReleaseDublinPre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.Testing StepsStepsExpected ResultSend a request to the pm-mapper without a metadata header.
No Format
curl -X PUT <PM Mapper IP>:8081/delivery
Missing Metadata.

/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:

No Format
2019-02-20T14:11:25.879Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	InstanceUUID=02bc37e3-4959-4ce5-b1fd-d93b21c7751d, RequestID=09012095-be25-4990-9e51-32701c6e3f1b, ServiceName=/delivery, InvocationID=430ede44-7fe5-4476-873a-e101ae65af73, InvokeTimestamp=2019-02-20T14:11:25.878Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost			ENTRY	
2019-02-20T14:11:25.881Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	InstanceUUID=02bc37e3-4959-4ce5-b1fd-d93b21c7751d, RequestID=09012095-be25-4990-9e51-32701c6e3f1b, ServiceName=/delivery, InvocationID=430ede44-7fe5-4476-873a-e101ae65af73, InvokeTimestamp=2019-02-20T14:11:25.878Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost	Bad Request: no metadata found under 'X-ATT-DR-META' header.	org.onap.dcaegen2.services.pmmapper.exceptions.NoMetadataException: Metadata Not found.
2019-02-20T14:11:25.889Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	ResponseCode=, InstanceUUID=02bc37e3-4959-4ce5-b1fd-d93b21c7751d, RequestID=09012095-be25-4990-9e51-32701c6e3f1b, ServiceName=/delivery, ResponseDescription=, InvocationID=430ede44-7fe5-4476-873a-e101ae65af73, Severity=, InvokeTimestamp=2019-02-20T14:11:25.878Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost, StatusCode=			EXIT
Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab/CSITTest Case ID

PM_Mapper_05

Test Case NameVerify 3GPP PM Mapper responds appropriately when invalid metadata is providedDescription

Verify 3GPP PM Mapper responds 400 with the message "Malformed Metadata." when invalid metadata is provided

ReleaseDublinPre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.Testing StepsStepsExpected Result
  • 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:

No Format2019-02-21T08:41:33.422Z XNIO-1 I/O-10 INFO org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber InstanceUUID=ea927d94-a91c-42f5-a145-138ee56259fe, RequestID=
05def218-0d62-4e04-9b84-93424b410af4, ServiceName=/delivery, InvocationID=5e0015e9-87f4-46a4-975f-a82a2e308926, InvokeTimestamp=2019-02-21T08:41:33.421Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost			ENTRY	
2019-02-21T08:41:33.425Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	InstanceUUID=ea927d94-a91c-42f5-a145-138ee56259fe, RequestID=05def218-0d62-4e04-9b84-93424b410af4, ServiceName=/delivery, InvocationID=5e0015e9-87f4-46a4-975f-a82a2e308926, InvokeTimestamp=2019-02-21T08:41:33.421Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost	Bad Request: Failure to parse metadata		
2019-02-21T08:41:33.432Z	XNIO-1 I/O-10	INFO	org.onap.dcaegen2.services.pmmapper.datarouter.DataRouterSubscriber	ResponseCode=, InstanceUUID=ea927d94-a91c-42f5-a145-138ee56259fe, RequestID=05def218-0d62-4e04-9b84-93424b410af4, ServiceName=/delivery, ResponseDescription=, InvocationID=5e0015e9-87f4-46a4-975f-a82a2e308926, Severity=, InvokeTimestamp=2019-02-21T08:41:33.421Z, PartnerName=, ClientIPAddress=/127.0.0.1, ServerFQDN=localhost, StatusCode=			EXIT




Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab/CSIT


Test Case ID

PM_Mapper_

06

05

Test Case Name
Verify PM mapper is able to retrieve pushed PM data from data router.
Verify PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format).
DescriptionVerifies 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
Description
ReleaseDublin
Pre-conditionsFrom 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


StepsExpected Result


  • Send a request to the pm-mapper with valid pm
files to Data Router with proper meta data. 
curl -v -X PUT https://172.18.0.10:8443/publish/1/pm.xml --data-binary @../pmfiles/pm.xml -H
  • data (no_measdata.xml)


No Format
 curl -v -X PUT localhost:8081/delivery/pm  -H "Content-Type:application/
octet-stream"  
xml"  -H 'X-DMAAP-DR-META:{"productName": "NrRadio","vendorName": "Ericsson","lastEpochMicrosec": "1538478000000","sourceName": "
csit
oteNB5309","startEpochMicrosec": "1538478900000","timeZoneOffset": "UTC+05:00","location":
"pm.xml
 "ftpes://192.168.0.101:22/ftp/rop/A20161224.1045-1100.bin.gz","compression": "gzip","fileFormatType": "org.3GPP.32.435#measCollec","fileFormatVersion": "V9"}'
-H "Authorization: Basic cG1tYXBwZXI6cG1tYXBwZXI=" -H "
 --data @tests/dcaegen2-pmmapper/pmmapper/assets/no_measdata.xml -H 'X-DMAAP-DR-
ON
PUBLISH-
BEHALF-OF: pmmapper" --location-trusted -k
Data router push the pm data to PM Mapper. PM Mapper receive the pm files
ID: 2' -H 'X-ONAP-RequestID: 2'

HTTP/1.1 200 OK.


/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log

:2019-03-06T16:14:03.549Z    -5    INFO    org.onap.dcaegen2.services.pmmapper.mapping.Mapper    InstanceUUID=cb96a84f-8f9a-4ba2-aeee-d5258024e977, RequestID=3764e4f0-709f-4ec7-bec9-28ab0679bf55, ServiceName=/delivery/pm.xml, InvocationID=cf73fc2d-d449-4b00-82ea-7a79e75c45db, InvokeTimestamp=

:

No Format
2019-03-
06T16
07T13:
14:03.533Z, PartnerName=, ClientIPAddress=/172.18.0.10, ServerFQDN=3gpppmmapper    XML validation successful Event(httpServerExchange=HttpServerExchange{ PUT /delivery/pm.xml request {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], X-DMAAP-DR-PUBLISH-ID=[1551888840226.dmaap-dr-node], User-Agent=[Java/1.8.0_111], 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" }], X-DMAAP-DR-RECEIVED=[2019-03-06T16:14:00.225Z;from=172.18.0.1;by=172.18.0.10], Connection=[keep-alive], Authorization=[Basic dXNlcm5hbWU6cGFzc3dvcmQ=], X-ONAP-RequestID=[3764e4f0-709f-4ec7-bec9-28ab0679bf55], Content-Type=[application/octet-stream], Content-Length=[31690], X-InvocationID=[fb58765a-6946-4fc1-8cd8-87116c7a1546], Host=[3gpppmmapper:8081]} response {Connection=[keep-alive], Content-Length=[2], Date=[Wed, 06 Mar 2019 16:14:03 GMT]}},   

...

..

2019-03-06T16:14:03.552Z    -5    INFO    org.onap.dcaegen2.services.pmmapper.mapping.Mapper    InstanceUUID=cb96a84f-8f9a-4ba2-aeee-d5258024e977, RequestID=3764e4f0-709f-4ec7-bec9-28ab0679bf55, ServiceName=/delivery/pm.xml, InvocationID=cf73fc2d-d449-4b00-82ea-7a79e75c45db, InvokeTimestamp=2019-03-06T16:14:03.533Z, PartnerName=, ClientIPAddress=/172.18.0.10, ServerFQDN=3gpppmmapper    Mapping event            

2019-03-06T16:14:03.562Z    -5    INFO    org
54:21.346Z	-4	INFO	org.onap.dcaegen2.services.pmmapper.mapping.Mapper	InstanceUUID=d57a755d-cc56-4c1f-bbdc-1c28ff5d2f81, RequestID=2, ServiceName=/delivery/pm, InvocationID=afbcedd4-578a-41fb-b426-c6a5e8937e17, InvokeTimestamp=2019-03-07T13:54:21.335Z, PartnerName=, ClientIPAddress=/172.18.0.1, ServerFQDN=localhost	XML validation successful




Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab


Test Case ID

PM_Mapper_06

Test Case NameVerify that PM mapper throws Event Failed validation against schema error when no managed element content is provided..
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
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
  • Send a request to the pm-mapper with invalid pm data (no_managed_element.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_managed_element.xml -H 'X-DMAAP-DR-PUBLISH-ID: 2' -H 'X-ONAP-RequestID: 2'

/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:

No Format
2019-03-06T15:47:19.720Z	-3	INFO	org.onap.dcaegen2.services.pmmapper.mapping.
Mapper    InstanceUUID=cb96a84f-8f9a-4ba2-aeee-d5258024e977, RequestID=3764e4f0-709f-4ec7-bec9-28ab0679bf55, 
Mapper	InstanceUUID=d57a755d-cc56-4c1f-bbdc-1c28ff5d2f81, RequestID=2, ServiceName=/delivery/pm
.xml
, InvocationID=
cf73fc2d
1712fba7-
d449
e073-
4b00
47d3-
82ea
b1bd-
7a79e75c45db
0c428a83fdb9, InvokeTimestamp=2019-03-
06T16
06T15:
14
47:
03
18.
533Z
717Z, PartnerName=, ClientIPAddress=/172.18.0.
10
1, ServerFQDN=localhost	XML validation failed




Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab


Test Case ID

PM_Mapper_07

Test Case NameVerify that PM Mapper maps Type-C xml file and publish 3gpp perf VES events to message router.
DescriptionVerifies that PM Mapper maps Type-C xml files correctly and publishes 3gpp perf VES events to message router
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


ServerFQDN=3gpppmmapper    Data mapped successfully            2019-03-06T16:14:03.563Z    -5    INFO    org.onap.dcaegen2.services.pmmapper.App    InstanceUUID=cb96a84f-8f9a-4ba2-aeee-d5258024e977, RequestID=3764e4f0-709f-4ec7-bec9-28ab0679bf55, ServiceName=/delivery/pm.xml, InvocationID=cf73fc2d-d449-4b00-82ea-7a79e75c45db, InvokeTimestamp=2019-03-06T16:14:03.533Z, PartnerName=, ClientIPAddress=/172.18.0.10, ServerFQDN=3gpppmmapper    Event Processed   
StepsExpected Result



  • Check subscriber info in Data Router.



Conclusion (Pass /Fail)PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/
Testing LabEricsson Lab / CSIT


Test Case ID

PM_Mapper_

07

08

Test Case NameVerify
PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format).
3GPP PM Mapper maps Type-A file based on counter filtering and publish 3gpp perf VES evnets to message router
DescriptionVerifies 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
PM Mapper maps Type-A xml files correctly and publishes 3gpp perf VES events to message router
ReleaseDublin
Pre-conditionsFrom 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


StepsExpected Result
  • 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
xml"
  • octet-stream"  -H
  • 'X-DMAAP-DR-META:{"productName":
  • "NrRadio","vendorName":
  • "Ericsson","lastEpochMicrosec":
  • "1538478000000","sourceName":
  • "
oteNB5309
  • csit","startEpochMicrosec":
  • "1538478900000","timeZoneOffset":
  • "UTC+05:00","location":
  • "
ftpes://192.168.0.101:22/ftp/rop/A20161224.1045-1100.bin.gz
  • pm.xml","compression":
  • "gzip","fileFormatType":
  • "org.3GPP.32.435#measCollec","fileFormatVersion":
  • "V9
"}' --data @tests/dcaegen2-pmmapper/pmmapper/assets/no_measdata.xml -H '
  • "}' -H "Authorization: Basic cG1tYXBwZXI6cG1tYXBwZXI=" -H "X-DMAAP-DR-
PUBLISH
  • ON-BEHALF-
ID: 2' -H 'X-ONAP-RequestID: 2' HTTP/1.1 200 OK
  • OF: pmmapper" --location-trusted -k



Data router push the pm data to PM Mapper. PM Mapper receive the pm files.

/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log

: No Format2019-03-07T13:54:21.346Z -4 INFO org.onap.dcaegen2.services.pmmapper.mapping.Mapper InstanceUUID=d57a755d-cc56-4c1f-bbdc-1c28ff5d2f81, RequestID=2, ServiceName=/delivery/pm, InvocationID=afbcedd4-578a-41fb-b426-c6a5e8937e17, InvokeTimestamp=

:

2019-03-

07T13

06T16:

54:21.335Z, PartnerName=, ClientIPAddress=/172.18.0.1, ServerFQDN=localhost XML validation successful Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab
Test Case ID

PM_Mapper_08

Test Case NameVerify that PM mapper throws Event Failed validation against schema error when no managed element content is provided..
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
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps
curl -v -X PUT localhost:8081/delivery/pm -H "Content-Type:application/xml" -H '

14:03.549Z    -5    INFO    org.onap.dcaegen2.services.pmmapper.mapping.Mapper    InstanceUUID=cb96a84f-8f9a-4ba2-aeee-d5258024e977, RequestID=3764e4f0-709f-4ec7-bec9-28ab0679bf55, ServiceName=/delivery/pm.xml, InvocationID=cf73fc2d-d449-4b00-82ea-7a79e75c45db, InvokeTimestamp=2019-03-06T16:14:03.533Z, PartnerName=, ClientIPAddress=/172.18.0.10, ServerFQDN=3gpppmmapper    XML validation successful Event(httpServerExchange=HttpServerExchange{ PUT /delivery/pm.xml request {Accept=[text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], X-DMAAP-DR-PUBLISH-ID=[1551888840226.dmaap-dr-node], User-Agent=[Java/1.8.0_111], 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_managed_element.xml -H 'X-DMAAP-DR-PUBLISH-ID: 2' -H 'X-ONAP-RequestID: 2'

/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:

2019-03-06T15:47:19.720Z -3 INFO org.onap.dcaegen2.services.pmmapper.mapping.Mapper InstanceUUID=d57a755d-cc56-4c1f-bbdc-1c28ff5d2f81, RequestID=2, ServiceName=/delivery/pm, InvocationID=1712fba7-e073-47d3-b1bd-0c428a83fdb9, InvokeTimestamp=2019-03-06T15:47:18.717Z, PartnerName=, ClientIPAddress=/172.18.0.1, ServerFQDN=localhost XML validation failed

], X-DMAAP-DR-RECEIVED=[2019-03-06T16:14:00.225Z;from=172.18.0.1;by=172.18.0.10], Connection=[keep-alive], Authorization=[Basic dXNlcm5hbWU6cGFzc3dvcmQ=], X-ONAP-RequestID=[3764e4f0-709f-4ec7-bec9-28ab0679bf55], Content-Type=[application/octet-stream], Content-Length=[31690], X-InvocationID=[fb58765a-6946-4fc1-8cd8-87116c7a1546], Host=[3gpppmmapper:8081]} response {Connection=[keep-alive], Content-Length=[2], Date=[Wed, 06 Mar 2019 16:14:03 GMT]}},   

...

..





StepsExpected Result
  • Send a request to the pm-mapper with invalid pm data (no_managed_element.xml)
No Format
No Format


Conclusion (Pass /Fail)PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/
Testing LabEricsson Lab


Test Case ID

PM_Mapper_09

Test Case NameVerify that PM Mapper correctly identifies a file that should not be mapped based on metadata filtering.
DescriptionVerify that PM Mapper correctly determines whether a file should be mapped based on the metadata against the instantiated PM Mapper filter information.
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
  1. Send a request to pm-mapper where the metadata vendor name does not match the filter vendor name defined for the pm-mapper


No Format
curl -v -X PUT localhost:8081/delivery/pm  -H "Content-Type:application/xml"  -H 'X-DMAAP-DR-META:{"productName": "gnb","vendorName": "Anon","lastEpochMicrec": "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/meas_result.xml -H 'X-DMAAP-DR-PUBLISH-ID: 2' -H 'X-ONAP-RequestID: 2'


/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:

No Format
2019-03-14T14:03:19.768Z	-8	INFO	org.onap.dcaegen2.services.pmmapper.filtering.MetadataFilter	InstanceUUID=0e53e6f1-e411-4132-9d6e-840ce0eca178, RequestID=2, ServiceName=/delivery/pm, InvocationID=1ded3e0f-6863-462f-8f35-8106c4d1e1fd, InvokeTimestamp=2019-03-14T14:03:19.764Z, PartnerName=, ClientIPAddress=/172.18.0.1, ServerFQDN=localhost	Metadata does not match any filters,





Conclusion (Pass /Fail)

PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/

Testing LabEricsson Lab



Test Case ID

PM_Mapper_10

Test Case NameVerify that PM Mapper correctly identifies a non-xml file.
DescriptionVerify that PM Mapper correctly identifies a non-xml file by correctly outputting the expected message
ReleaseDublin
Pre-conditionsFrom the above section "Deployment" a test environment with all the required components - Config Binding Service, Consul and PM Mapper service.
Testing Steps


StepsExpected Result
    • Send a request to the pm-mapper that contains non-xml file.



No Format
curl -v -X PUT localhost:8081/delivery/pm  -H "Content-Type:application/xml"  -H 'X-DMAAP-DR-META:{"productName": "gnb","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/diff_vendor_metadata.json -H 'X-DMAAP-DR-PUBLISH-ID: 2' -H 'X-ONAP-RequestID: 2'


/var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log:

No Format
2019-04-09T14:00:08.780Z	-8	INFO	org.onap.dcaegen2.services.pmmapper.filtering.MeasFilterHandler	InstanceUUID=63d0106e-5ba1-45b1-b0f0-9debe9eb2be7, RequestID=2, ServiceName=/delivery/pm, InvocationID=5598c331-9d9d-4679-8cb2-c30231f25495, InvokeTimestamp=2019-04-09T14:00:08.775Z, PartnerName=, ClientIPAddress=/172.18.0.1, ServerFQDN=localhost	PM measurement file type not supported



Conclusion (Pass /Fail)PASS - https://jenkins.onap.org/job/dcaegen2-pmmapper-master-csit-pmmapper/
Testing LabEricsson 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 CriteriaMeasurementComments
XML to VES Message / Sec2 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 time0.018100% success.