Page Comparison

...

The test structure here has been adapted from Policy Team's CSIT Functional Test Cases created by Pamela Dragosh

...

Id	Description	Pre-conditions	Test Steps	Expected Results
A: Health Checks for OOF-OSDF Components and Dependencies (Policy and OOF-HAS API)
A.1	Perform health check for the OOF-OSDF components using Health Check API OSDF Manager	[OSDF Manager] EMULATORS-OR-SERVICES-ARE-UP Server and authentication details should be configured at $OOF_HOME/config/feature-healthcheck.properties	SIMPLE-GET-HEALTH-CHECK-API	HTTP-200-TRUE
A.2	CHECK-REQ-OR-OPTIONAL Perform health check for the following external components and OOF components using Health Check API: ~~Policy (external component)~~ ~~OOF-HAS API (OOF component)~~	[Policy Emulator] [OOF-HAS API – container or emulator] EMULATORS-OR-SERVICES-ARE-UP	~~SIMPLE-GET-HEALTH-CHECK-API~~	~~HTTP-200-TRUE~~ NOTE: Per comment and discussion with Ramki, removing this cell TODO: Retain this cell till 19 Feb 2018 and then remove it.
B: Fetch Data from Emulators (valid and invalid data, via GET and POST)
B.1	Retrieve response corresponding to "valid request" from HAS-API emulator OSDF → HAS (POST data)	[OOF-HAS API – container or emulator]EMULATORS-OR-SERVICES-ARE-UP	SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES TODO: Payload for OSDF-HAS request (based on SO-OOF/HAS Request Example below in section on payloads; dr_patel_an to add the payload; Shankaranarayanan Puzhavakath Narayanan to review) TODO: Endpoint and ports	Should receive a "request accepted" type response, following which we query status and the status should be a valid one (translating, translated, solving, solved, solution not found, etc.)
B.2	Retrieve response corresponding to "valid policy query" from Policy emulator OSDF → Policy (POST query data)	[Policy] EMULATORS-OR-SERVICES-ARE-UP	SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES TODO: Payloads and Endpoint	Should receive response for valid policy query TODO: Payloads
B.3	CHECK-REQ-OR-OPTIONAL ~~OSDF → Policy (bad result)~~ ~~OSDF → HAS (GET; bad status)~~ Moved to another cell ~~OSDF → HAS (GET; solution found)~~	[Policy Emulator] [OOF-HAS API – container or emulator] EMULATORS-OR-SERVICES-ARE-UP	~~SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES~~ ~~TODO: Payloads and Endpoint~~	~~Should receive corresponding responses~~ ~~TODO: Payloads~~ NOTE: Per comment and discussion with Ramki, removed tests for "malformed" requests (open to adding them later on as needed). Moved the remaining one to a separate cell. TODO: Retain this cell till 19 Feb 2018 and then remove it.
B.4	Retrieve response corresponding to a decision from Conductor (i.e. "done" with either a solution found or no solution found): OSDF → HAS (GET; solution found OR no solution found). Since we cannot guarantee whether a solution can be found (it is dependendent on dynamic state of the cloud instance), it may be better to merge it to a "solution found OR no solution found" – i.e. Conductor is done processing and gave a decision	[Policy Emulator] [OOF-HAS API – container or emulator] EMULATORS-OR-SERVICES-ARE-UP	SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES TODO: Payloads and Endpoint	TODO: Check format of response and valid status messages
C: Run Complete Requests for Different Applications
C.1	SO → OSDF → HAS (well formatted request)	[Policy Emulator] [OOF-HAS API – container or emulator] EMULATORS-OR-SERVICES-ARE-UP	SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES TODO: Payloads, Endpoint, and Call-Back URL	Should receive a valid Conductor reponse TODO: Payloads
C.2	CHECK-REQ-OR-OPTIONAL SO → OSDF → HAS (mal-formatted request or a data error so that the request goes through OSDF but fails at Conductor)	[Policy Emulator] [OOF-HAS API – container or emulator] EMULATORS-OR-SERVICES-ARE-UP	~~SIMPLE-GET-POST-TO-EMULATORS-OR-SERVICES~~ ~~TODO: Payloads, Endpoint, and Call-Back URL~~	~~Should receive a RequestError or an error from Conductor~~ ~~TODO: Payloads~~ NOTE: Per comment and discussion with Ramki, removing this cell TODO: Retain this cell till 19 Feb 2018 and then remove it.

Example Request/Response Payloads for OOF-OSDF Functional Test Cases

...

language	js
theme	Eclipse
title	SO-OOF/HAS Request Example
linenumbers	true
collapse	true

...

C.3

SO → OSDF → HAS → OSDF → Call Back URL

A valid request sent from SO to OSDF, which results in a valid template sent from OSDF to HAS. OSDF will then poll HAS till a decision is made (i.e. "done" with either a solution found or no solution found; it is probably difficult to ensure a solution is guaranteed – it is great if a solution is found, and it is OK for testing purposes even if there if no solution in some cases)

[Policy Emulator]
[OOF-HAS API – container or emulator] [SO-OOF-OSDF call-back receiver]

EMULATORS-OR-SERVICES-ARE-UP

[Policy Emulator]
[OOF-HAS API – container or emulator] EMULATORS-OR-SERVICES-ARE-UP

Should receive a "done" type Conductor reponse (either successful in finding a solution or failed to find a solution, but Conductor made a decision either way)

TODO: Payloads

Example Request/Response Payloads for OOF-OSDF Functional Test Cases

Code Block

language	js
theme	Eclipse
title	SO-OOF/HAS Request Example
linenumbers	true
collapse	true

{
  "requestInfo": {
    "transactionId": "xxx-xxx-xxxx",
    "optimizersrequestId": ["placementyyy-yyy-yyyy"],
    "timeoutcallbackUrl": 600"https://so:5000/callbackUrl",
  },
  "requestParameterssourceId": { "customerLatitudeSO": 32.89748, "customerLongitude": -97.040443, "customerName,
    "requestType": "xyzcreate",
},    "placementDemandsnumSolutions": [1,
    {
"optimizers": ["placement"],
     "resourceModuleNametimeout": "vGMuxInfra",600
   },
  "serviceResourceIdrequestParameters": { "vGMuxInfra-xx"customerLatitude": 32.89748,       "tenantId"customerLongitude": -97.040443, "customerName": "vGMuxInfra-tenantxyz" },
  "placementDemands": [
   "resourceModelInfo": {
 
      "modelInvariantIdresourceModuleName": "vGMuxInfra-modelInvariantId",
        "modelVersionIdserviceResourceId": "vGMuxInfra-versionIdxx",
 
      "modelNametenantId": "vGMuxInfra-modeltenant",
 
      "modelTyperesourceModelInfo": "resource",{
        "modelVersionmodelInvariantId": "1.0vGMuxInfra-modelInvariantId",
        "modelCustomizationNamemodelVersionId": "vGMuxInfra-customeModelNameversionId",
      },  "modelName": "vGMuxInfra-model",
        "existingCandidatesmodelType": { "resource",
        "identifierTypemodelVersion": "service_instance_id1.0",
"identifiers        "modelCustomizationName": ["87257b49-9602-4ca1-9817-094e52bc873b"]vGMuxInfra-customeModelName"
      },
      "excludedCandidatesexistingCandidates": { "identifierType": "service_instance_id", "identifiers": ["87257b49-9602-4ca1-9817-094e52bc873b"] },
      "excludedCandidates": { "identifierType": "service_instance_id", "identifiers": ["1ac71fb8-ad43-4e16-9459-c3f372b8236d"] },
      "requiredCandidates": { "identifierType": "service_instance_id", "identifiers": ["7e6c3e57-62cd-44f6-aa88-d0896998f7ec"] }
    },
    {
      "resourceModuleName": "vG",
      "serviceResourceId": "71d563e8-e714-4393-8f99-cc480144a05e",
      "tenantId": "vG-tenant",
      "resourceModelInfo": {
        "modelInvariantId": "vG-modelInvariantId",
        "modelVersionId": "vG-versionId",
        "modelName": "vG-model",
        "modelType": "resource",
        "modelVersion": "1.0",
        "modelCustomizationName": "vG-customeModelName"
      },
      "existingCandidates": { "identifierType": "service_instance_id", "identifiers": ["21d5f3e8-e714-4383-8f99-cc480144505a"] },
      "excludedCandidates": { "identifierType": "service_instance_id", "identifiers": ["1ac71fb8-ad43-4e16-9459-c3f372b8236d"] },
      "requiredCandidates": { "identifierType": "cloud_region_id", "identifiers": ["TXAUS219"] }
    }
  ],
  "serviceInfo": {
    "serviceInstanceId": "d61b2543-5914-4b8f-8e81-81e38575b8ec",
    "serviceModelInfo": {
      "modelInvariantId": "vCPE-invariantId",
      "modelVersionId": "vCPE-versionId",
      "modelName": "vCPE-model",
      "modelType": "service",
      "modelVersion": "1.0",
      "modelCustomizationName": "vCPE-customeModelName"
    }
  },
  "licenseDemands": [
    {
      "resourceModuleName": "vGMuxInfra",
      "serviceResourceId": "vGMuxInfra-xx",
      "tenantId": "vGMuxInfra-tenant",
      "resourceModelInfo": {
        "modelInvariantId": "vGMuxInfra-modelInvariantId",
        "modelVersionId": "vGMuxInfra-versionId",
        "modelName": "vGMuxInfra-model",
        "modelType": "resource",
        "modelVersion": "1.0",
        "modelCustomizationName": "vGMuxInfra-customeModelName"
      },
      "existingLicenses": {
        "entitlementPoolUUID": ["87257b49-9602-4ca1-9817-094e52bc873b", "43257b49-9602-4fe5-9337-094e52bc9435"],
        "licenseKeyGroupUUID": ["87257b49-9602-4ca1-9817-094e52bc873b", "43257b49-9602-4fe5-9337-094e52bc9435"]
      }
    }
  ]
}

...

All Functional Test Cases described here below will be automatized in the CSIT ONAP integration environment. OOF-HAS is a data driven component, this means that test cases and related results have dependency on A&AI network database content. For this reason OOF-HAS Functional Test cases divided in 2 groups according to OOF-HAS functionality definition status and dependency from A&AI: Test cases marked in Green are those that will be delivered as first set of Functional Test cases as they have limited dependencies on A&AI data set, those marked in white will be scoped by ONAP Beijing delivery final test steps where all components have better stability in the scope of Beijing release.

Note: for the moment we consider the whole OOF component as the contribution of 2 Docker Containers:

- OSDF : handling “R” interface, which is invoked by SO

- OOF-HAS: handling the internal “R’” interface, which in invoked by OSDF

...

Id

...

Description

...

Pre-conditions

...

Test Steps

...

Expected Results

...

N.1

...

Note: for the moment we consider the whole OOF component as the contribution of 2 Docker Containers:

- OSDF : handling “R” interface, which is invoked by SO

- OOF-HAS: handling the internal “R’” interface, which in invoked by OSDF

Id	Description	Pre-conditions	Test Steps	Expected Results	Status

N.1	Name: Verify docker Containers are up and running	1. MUSIC (real ONAP) docker image is up and running 2. OOF-HAS docker image is up and running	Robot Framework is checking with "docker ps" command that all needed docker containers are up and in execution	N. 4 Docker Containers for music are Up and running (music-db, music-zk, music-war, music-tomcat) N.5 Docker Containers for OPTF-HAS are up and running (cond-api, cond.solv, cond-cont, cond-data, cond-resv)	Implemented
N.2	Name: OOF-HAS Get root Interface (R’). Perform GET on root "/" url	1. OOF-HAS docker image is up and running	Robot Framework is sending a REST call to OOF-HAS API – "/" Method - GET Endpoint: http://$(hostname ):8091/	OOF-HAS should respond with HTTP 200 and body containing "true"	Implemented
N.3	Name: OOF-HAS Healthcheck Interface (R’). Perform healthcheck for OOF-HAS using Healthcheck REST API	1. OOF-HAS docker image is up and running 2. OOF-HAS configuration is performed 3. MUSIC (real ONAP) docker image is up and running 4. Music is prepopulated with Healthcheck row	Robot Framework is sending a Rest Call to MUSIC to Inject a Plan named "healthcheck" Method - PUT Endpoint: /MUSIC/rest/v2/keyspaces/conductor/tables/plans/rows?id=healthcheck	MUSIC should respond with HTTP 200	Implemented
N.3			Robot Framework is sending a REST call to OOF-HAS API – healthcheck Method - GET Endpoint: http://$(hostname ):8091/v1/plans/healthcheck	OOF-HAS should respond with HTTP 200 and body containing "true"	Implemented
N.4	Name: OOF-HAS Wrong Version Interface (R’). Perform

healthcheck for OOF-HAS using Healthcheck REST API

sanity sending a plan with wrong Version

1. OOF-HAS docker image is up and running

2. OOF-HAS configuration is performed

3. MUSIC (real ONAP) docker image is up and running

4. Music is prepopulated with Healthcheck

row

Robot Framework is sending a REST call to OOF-HAS API – to Post a Plan

Method - POST

Endpoint: http://$(hostname ):8091/v1/plans

OOF-HAS should respond with HTTP 201 and body containing the plan acceptance (i.e. the plan is in “template” status and a unique identifier <planid> is returned)

Implemented

Robot Framework is sending a REST call to OOF-HAS

API –

healthcheck

to GET a final recommendations

Method - GET

Endpoint: http://$(hostname ):8091/v1/plans/

healthcheck

OOF-HAS should respond with HTTP 200 and body containing "

true

the error reason"	Implemented
N.

2

5	Name: OOF-HAS

Wrong Version

Missing Demand Section

Interface (R’).

Perform

sanity

Sanity sending a plan with

wrong Version

missing Demand Section

1. OOF-HAS docker image is up and running

2. OOF-HAS configuration is performed

3. MUSIC (real ONAP) docker image is up and running

4. Music is prepopulated with Healthcheck row

Robot Framework is sending a REST call to OOF-HAS

API – to Post a Plan

Method - POST

Endpoint: http://$(hostname ):8091/v1/

plansOOF-HAS should respond with HTTP 200 and body containing "the error reason"N.3

Name: OOF-HAS Missing Demand Section

Interface (R’).

Perform Sanity sending a plan with missing Demand Section

1. OOF-HAS docker image is up and running

2. OOF-HAS configuration is performed

3. MUSIC (real ONAP) docker image is up and running

4. Music is prepopulated with Healthcheck row

plans

OOF-HAS should respond with HTTP 201 and body containing the plan acceptance (i.e. the plan is in “template” status and a unique identifier <planid> is returned)

Implemented

Robot Framework is sending a REST call to OOF-HAS

API – to

Post

GET a

Plan

final recommendations

Method -

POST

GET

Endpoint: http://$(hostname ):8091/v1/plans/<planId>

OOF-HAS should respond with HTTP 200 and body containing "the error reason"

Implemented

N.

4

6

Name: OOF-HAS Wrong Constraint

Interface (R’).

Perform sanity sending a plan with wrong Constraints

1. OOF-HAS docker image is up and running

2. OOF-HAS configuration is performed

3. MUSIC (real ONAP) docker image is up and running

4. A&AI simulator docker image is up and running and it is populated in such a way that

OOF cache can be built

Robot Framework is sending a REST call to OOF-HAS API – to Post a Plan

Method - POST

Endpoint: http://$(hostname ):8091/v1/plans

OOF-HAS should respond with HTTP 201 and body containing the plan acceptance (i.e. the plan is in “template” status and a unique identifier <planid> is returned)

Implemented

Robot Framework is sending a REST call to OOF-HAS

API – to

Post

GET a

Plan

final recommendations

Method -

POST

GET

Endpoint: http://$(hostname ):8091/v1/plans/<planId>

OOF-HAS should respond with HTTP 200 and body containing "the error reason"

Implemented

N.

5

7	Name: OOF-HAS Correct plan no result Interface (R’). Send a correct plan requiring

vCPE

Optimization request for a set of Candidates and constraints that cannot be satisfied

1. OOF-HAS docker image is up and running

2. OOF-HAS configuration is performed

3. MUSIC (real ONAP) docker image is up and running

4. A&AI simulator docker image is up and running and it is populated in such a way that OOF cache can be built and that a set of recommendations can be returned

Robot Framework is sending a REST call to OOF-HAS

API – to Post a Plan

Method - POST

Endpoint: http://$(hostname ):8091/v1/plans

OOF-HAS should respond with HTTP

200

201 and body containing the plan acceptance (i.e. the plan is in “template” status and a unique identifier <planid> is returned)	Implemented
Robot Framework is sending a REST call to OOF-HAS

API – to GET a final recommendations

Method - GET

Endpoint: http://$(hostname ):8091/v1/plans/<planId>

OOF-HAS should respond with HTTP 200 and body containing NO recommendations (i.e. the plan is in

“done”

“not found” status and no resources are returned back)	Implemented
N.

6

8	Name: Correct Plan with recommendations Interface (R’). Send a plan requiring

vCPE

Optimization request for a set of Candidates

1. OOF-HAS docker image is up and running

2. OOF-HAS configuration is performed

3. MUSIC (real ONAP) docker image is up and running

4. A&AI simulator docker image is up and running and it is populated in such a way that OOF cache can be built and that a set of recommendations can be returned

Robot Framework is sending a REST call to OOF-HAS

API – to Post a Plan

Method - POST

Endpoint: http://$(hostname ):8091/v1/plans

OOF-HAS should respond with HTTP

200

201 and body containing the plan acceptance (i.e. the plan is in “template” status and a unique identifier <planid> is returned)	Implemented
Robot Framework is sending a REST call to OOF-HAS

API – to GET a final recommendations

Method - GET

Endpoint: http://$(hostname ):8091/v1/plans/<planId>

OOF-HAS should respond with HTTP 200 and body containing the plan recommendations (i.e. the plan is in “done” status and a set of

optimized vCPEs is

recommendations are returned to the caller )	Implemented

Appendix A: Overview of ONAP Testing Requirements

...

Notes on creating a CSIT test script: https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Creating+a+CSIT+Test
Policy Team's CSIT Functional Test Cases by Pamela Dragosh. The OOF-OSDF test cases are adapted from that page.
Slides on Platform Maturity Requirements for Beijing Release: https://wiki.onap.org/download/attachments/16002054/Platform%20Maturity%20Level%20proposal%2013Dec2017v2.pdf?version=1&modificationDate=1513625784000&api=v2
Current Individual Project Commitment for supporting Platform Maturity Requirements for Beijing Release:
https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Beijing+Release+Platform+Maturity
ONAP 4 level CI/CD architecture: Integration (5/11/2017)

...

Versions Compared

Old Version 32

New Version Current

Key

Example Request/Response Payloads for OOF-OSDF Functional Test Cases

Example Request/Response Payloads for OOF-OSDF Functional Test Cases

Appendix A: Overview of ONAP Testing Requirements