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 data using schema (e.g. 3gpp xml format). |
| ||||||||
8 | Verify PM mapper can validate the pm file that contains no measdata using schema (e.g. 3gpp xml format). |
| ||||||||
9 | Verify any file validation errors are logged. |
| ||||||||
10 | Verify PM mapper filter counters based on filter configuration. |
| ||||||||
11 | Verify PM mapper creates expected VES PM events for the mapped data. |
| ||||||||
12 | Verify any mapping errors are logged. |
| ||||||||
13 | Verify mapped events are publish on Message Router. |
| ||||||||
14 | 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:
< To - Do > - In progress
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) | |||||
Testing Lab | Ericsson Lab |
Test Case ID | PM_Mapper_07 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify mapper can validate the data using schema (e.g. 3gpp xml format). | ||||||||
Description | Verifies that a valid pm xml file 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 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_09 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Test Case Name | Verify any file validation errors are logged. | ||||||||
Description | Verifies that when a valid 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 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_08 | ||||
---|---|---|---|---|---|
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_09 | ||||
---|---|---|---|---|---|
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_10 | ||||
---|---|---|---|---|---|
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 |
Test Case ID | PM_Mapper_11 |
---|---|
Test Case Name |
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:
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 |
Test Case ID | PM_Mapper_12 | ||||
---|---|---|---|---|---|
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 | |||
Steps | Expected Result |
|
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=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
|
PM_Mapper_13
Steps | Expected Result |
---|---|