Table of Contents maxLevel 2
...
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ensure the response from the Network Discovery Context Builder align with Common Model v.1 | Verify the response from Network Discovery Context Builder is using Common Model v.1 Verify all of the underlying context builders receive a ‘Get context” request from POMBA-CA with the following 3 parameters: ServiceInstanceId, modelVersionId, and modelInvariantId | PASS |
| |||||||||||
| Ensure the response from the Network Discovery Context Builder align with Common Model v.1 | Verify the response from Network Discovery Context Builder is using Common Model v.1 | PASS |
| |||||||||||
| Ensure the response from the Network Discovery Context Builder align with Common Model v.1 | Verify the response from Network Discovery Context Builder is using Common Model v.1 | PASS |
| |||||||||||
| Verify XFromAppId is needed in the Event |
| PASS |
| |||||||||||
| Verify xTransactionId is needed in the Event |
| PASS |
| |||||||||||
| Verify customerId is not a mandatory attributes in the Even |
| PASS |
| |||||||||||
| Verify serviceType is not a mandatory attributes in the Even |
| PASS |
| |||||||||||
| Retrieve model data for Network Discovery context builder |
| PASS |
|
Context Builder: AAI
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Deploy MS | Verify AAI Context Builder MS starts up without error | PASS | David Stangl |
| ||||||||||
| success path | Verify that the AAI Context Builder service is able to process an incoming context request. | PASS |
| |||||||||||
| bad credentials | Verify that the AAI Context Builder service fails to process a context request from a sender that cannot be authenticated. An error response should be returned to the Context Aggregator. | PASS |
| |||||||||||
| sonar report | Verify that the AAI Context Builder service Sonar report does not include any critical level issues that need to be resolved. | PASS |
| |||||||||||
| wiki update | Verify that the ONAP developer wiki has been updated to include pertinent information for the development and usage of the AAI Context Builder. | PASS |
|
Context Builder: AAI - OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Deploy AAI Context Builder in OOM | Verify that the AAI Context Builder can be deployed in a Kubernetes environment | PASS |
| |||||||||||
| Login to the AAI Context Builder pod and ensure it is running | Verify that the AAI Context Builder pod is reachable and SDC Context Builder is running | PASS |
| |||||||||||
| Delete the deployed AAi Context Builder from OOM | Verify that the AAI Context Builder pod can be deleted by using the standard OOM deletion instruction | PASS |
|
...
Context Builder: AAI - APIv1 Update
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| aai-context-builder | service | context | success | Verify that the AAI Context Builder is capable of receiving a context request that includes only the serviceInstanceId parameter. | PASS |
| |||||||||||||||||||
| aai-context-builder | service | v1 | context | Verify that the AAI Context Builder is able to accept context requests that explicitly specify v1 of the API. | PASS |
| |||||||||||||||||||
| aai-context-builder | swagger | index.html | Verify that the AAI Context Builder provides swagger documentation for the latest API (v1). | FAIL |
| Bug entered:
| ||||||||||||||||||
| aai-context-builder | service | context | missing serviceInstanceId | Verify that the AAI Context Builder service will fail to process a context request that does not provide a service-Instance-Id. An error response should be returned to the Context Aggregator. | PASS |
| |||||||||||||||||||
| aai-context-builder | service | context | header | missing application id | Verify that the AAI Context Builder service will fail to process a context request that does not provide an AppId in the header. An error response should be returned to the Context Aggregator. | PASS |
| |||||||||||||||||||
| aai-context-builder | service | context | service not in AAI | Verify that the AAI Context Builder service returns a suitable response when the service for which context is requested cannot be found in the A&AI database. |
|
Context Builder: SDC
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Deploying SDC context builder service | Verify that SDC context builder can be deployed (manually) | PASS |
| |||||||||||
| Send API request to SDC context builder | Verify that an API request can be sent to SDC context builder | PASS |
| |||||||||||
| Send API request to SDC context builder with error in modelVersionId | Verify that an error occurs when the null value or missing modelVersionId | PASS |
| |||||||||||
| Send API request to SDC context builder - missing AppId from the header | Verify that missing parameter returns proper error code in response | PASS |
| |||||||||||
| Send API request to SDC context builder - missing basic auth from the header | Verify that missing parameter returns proper error code in response | PASS |
| |||||||||||
| Check sonar report | Verify that no critical sonar issues | PASS |
| |||||||||||
| Review wiki page | Verify that the ONAP developer wiki has been updated with information regarding the SDC Builder. | PASS |
|
Context Builder: SDC - OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Deploy SDC Context Builder in OOM | Verify that the SDC Context Builder can be deployed in a Kubernetes environment | PASS |
| |||||||||||
| Login to the SDC Context Builder pod and ensure it is running | Verify that the SDC Context Builder pod is reachable and SDC Context Builder is running | PASS |
| |||||||||||
| Delete the deployed SDC Context Builder from OOM | Verify that the SDC Context Builder pod can be deleted by using the standard OOM deletion instruction | PASS |
|
...
Context Builder: SDC - APIv1 Update
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Deploy SDC Context Builder in OOM | Verify that the SDC Context Builder can be deployed in a Kubernetes environment | Pass |
| |||||||||||||||||||||
| SDC-context-builder | service | context | success | Verify that the SDC Context Builder is capable of receiving a context request that includes only the modelVersionId parameter. | Pass |
| |||||||||||||||||||||
api v1 - SDC-context-builder | service |context ignores extra parameters | Verify that the SDC Context Builder is able to accept context requests that explicitly specify v1 of the API. API contains parameters extra parameters like serviceType and customerId.
| Pass |
| |||||||||||||||||||||
api v1 - SDC-context-builder | service | context do not include serviceType | Verify that the SDC Context Builder is able to accept context requests that explicitly specify v1 of the API. Absence of serviceType should not cause problem. | Pass |
| |||||||||||||||||||||
api v1 - SDC-context-builder | service | context do not include customerId | Verify that the SDC Context Builder is able to accept context requests that explicitly specify v1 of the API. Absence of customerId should not cause problem. | Pass |
| |||||||||||||||||||||
| SDC-context-builder | swagger | index.html | Verify that the SDC Context Builder provides swagger documentation for the latest API (v1). | FAIL |
| Defect entered:
| ||||||||||||||||||||
| SDC-context-builder | service | context | missing modelVersionId | Verify that the SDC Context Builder service will fail to process a context request that does not provide a service-Instance-Id. An error response should be returned to the Context Aggregator. | Pass |
| |||||||||||||||||||||
| SDC-context-builder | service | context | model version id not in SDC | Verify that the SDC Context Builder service returns a suitable response when the service for which context is requested cannot be found in SDC. | Pass |
|
Context Builder: Network Discovery
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| api | network-discovery-context-builder | service | context | decomposition request | Verify that the Network Discovery Context Builder generates a service instance decomposition action when it is sent a POMBA request from the Context Aggregator. The decomposition request should utilize the proper credentials. | PASS |
| |||||||||||
| api v1 | network-discovery-context-builder | service | context | decomposition request | Verify that the Network Discovery Context Builder generates a service instance decomposition action when it is sent a POMBA request from the Context Aggregator. The decomposition request should utilize the proper credentials. The request includes new API v2 headers. | PASS |
| |||||||||||
| api v1 | network-discovery-context-builder | service | context | ignores extra parameters | Verify that the Network Discovery Context Builder accepts a request that contains more query parameters than required (context-aggregator may send other parameters like modelVersionId and modelInvariantId). | PASS |
| |||||||||||
| api v1 | network-discovery-context-builder | service | context | no X-ONAP-PartnerName | Verify that the Network Discovery Context Builder returns an error to the Context Aggregator when its request does not include a PartnerName header. | PASS |
| |||||||||||
| api v1 | network-discovery-context-builder | service | context | using X-FromAppId | Verify that the Network Discovery Context Builder accepts X-FromAppId in lieu of X-ONAP-PartnerName | PASS |
| |||||||||||
| api v1 | network-discovery-context-builder | service | context | using X-TransactionId | Verify that the Network Discovery Context Builder accepts X-TransactionId in lieu of X-ONAP-RequestID | PASS |
| |||||||||||
| api | network-discovery-context-builder | service | context | bad username | Verify that the Network Discovery Context Builder API disallows requests when the provided username is not correct. | PASS |
| |||||||||||
| api | network-discovery-context-builder | service | context | bad password | Verify that the Network Discovery Context Builder API disallows requests when the provided password is not correct. | PASS |
| |||||||||||
| api | network-discovery-context-builder | service | context | no serviceInstanceId | Verify that the Network Discovery Context Builder returns an error to the Context Aggregator when its request does not include a service instance ID. | PASS |
| |||||||||||
| api | network-discovery-context-builder | service | context | service decomposer down | Verify that the Network Discovery Context Builder returns an error to the Context Aggregator when an audit request cannot be carried out due to an unresponsive Service Decomposer. | PASS |
| |||||||||||
| api | network-discovery-context-builder | service | context | service not in aai | Verify that the Network Discovery Context Builder returns an error to the Context Aggregator when an audit request cannot be carried out due to the specified service not being available in the A&AI database. | PASS |
| |||||||||||
| api v2 | network-discovery-context-builder | service | context | X-ONAP-TransactionId | Verify that the Network Discovery Context Builder returns an error to the Context Aggregator when its request does not include a service instance ID. | PASS |
| |||||||||||
| logging | network-discovery-context-builder | audit request | Verify that the Network Discovery Context Builder logs appropriate information upon reception of an audit request. | PASS |
| |||||||||||
| logging | network-discovery-context-builder | audit request | missing parameter | Verify that the Network Discovery Context Builder logs appropriate information upon reception of an audit request that is missing the required service instance ID. | PASS |
| |||||||||||
| api | network-discovery-context-builder | service | context | swagger documentation | Verify that the micro service API provides a swagger description of the API parameters, versions, etc. | PASS |
| |||||||||||
| wiki | developer documentation | Verify that the ONAP developer wiki has been updated with information regarding the Network Discovery Context Builder. | PASS |
| |||||||||||
| properties file | default resource types | PASS |
| ||||||||||||
| properties file | no resource types | PASS |
| ||||||||||||
| properties file | unknown resource type | PASS |
| ||||||||||||
| properties file | missing resource type | PASS |
| ||||||||||||
| Network-discovery-context-builder sends request | To Network Discovery for each resource type | Verify that the Network Discovery Context Builder sends one Network Discovery request for each resource found in the response from the Service Decomposition service. | PASS |
| |||||||||||
| Network-discovery-context-builder disallows|unsupported resource types | Verify that the Network Discovery Context Builder is able to produce a final audit report when one (or more) of the resource discovery requests was rejected due to the resource type not being supported. The final report should include error messaging for the unsupported resource types. | PASS |
| |||||||||||
| Network-discovery-context-builder | timeout is configurable | Verify that the Network Discovery Context Builder timeout is configurable and resource discovery responses will be timeout based on the configured time | PASS |
| |||||||||||
| Network-discovery-context-builder disallows| malformed request | Verify that the Network Discovery Context Builder disallows the resource discovery requests and gets rejected due to malformed request | PASS |
| |||||||||||
| Network-discovery-context-builder disallows| missing parameter| ServiceInstanceId and ONAP-PartnerName | Verify that the Network Discovery Context Builder disallows the resource discovery requests and gets rejected due missing ServiceInstanceId and ONAP-ParameterName. The final report should include proper error code | PASS |
| |||||||||||
| Network-discovery-context-builder| Not able to discover resource type | Verify that the Network Discovery Context Builder is able to generate a response back to context aggregator without any resource type information | PASS |
| |||||||||||
| Network Discovery Context Builder returns failure| Network-Discovery is down | Verify that the Network Discovery Context Builder returns a failure response to the Context Aggregator if resource discovery cannot be performed due to the unavailability of the Network Discovery service.The Network Discovery Context Builder disallows to accept a discovery request from the Network Discovery micro service
| PASS |
| |||||||||||
| Network-discovery-context-builder disallows request | when network-discovery credentials incorrect or missing | Verify that the Network Discovery Context Builder returns an error when network-discovery credentials are incorrect | PASS |
| |||||||||||
| logging | network-discovery-context-builder | audit request | Verify that the Network Discovery Context Builder logs appropriate information when receiving the service decomposition response and generating resource discovery requests. | PASS |
| |||||||||||
| logging | network-discovery-context-builder | audit request | Verify that the Network Discovery Context Builder logs appropriate information when receiving resource discovery results. | PASS |
| |||||||||||
| wiki | developer documentation | Verify that the ONAP developer wiki has been updated with information regarding the "discovery" part of the Network Discovery Context Builder. | PASS |
|
Context Builder: Network Discovery - OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| oom | install | network discovery context builder | Verify that the Network Discovery Context Builder can be deployed using OOM. | PASS | David Stangl |
|
...
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GET A&AI service instance details - success scenario | Verify that A&AI data is populated correctly | PASS |
| |||||||||||||||||||
| GET A&AI service instance details - missing parameter(AppId) | Verify that missing parameter returns proper error code in response | PASS |
| |||||||||||||||||||
| GET A&AI service instance details - missing parameter(serviceInstanceId) | Verify that missing parameter returns empty json response | PASS |
| |||||||||||||||||||
| GET A&AI service instance details - invalid parameter(serviceInstanceId) | Verify that missing parameter returns proper error code in response | PASS |
| |||||||||||||||||||
| Malformed GET Request to fetch the data | Verify that malformed GET request returns proper error code in response | PASS |
| |||||||||||||||||||
| service-decomposition | service includes VNFs | Verify that VNF resources that comprise a services can be returned by the service decomposition micro service. | PASS |
| |||||||||||||||||||
| service-decomposition | service includes VNFCs | Verify that VNFC resources that comprise a services can be returned by the service decomposition micro service. | PASS |
| |||||||||||||||||||
| service-decomposition | service includes VFModules | Verify that VFModule resources that comprise a services can be returned by the service decomposition micro service. | PASS |
| |||||||||||||||||||
| service-decomposition | service includes VServers | Verify that VServer resources that comprise a services can be returned by the service decomposition micro service. | PASS |
| |||||||||||||||||||
| service-decomposition | service includes L3 network | Verify that L3 network resources that comprise a services can be returned by the service decomposition micro service. | PASS |
| |||||||||||||||||||
| GET Generic VNF output for supported resources with different combinations of the data | Verify that all supported resource types should be populated in correct hierarchy | PASS |
| |||||||||||||||||||
| service-decomposition | interrelated resources don't result in redundancy or unrelated service resources | Verify that the service decomposition micro service returns only components directly related to the service and does not return duplicate components when the components are related to each other recursively. | PASS |
| |||||||||||||||||||
| service-decomposition | service not found | Verify that the service decomposition micro service returns an error code and message when the service that is requested cannot be located. | PASS |
| |||||||||||||||||||
| service-decomposition | X-ONAP-RequestID not specified | Verify that the service decomposition micro service generates a unique transaction ID when one had not been specified in the request. | FAIL |
| X-ONAP-RequestID not generated by microservice. Not so much an issue because the only caller currently passes in an ID. Tracking this issue outside of story. | ||||||||||||||||||
| service-decomposition | X-ONAP-RequestID specified | Verify that the service decomposition micro service response uses the same unique transaction ID as was specified in the request. | FAIL |
| X-ONAP-RequestID not returned in response to caller. Tracking this issue outside of story: | ||||||||||||||||||
| service-decomposition | X-ONAP-PartnerName | Verify that the service decomposition micro service response uses the same unique ONAP partner name as was specified in the request. | FAIL |
| X-ONAP-PartnerNAme not returned in response to caller. Tracking this issue outside of story. | ||||||||||||||||||
| service-decomposition | A&AI connection severed | Verify that the service decomposition micro service response includes an error code and error message when a lookup fails due to no connection to A&AI. | PASS |
| |||||||||||||||||||
| service-decomposition | mini-soak | Verify that the service decomposition micro service can handle multiple and sometimes concurrent requests for decomposition without causing issue with the process (memory leaks, etc.) or providing callers with bad information (mixing up response content, etc.) | PASS |
| |||||||||||||||||||
| service-decompoistion | swagger API documentation | Verify that the API documentation for the service decomposition micro service is available. | PASS |
|
POMBA Validation Service
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OOM | deployment | Verify that the Validation Service can be deployed in a POMBA environment with all the appropriate configuration, etc. | PASS |
| |||||||||||||||||||
| OOM | removal | Verify that the Validation Service can be undeployed from a POMBA environment. | PASS |
| |||||||||||||||||||
| pomba-validation-service | RULES-VALIDATION | success | Verify that the Validation Service can successfully consume a RULES-VALIDATION event, employ validation rules and return a validation report to the POA-AUDIT-RESULT queue in DMaaP. | PASS |
| |||||||||||||||||||
| pomba-validation-service | topic creation | POA-AUDIT-RESULT | Verify that the Validation Service is able to create the POA-AUDIT-RESULT queue in DMaaP for the purposes of publishing the results of evaluations. This should be done at the time of the very first outgoing DMaaP event. | FAIL |
| General issue with components writing to DMaaP without an existing topic. Topic is created but message dropped. Subsequent messages are written correctly. Will be dealt with outside of this story.
| ||||||||||||||||||
| sonar report | Verify that the Validation Service Sonar report does not include any critical level issues that need to be resolved. | PASS |
|
POMBA Validation Service - Rules: AAI vs. ND attribute comparison
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| aai vs. nd | all attributes | match | Verify that there are no violations reported when the attributes reported by both the AAI Context Builder and Network Discovery Context Builder have the same values. | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | vm.uuid comparision | mismatch | Verify that there is a MAJOR violation reported when the vm.uuid values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | FAIL |
| Report is generated but there are some issues:
| |||||||||||||||||||||||
| aai vs. nd | vm.name comparision | mismatch | Verify that there is a MAJOR violation reported when the vm.name values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | FAIL |
| Report is generated but there are some issues:
| |||||||||||||||||||||||
| aai vs. nd | vm.lockedBoolean comparison | mismatch | Verify that there is a MAJOR violation reported when the vm.lockedBoolean values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | FAIL |
| aai vs. nd | vm.hostName comparison | mismatch | Verify that there is aReport is generated but there are some issues:
| ||||||||||||||||||||||
| aai vs. nd | vm.hostName comparison | mismatch | Verify that there is a MAJOR violation reported when the vm.hostName values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | FAIL |
| Report is generated but there are some issues:
| |||||||||||||||||||||||
| aai vs. nd | vm.imageId comparison | mismatch | Verify that there is a MAJOR violation reported when the vm.imageId values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | FAIL |
| Report is generated but there are some issues:
| |||||||||||||||||||||||
| aai vs. nd | vm.name comparision | mismatch | case sensitivity | Verify that a mismatch is detected when the value for an attribute is the same but just not expressed in the same case. (e.g. "123fred" vs. "123Fred") | FAIL |
| Report is generated but there are some issues:
| 434
| ||||||||||||||||||||||
| aai vs. nd | vm.hostName comparison | dataQuality error from nd builder | Verify that there is no violation reported when the vm.hostName reported by the Network Discovery Context Builder has an associated dataQuality of "error". | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | vm.imageIdcomparison | attribute missing from nd builder | Verify that there is no violation reported when the Network Discovery Context Builder fails to include a vm.imageId attribute while the AAI Context Builder does. | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | network.uuid comparison | mismatch | Verify that there is a MAJOR violation reported when the network.uuid values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | network.name comparison | mismatch | Verify that there is a MAJOR violation reported when the network.namevalues reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | network.adminState comparison | mismatch | Verify that there is a MAJOR violation reported when the network.adminStatevalues reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | network.sharedNetworkBoolean comparison | mismatch | Verify that there is a MAJOR violation reported when the network.sharedNetworkBoolean values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value. | PASS |
| ||||||||||||||||||||||||
| aai vs. nd | multiple violations | Verify that multiple attribute comparison violations can be reported. | PASS |
|
POMBA Validation Service - Rules: AAI vs. SDC VNF comparison
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SDC and AAI output matches | Verify that the Validation Service does not detect any issues when the SDC and AAI context builders provide the same number of VNFCs, the vnfc-type and vf-module-type for each VNFC match and the AAI provides a nfc-naming-code for each VNFC. | PASS |
| |||||||||||||||||||||||
| vnfc-type | mismatch | Verify that the Validation Service is able to detect that the vnfc-type for a VNFC as reported by the SDC and AAI context builders does not match. An ERROR level violation should be reported. | PASS |
| |||||||||||||||||||||||
| vnfc-count | SDC reports more than AAI | Verify that the Validation Service is able to detect when the number of VNFCs reported by the SDC Context Builder is greater than the number of VNFCs reported by the AAI Context Builder. A WARN level violation should be reported. | PASS |
| |||||||||||||||||||||||
| vnfc-count | SDC reports fewer than AAI | Verify that the Validation Service does not detect a violation when the SDC Context Builder reports fewer VNFCs than | the AAI Context Builder.
| vf-module | mismatch | Verify that the Validation Service is able to detect when the vf-module name for a VF module as reported by the SDC and AAI context builders does not match. A CRITICAL level violation should be reported.the AAI Context Builder. | PASS |
|
POMBA Data Router
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||
| data-router | orchestration-event-service | orchestration-event | success | no transaction ID | Verify that the Data Router can successfully process an incoming request and produce a DMaaP event with the information. | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | success | transaction ID provided | Verify that the Data Router can successfully process an incoming request that includes a transaction ID to use. | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | success | multiple services | Verifythat the Data Router can successfully process an incoming request and produce | PASS |
| |||||||||||
| data-router | POA-AUDIT-RESULT | success | Verify that the Data Router monitors the DMaaP POA-AUDIT-RESULT queue and is able to process events tat are found, resulting in a request to the SDS. | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | missing service instance ID | Verify that the Data Router rejects an incoming request that does not specify a service instance ID. | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | missing model version ID | Verify that the Data Router rejects an incoming request that does not specify a service instance ID. | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | DMaaP not available | Verify that the Data Router responds with an error code when the DMaaP service is not accessible when a request is being processed. | PASS |
| |||||||||||
| data-router | POA-AUDIT-RESULT | malformed event | Verify that the Data Router fails gracefully when a POA-AUDIT-RESULT event is being processed but the content of the event prevents proper processing. | PASS |
| |||||||||||
| data-router | POA-AUDIT-RESULT | SDS not available | Verify that the Data Router fails gracefully when a POA-AUDIT-RESULT event is being processed and the SDS is not available to receive requests. | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | bad certificate | Verify that the Data Router rejects connections from clients that do not utilize the correct certificate (or the certificate is bad). | PASS |
| |||||||||||
| data-router | orchestration-event-service | orchestration-event | missing certificate | Verify that the Data Router rejects connections from clients that do not utilize the correct keystore password. | PASS |
|
...
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||
| data-router | v1 | orchestration-event-service | orchestration-event | Verify that the orchestration-event API operation only needs to be provided the serviceInstanceId, modelVersionId and modelInvariantId parameters | PASS |
| |||||||||||||||||||
| data-router | orchestration-event-service | orchestration-event | Verify that the latest version (v1) of the orchestration-event operation is invoked when the API version is not explicitly specified. | FAIL |
| Bug entered:
| ||||||||||||||||||
| data-router | orchestration-event-service | orchestration-event | Verify that if the v1 API is used to send an orchestration-event operation and the two deprecated parameters – customerId and serviceType – are included, either a POA-AUDIT-INIT message is written without the offending parameters or the request is entirely rejected. | PASS |
| |||||||||||||||||||
| POA-AUDIT-RESULT | processing | Verify that the Data Router remains capable of consuming and processing POA-AUDIT-RESULT events. | PASS |
|
POMBA Data Router - Audit Report Additional Fields
| Test Case | Description | Status | Owner | Date | JIRA link | Comment | ||||||||||||||||
| orchestration-event-service | orchestration-event | X- | ONAP-RequestIDTransactionId | Verify that the POA-AUDIT-RESULT messages produced by the Validation Service include the X- | ONAP-Request-IDTransactionId value that was originally sent in the post-orchestration audit request so that this information can appear in the final audit report. | PASS |
| |||||||||||||||||
| orchestration-event-service | orchestration-event | missing X- | ONAP-RequestIDTransactionId | Verify that the POA-AUDIT-RESULT messages produced by the Validation Service includes an X- | ONAP-Request-IDTransactionId value generated by the Data Router in the case where the original orchestration event did not include one. | PASS |
| |||||||||||||||||
| orchestration-event-service | orchestration-event | X-FromAppId | Verify that the POA-AUDIT-RESULT messages produced by the Validation Service include an X-FromAppId attribute that indicates the application that initiated the audit. (i.e. The client that sent the orchestration-event) | FAIL |
| Big entered:
|
POMBA Search Data Service
...