Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DCAE R9 test updates

...

https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/2021-03/10_06-03/xtesting-smoke-usecases-robot/ves-collector/ves-collector/report.html03102021-VES-TCA.txt
#Sub ModuleTest CasesStatusNotes 
1DeploymentVerify all DCAE services can be deployed via helm and passing healthcheck

Status
colourGreen
titlePASS


2

Deployment

Verify all platform component (Cloudify) can be deployed and passing healthcheck

Status
colourGreyGreen
titleNOT DONEPASS

https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/2021-03/10_06-03/xtesting-healthcheck/full/full/log.html#s1-t8
3

Deployment

Verify all static components identified for the release (ves, tcagen2,prh, hv-ves) are deployed and passing healthcheck

Status
colourGreyGreen
titleNOT DONEPASS


4Event FlowVerify data flow through VES Collector

Status
colourGreyGreen
titleNOT DONE

PASS

Validated and recorded under pair-wise test - DCAE Pair Wise Testing for Istanbul Release
5Event FlowVerify data flow into TCAgen2 and CL o/p

Status
colourGreyGreen
titleNOT DONE

PASS

Validated and recorded under pair-wise test - DCAE Pair Wise Testing for Istanbul Release
6InterfacesVerify SCH interface with Inventory (through Dashboard)

N/A

Wll be validated

Status
colourGrey
titleNOT DONE

Validated and recorded under pair-wise test - DCAE Pair Wise Testing for Istanbul Release






DCAE MOD

DCAEGEN2-2673

No.

Test Scenario


Description

Status

(Not Started, In-Progress, Pass, Fail)

Notes

(Document results with Screenshots and/or logs)

1MOD Healthcheck

Verify all MOD components healthcheck and external API

Status
colourGreyGreen
titleNOT DONE

All components report as ready via kubernetes. There is no healthcheck during gating. Healthcheck pod reports all components as unavailable (probably due to old base image for older versions of K8s)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key
PASS

2Onboard dataformatUse onboardingAPI to add new data-formats for VESCollector & TCA-gen2 DCAE mS and verify if its shown up in the catalog

Status
colourGreyGreen
titleNOT DONEPASS

see above3Onboard component specUse onboardingAPI to add new spec file for VESCollector & Tca-gen2 DCAE mS and verify if its shown up in the catalog

Status
colourGreyGreen
titleNOT DONEPASS

see above4Create flowCreate flow on DesignUI for VESCollector and TCAgen2 and set connection

Status
colourGreyGreen
titlePASSNOT DONE

see above5Add distribution targetSet the configuration for distributorAPI to point to DCAE runtimeAPI

Status
colourGreyGreen
titlePASSNOT DONE

see above6DistributionVerify if the blueprint are generated and loaded into DCAE InventoryAPI

Status
colourGreyGreen
titlePASSNOT DONE

see above7DeploymentPerform deployment via Dashboard/Deployment-handler API  to deploy using latest blueprint pushed. Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyDCAEGEN2-2672

Status
colourGreyGreen
titleNOT DONE
tca-

tca-gen2 component spec has issue with incorrectly set input type and because of that inputs didn't show up when deploying via dashboard

PASS
tca-