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 | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-519 |
|---|
|
|
|
| Consume audit event from “event bus” (message router) | Verify audit event is consumed by POMBA-CA and is processed successfully
| PASS | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-519 |
|---|
|
|
|
| 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 | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-519 |
|---|
|
|
|
| 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 | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-519 |
|---|
|
|
|
| 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 | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-519 |
|---|
|
|
|
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 | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-422 |
|---|
|
|
|
| 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 | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-422 |
|---|
|
|
|
| Delete the deployed Context Aggregator from OOM | Verify that the Context Aggregator pod can be deleted by using the standard OOM deletion instruction | PASS | |
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | LOG-422 |
|---|
|
|
|
Context Builder: SDC
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
...
