Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Context Builder: SDNC
OOM
Test Case | Description | Status | Owner | Date | JIRA link | Comment |
---|
oom deployment | Verify that the SDNC Context Builder is capable of being deployed through OOM. | PASS | |
|
LOG-426
-
Getting issue details...
STATUS
| |
oom deletion | Verify that the SDNC Context Builder is capable of being deleted form a POMBA deployment. | PASS | |
|
LOG-426
-
Getting issue details...
STATUS
|
|
SDNC Seed Code w/ Generic Resources API
Test Case | Description | Status | Owner | Date | JIRA link | Comment |
---|
context aggregator | builders | properties | sdnc.properties | Verify that the Context Aggregator config/builders/ directory contains an sdnc.properties file upon deployment so that the builder can be utilized in audits. | PASS | |
|
LOG-520
-
Getting issue details...
STATUS
| |
sdnccontextbuilder | service | context | basic auth | Verify that the SDNC Context Builder can successfully process an incoming context request using basic authentication. | PASS | |
|
LOG-520
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | service | context | basic auth | bad credentials | Verify that the SDNC Context Builder rejects requests that do not provide the correct credentials. | PASS | |
|
LOG-520
-
Getting issue details...
STATUS
|
|
context aggregator -> sdnc context builder | Verify that the Context Aggregator is capable of interoperating with the SDNC Context Builder. | PASS | |
|
LOG-520
-
Getting issue details...
STATUS
|
|
sdnc context builder -> sdnc | Verify that the SDNC Context Builder is capable of interoperating with an SDNC. | PASS | |
|
LOG-520
-
Getting issue details...
STATUS
|
|
POMBA APIv1
Test Case | Description | Status | Owner | Date | JIRA link | Comment |
---|
sdnccontextbuilder | v1 | service | context | Verify that the SDNC Context Builder context API can be called while explicitly referencing the version (v1). | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
| |
sdnccontextbuilder | service | context | Verify that when the API version for the SDNC Context Builder is not explicitly specified, the latest version (APIv1) will be invoked. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | vservers fields | Verify that the SDNC Context Builder can return the full list of required attributes associated with one or more vservers associated with a service instance. The attribute values should be obtained from the correct source attributes. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | l3-networks fields | Verify that the SDNC Context Builder can return the full list of required attributes associated with one or more l3-networks associated with a service instance. The attribute values should be obtained from the correct source attributes. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | serviceInstanceId missing | Verify that the SDNC Context Builder returns a 400 error when the required serviceInstanceID parameter is missing. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | X-TransactionId missing | Verify that the SDNC Context Builder is capable of processing a context request that omits the X-TransactionId header. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | X-FromAppId missing | Verify that the SDNC Context Builder reutrns a 400 error processing a context request that omits the X-FromAppId header. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | SDNC not available | Verify that the SDNC Context Builder returns a 500 error when the SDNC from which data is to be obtained is not available. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | v1 | service | context | service not found | Verify that the SDNC Context Builder returns a 404 error when the service instance for which context is requested cannot be located in the SDNC. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
sdnccontextbuilder | logging | success | Verify that the SDNC Context Builder provides sufficient logging when a context request is successfully processed. |
| |
|
LOG-462
-
Getting issue details...
STATUS
| Logging for the sdncctxbuilder will be tested on the next phase of the epic |
sdnccontextbuilder | logging | failure | bad request | Verify that the SDNC Context Builder provides sufficient logging when a context request is unsuccessfully processed due to a missing parameter. |
| |
|
LOG-462
-
Getting issue details...
STATUS
| Logging for the sdncctxbuilder will be tested on the next phase of the epic |
sdnccontextbuilder | v1 | swagger | Verify that the SDNC Context Builder provides swagger documentation for v1 of the Context Builder API. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
wiki | Verify that the wiki documentation provides a suitable description of the SDNC Context Builder APIv1. | PASS | |
|
LOG-462
-
Getting issue details...
STATUS
|
|
API Mapper w/ VNF API
Test Case | Description | Status | Owner | Date | JIRA link | Comment |
---|
default config | context request | service type | vFW | Verify that, using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vFW". |
| |
|
LOG-421
-
Getting issue details...
STATUS
| |
default config | context request | service type | vDNS | Verify that, using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vDNS". |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|
default config | context request | service type | non-vFW/vDNS | Verify that, using the default configuration, the GENERIC-RESOURCE-API is utilized when the SDNC Context Builder detects that the service instance isn't of the type vFW or vDNS. |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|
generic-resource-api | common model support | vserver | Verify that when the SDNC Context Builder utilizes the Generic Resource API to gather service data, the output is able to pass along all of the mandatory vserver attributes. |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|
generic-resource-api | common model support | l3-network | Verify that when the SDNC Context Builder utilizes the Generic Resource API to gather service data, the output is able to pass along all of the mandatory l3-network attributes. |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|
rules modification | Verify that the rules used to select which API should be used to gather service data can be changed. |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|
context request | aai unavailable | Verify that an error is returned when the SDNC Context Builder is unable to contact the AAI and cannot, therefore, determine ServiceType for rules mapping |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|
developer wiki | Verify that the developer wiki has been updated to include information about the API mapping feature in SDNC Context Builder, including how to modify the mapping rules |
| |
|
LOG-421
-
Getting issue details...
STATUS
|
|