Versions Compared

Key

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

...

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy Context Aggregator in OOMVerify that the Context Aggregator can be deployed in a Kubernetes environmentPASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-422


Login to the Context Aggregator pod and ensure it is runningVerify that the Context Aggregator pod is reachable and Context Aggregator is runningPASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-422

Delete the deployed Context Aggregator from OOMVerify that the Context Aggregator pod can be deleted by using the standard OOM deletion instructionPASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-422



Context Aggregator - Latest POMBA API

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Ensure only 3 parameters are sent to the context builderVerify all of the underlying context builders receive a ‘Get context” request from POMBA-CA with the following 3 parameters: ServiceInstanceIdmodelVersionId, and modelInvariantId

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-439


Ensure the response from the Network Discovery Context Builder align with Common Model v.1Verify the response from Network Discovery Context Builder is using Common Model v.1

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-439


Retrieve model data for Network Discovery context builder
  • Verify POMBA-CA is able to retrieve model data from Network Discovery context builder
  • Verify the Network Discovery context builder receives a ‘Get context” request from POMBA-CA
  • Verify a response is received at POMBA-CA from Network Discovery context builder


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-439



Context Builder: AAI

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy MSVerify AAI Context Builder MS starts up without errorPASSDavid Stangl

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-521


success pathVerify that the AAI Context Builder service is able to process an incoming context request.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-521


bad credentialsVerify 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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-521


sonar reportVerify that the AAI Context Builder service Sonar report does not include any critical level issues that need to be resolved.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-521


wiki updateVerify that the ONAP developer wiki has been updated to include pertinent information for the development and usage of the AAI Context Builder.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-521


...

Test CaseDescriptionStatusOwnerDateJIRA linkComment
oom | install | network discovery context builderVerify that the Network Discovery Context Builder can be deployed using OOM.PASSDavid Stangl



Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOOM-1320



Service Decomposition


Test CaseDescriptionStatusOwnerDateJIRA linkComment
GET A&AI service instance details - success scenarioVerify that A&AI data is populated  correctlyPASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397


GET A&AI service instance details - missing parameter(AppId)Verify that missing parameter returns proper error code in responsePASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397


GET A&AI service instance details - missing parameter(serviceInstanceId)Verify that missing parameter returns empty json responsePASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

GET A&AI service instance details - invalid parameter(serviceInstanceId)Verify that missing parameter returns proper error code in responsePASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

Malformed GET Request to fetch the dataVerify that malformed GET request returns proper error code in responsePASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | service includes VNFsVerify that VNF resources that comprise a services can be returned by the service decomposition micro service.PASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | service includes VNFCsVerify that VNFC resources that comprise a services can be returned by the service decomposition micro service.PASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | service includes VFModulesVerify that VFModule resources that comprise a services can be returned by the service decomposition micro service.PASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | service includes VServersVerify that VServer resources that comprise a services can be returned by the service decomposition micro service.PASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | service includes L3 networkVerify that L3 network resources that comprise a services can be returned by the service decomposition micro service.PASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

GET Generic VNF output for supported resources with different combinations of the dataVerify that all supported resource types should be populated in correct hierarchyPASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | interrelated resources don't result in redundancy or unrelated service resourcesVerify 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
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | service not foundVerify that the service decomposition micro service returns an error code and message when the service that is requested cannot be located.PASS
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | X-ONAP-RequestID not specifiedVerify that the service decomposition micro service generates a unique transaction ID when one had not been specified in the request.FAIL

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

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 specifiedVerify that the service decomposition micro service response uses the same unique transaction ID as was specified in the request.FAIL

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

X-ONAP-RequestID not returned in response to caller.

Tracking this issue outside of story:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-237

service-decomposition | X-ONAP-PartnerNameVerify that the service decomposition micro service response uses the same unique ONAP partner name as was specified in the request.FAIL

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

X-ONAP-PartnerNAme not returned in response to caller.

Tracking this issue outside of story.

service-decomposition | A&AI connection severedVerify 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
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397

service-decomposition | mini-soakVerify 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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397


service-decompoistion | swagger API documentationVerify that the API documentation for the service decomposition micro service is available.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-397




POMBA Validation Service

Test CaseDescriptionStatusOwnerDateJIRA linkComment
OOM | deploymentVerify that the Validation Service can be deployed in a POMBA environment with all the appropriate configuration, etc.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-427


OOM | removalVerify that the Validation Service can be undeployed from a POMBA environment.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-427


pomba-validation-service | RULES-VALIDATION | successVerify 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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-427


pomba-validation-service | topic creation | POA-AUDIT-RESULTVerify 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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-427

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 reportVerify that the Validation Service Sonar report does not include any critical level issues that need to be resolved.PASS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyLOG-427


...