Context Aggregator
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| Deploy context aggregator Micro Service | Verify context aggregator MS starts up without error | PASS | LOG-519 - Getting issue details... STATUS | |||
| Consume audit event from “event bus” (message router) | Verify audit event is consumed by POMBA-CA and is processed successfully | PASS | LOG-519 - Getting issue details... STATUS | |||
| Retrieve model data for all underlying context builders | Verify POMBA-CA is able to retrieve model data if all of the .properties files for all of the context builders exist in config/builders directory Verify all of the underlying context builders receive a ‘Get context” request from POMBA-CA Verify a response is received at POMBA-CA from all under lying context builders | PASS | LOG-519 - Getting issue details... STATUS | |||
| Unable to retrieve model data | Malformed .properties file for at least one of the underlying context builders | Verify POMBA-CA is unable to retrieve model data if one of the .properties files for a context builder (e.g. aai.properties) is misconfigured | PASS | LOG-519 - Getting issue details... STATUS | |||
| Unable to retrieve model data | Missing .properties file for a context builder | Verify POMBA-CA is unable to retrieve model data if one of the .properties files for a context builder (e.g. aai.properties) is missing from config/builders directory | PASS | LOG-519 - Getting issue details... STATUS |
Context Aggregator - OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| Deploy Context Aggregator in OOM | Verify that the Context Aggregator can be deployed in a Kubernetes environment | PASS |
LOG-422
-
Getting issue details...
STATUS
| |||
| Login to the Context Aggregator pod and ensure it is running | Verify that the Context Aggregator pod is reachable and Context Aggregator is running | PASS | LOG-422 - Getting issue details... STATUS | |||
| Delete the deployed Context Aggregator from OOM | Verify that the Context Aggregator pod can be deleted by using the standard OOM deletion instruction | PASS | LOG-422 - Getting issue details... STATUS |
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 | LOG-521 - Getting issue details... STATUS | ||
| success path | Verify that the AAI Context Builder service is able to process an incoming context request. | PASS | LOG-521 - Getting issue details... STATUS | |||
| 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 | LOG-521 - Getting issue details... STATUS | |||
| sonar report | Verify that the AAI Context Builder service Sonar report does not include any critical level issues that need to be resolved. | PASS | LOG-521 - Getting issue details... STATUS | |||
| 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 | LOG-521 - Getting issue details... STATUS |
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 |
LOG-425
-
Getting issue details...
STATUS
| |||
| 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 | LOG-425 - Getting issue details... STATUS | |||
| 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 | LOG-425 - Getting issue details... STATUS |
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 |
LOG-522
-
Getting issue details...
STATUS
| |||
| Send API request to SDC context builder | Verify that an API request can be sent to SDC context builder | PASS | LOG-522 - Getting issue details... STATUS | |||
| Send API request to SDC context builder with error in modelVersionId | Verify that an error occurs when the null value or missing modelVersionId | PASS | LOG-522 - Getting issue details... STATUS | |||
| Send API request to SDC context builder - missing AppId from the header | Verify that missing parameter returns proper error code in response | PASS | LOG-522 - Getting issue details... STATUS | |||
| Send API request to SDC context builder - missing basic auth from the header | Verify that missing parameter returns proper error code in response | PASS | LOG-522 - Getting issue details... STATUS | |||
| Check sonar report | Verify that no critical sonar issues | PASS | LOG-522 - Getting issue details... STATUS | |||
| Review wiki page | Verify that the ONAP developer wiki has been updated with information regarding the SDC Builder. | PASS | LOG-522 - Getting issue details... STATUS |
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 |
LOG-424
-
Getting issue details...
STATUS
| |||
| 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 | LOG-424 - Getting issue details... STATUS | |||
| 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 | LOG-424 - Getting issue details... STATUS |
Context Builder: Network Discovery
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
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 |
OOM-1320
-
Getting issue details...
STATUS
|
Service Decomposition
| 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 | LOG-397 - Getting issue details... STATUS | |||
| GET A&AI service instance details - missing parameter(AppId) | Verify that missing parameter returns proper error code in response | PASS | LOG-397 - Getting issue details... STATUS | |||
| GET A&AI service instance details - missing parameter(serviceInstanceId) | Verify that missing parameter returns empty json response | PASS | LOG-397 - Getting issue details... STATUS | |||
| GET A&AI service instance details - invalid parameter(serviceInstanceId) | Verify that missing parameter returns proper error code in response | PASS | LOG-397 - Getting issue details... STATUS | |||
| Malformed GET Request to fetch the data | Verify that malformed GET request returns proper error code in response | PASS | LOG-397 - Getting issue details... STATUS | |||
| service-decomposition | service includes VNFs | Verify that VNF resources that comprise a services can be returned by the service decomposition micro service. | PASS | LOG-397 - Getting issue details... STATUS | |||
| service-decomposition | service includes VNFCs | Verify that VNFC resources that comprise a services can be returned by the service decomposition micro service. | PASS | LOG-397 - Getting issue details... STATUS | |||
| service-decomposition | service includes VFModules | Verify that VFModule resources that comprise a services can be returned by the service decomposition micro service. | PASS | LOG-397 - Getting issue details... STATUS | |||
| service-decomposition | service includes VServers | Verify that VServer resources that comprise a services can be returned by the service decomposition micro service. | PASS | LOG-397 - Getting issue details... STATUS | |||
| 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 | LOG-397 - Getting issue details... STATUS | |||
| 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 | LOG-397 - Getting issue details... STATUS | |||
| 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 | LOG-397 - Getting issue details... STATUS | |||
| 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 | LOG-397 - Getting issue details... STATUS | |||
| 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 | LOG-397 - Getting issue details... STATUS | 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 | LOG-397 - Getting issue details... STATUS | X-ONAP-RequestID not returned in response to caller. Tracking this issue outside of story: LOG-237 - Getting issue details... STATUS | ||
| 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 | LOG-397 - Getting issue details... STATUS | 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 | LOG-397 - Getting issue details... STATUS | |||
| 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 | LOG-397 - Getting issue details... STATUS | |||
| service-decompoistion | swagger API documentation | Verify that the API documentation for the service decomposition micro service is available. | PASS | LOG-397 - Getting issue details... STATUS |
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 | LOG-427 - Getting issue details... STATUS | |||
| OOM | removal | Verify that the Validation Service can be undeployed from a POMBA environment. | PASS | LOG-427 - Getting issue details... STATUS | |||
| 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 | LOG-427 - Getting issue details... STATUS | |||
| 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 | LOG-427 - Getting issue details... STATUS | 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 | LOG-427 - Getting issue details... STATUS |
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 |
LOG-572
-
Getting issue details...
STATUS
| |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| data-router | orchestration-event-service | orchestration-event | success | multiple services | Verifythat the Data Router can successfully process an incoming request and produce | PASS | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS | |||
| 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 | LOG-572 - Getting issue details... STATUS |
POMBA Data Router - OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
| OOM | deployment | Verify that the Data Router can be deployed in a POMBA environment with all the appropriate configuration, etc. | PASS | LOG-572 - Getting issue details... STATUS | |||
| OOM | removal | Verify that the Data Router can be undeployed from a POMBA environment. | PASS | LOG-572 - Getting issue details... STATUS |
POMBA Search Data Service
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
| POA-AUDIT-REPORT event | Verify that the Search Data Service is able to accept POMBA messaging from the Data Router. | PASS | LOG-612 - Getting issue details... STATUS |
POMBA Search Data Service - OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
| oom | search-data-service | install | Verify that the Search Data Service can be deployed in a POMBA environment using OOM. | PASS |
LOG-612
-
Getting issue details...
STATUS
|