Versions Compared

Old Version 4

changes.mady.by.user Aditya Puthuparambil

Saved on

compared with

New Version Current

changes.mady.by.user Levente Csanyi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

The integration testing is implemented as CSIT Jenkins jobs as described in Project-specific CSIT structure

On CSIT job execution

  • the docker image of the component to be tested is built 
  • the tests are executed using Robot Framework 
  • the test results are published as Jenkins job results

...

#CSIT componentImageDecision
1cps-corecps-and-ncmplatest
2. cps-temporalcps-temporallatest
cps-and-ncmpmost recent stage released stable version 
3(onap) dmi-plugin
ncmp-dmi-plugin
latest
cps-and-ncmpmost recent stage released stable version 
sdnc and netconf-simulatormost recent stage released stable version

Jenkins Jobs

Following jobs are serving CSIT for CPS projectProjects

...

Test Plan

#

ScenarioCoversSteps Test Status
#JakartaKohn London
CPS(cps-core and ncmp)

1.1Health Checkcps-core
  1. Test Liveness Probe Endpoint
  2. Test Readiness Probe Endpoint
DoneDoneDone
1.2
CPS Admin Details Insert
cps-core, postgres
  1. Create Dataspace 
  2. Create schema set from YANG file
  3. Create Schema set with Zip file
  4. Get schema set info
  5. Create anchor
  6. Get Anchor

To Be Updated

Get Anchor test to be included in the existing test.

DoneDone
1.3CPS Data Node Insert, Update and Deletecps-core, postgres
  1. Create Data Node for an anchor
  2. Get Datanode by the dataspace, anchor and xpath

Done

DoneDone
CPS Temporal
2.1Health Checkcps-temporal
  1. Test Liveness Probe Endpoint
  2. Test Readiness Probe Endpoint

New


DoneWon't Do
2.2Get anchor historycps-core, postgres, kafka, cps-temporal
(through Kafka)
, timescaledb
  1. Create Dataspace 
  2. Create schema set 
  3. Create anchor
  4. Create Data Node using cps api 
  5. Update the Data Node using cps api

  6. Get the history of the anchor using cps-temporal api

    1. /v1/dataspaces/{dataspace-name}/anchors/{anchor-name}/history



DoneWon't Do
ONAP DMI PLUGIN
3.1Health Checkdmi-plugin
  1. Test Liveness Probe Endpoint
  2. Test Readiness Probe Endpoint

New

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-615
Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-930

DoneDone
3.2

Register and Model-Sync

dmi-plugin,
ncmp,
NCMP  cps-core
  • Create Data Node using cps api 
    • Notify NCMP DMI has new node http://localhost:8783/Use CPS endpoint that shows anchors & namespaces to conclude test completed
    , postgres, sdnc (mariadb), netconf simulator
    1. 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
    1. Get anchor by using cm-handle name as the anchor name
    2. Get schema set information for the retrieved schemaset in step #2

    New

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-615

    		DoneDone
    3.3Write
    &
    and read data using datastore
    PassTrough
    PassThrough running/operationaldmi-plugin,
    ncmp
    NCMP, cps-core, postgres, , sdnc (mariadb), netconf simulator
    1. Call create operation for passthrough-running datastore /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running/{resourceIdentifier} 
    2. Verify the resource is being created by GET api  /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running/{resourceIdentifier}
    3. Call read operation for passthrough-operational datastore /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-operational/{resourceIdentifier} 

    New

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-646

    		DoneDone
    3.4Get all modules for given cm handledmi-plugin, sdnc (mariadb)
    1. Get all modules related to a given cm-handle and response should be 200 OK.
      POST: /dmi/v1/ch/{cm-handle}/modules

    Jira Legacy
    serverSystem Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-930

    		DoneDone
    3.5Data sync (and sync state)


    		DoneDone