| S No | Scenario | Steps |
|---|
CPS
|
| 1.1 | CPS Admin Details Insert | - Create Dataspace
- Create Schema set with Zip file
- Get schema set
- Create anchor for the created schema-set and dataspace
- Get Anchor
|
| 1.2 | CPS Data Node Insert, Update and Delete | 1. Create Data Node
2. Get Data Node
2. Update Data Node
3. Delete Data Node
4. Get Data Node |
| CPS Temporal |
| 2.1 | Create an anchor history | - 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
|
| 2.2 | Delete the data node to add it to history | - Create Data Node using cps api
- Update the Data Node using cps api
- Delete the data node using cps-api
- Get the history of the anchor using cps-temporal api
/v1/dataspaces/{dataspace-name}/anchors/{anchor-name}/history
|
| CPS-NCMP-DMI_PLUGIN |
| 3.1 | Model-Sync, Write & read data using datastore PassTrough | Add (simulator) 'node' using 'internal' rest end point on ONAP DMI PluginWait till model sync is complete, call is synchronous at the moment so we should just - Create Data Node using cps api
- Notify NCMP DMI has new node
- http://localhost:8783/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
(demo only) - Show data in Postgres: anchor and module-set
- Use CPS endpoint that shows anchors & namespaces to conclude test completed
- <ENDPOINT TO BE CONFIRMED>
|
|
|
|
