# | Scenario | Covers | Steps | Status |
---|
CPS(cps-core and ncmp)
|
1.1 | Health Check | cps-core | - Test Liveness Probe Endpoint
- Test Readiness Probe Endpoint
| Done |
1.2 | CPS Admin Details Insert | cps-core | - Create Dataspace
- Create schema set from YANG file
- Create Schema set with Zip file
- Get schema set info
- Create anchor
- Get Anchor
| To Be Updated Get Anchor test to be included in the existing test. |
1.3 | CPS Data Node Insert, Update and Delete | cps-core | - Create Data Node for an anchor
- Get Datanode by the dataspace, anchor and xpath
| Done |
CPS Temporal |
2.1 | Health Check | cps-temporal | - Test Liveness Probe Endpoint
- Test Readiness Probe Endpoint
| New
|
2.2 | Get anchor history | cps-core, cps-temporal (through Kafka) | - Create Dataspace
- Create schema set
- Create anchor
- Create Data Node using cps api
- Update the Data Node using cps api
Get the history of the anchor using cps-temporal api /v1/dataspaces/{dataspace-name}/anchors/{anchor-name}/history
|
|
ONAP DMI PLUGIN |
3.1 | Health Check | dmi-plugin | - Test Liveness Probe Endpoint
- Test Readiness Probe Endpoint
| New Jira Legacy |
---|
server | System ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
---|
key | CPS-615 |
---|
|
|
3.2 | Register and Model-Sync | dmi-plugin, ncmp, cps-core | - Create Data Node using cps api
- Notify NCMP DMI has new node http://localhost:8783/DMI notifies NCMP for a new cmhandle using api /dmi/api/v1/inventory/cmHandles
- This will kick off model sync as part of registation
- wait till above method call completes and send a 2xx response
- Use CPS endpoint that shows anchors & namespaces to conclude test completed
- Get anchor by using cm-handle name as the anchor name
- Get schema set information for the retrieved schemaset in step #2
| New Jira Legacy |
---|
server | System ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
---|
key | CPS-615 |
---|
|
|
3.3 | Write & and read data using datastore PassTroughPassThrough running/operational | dmi-plugin, ncmp, cps-core | - Call create operation for passthrough-running datastore /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running/{resourceIdentifier}
- Verify the resource is being created by GET api /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running/{resourceIdentifier}
- Call read operation for passthrough-operational datastore /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-operational/{resourceIdentifier}
| New Jira Legacy |
---|
server | System ONAP Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
---|
key | CPS-646 |
---|
|
|