Table of Contents maxLevel 2
...
| 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 | ||||||||||||||||
| 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-ID TransactionId value generated by the Data Router in the case where the original orchestration event did not include one. |
| ||||||||||||||||||||
| 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
...