...
| # | Sub Module | Test Cases | Status | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Deployment | Verify all DCAE services can be deployed via helm and passing healthcheck |
| |||||||||||
| 2 | Deployment | Verify all platform component (Cloudify) can be deployed and passing healthcheck |
| 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 |
| |||||||||||
| 4 | Event Flow | Verify data flow through VES Collector |
| Validated and recorded under pair-wise test - DCAE Pair Wise Testing for Istanbul Releasehttps://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/2021-03/10_06-03/xtesting-smoke-usecases-robot/ves-collector/ves-collector/report.html | ||||||||||
| 5 | Event Flow | Verify data flow into TCAgen2 and CL o/p |
| Validated and recorded under pair-wise test - DCAE Pair Wise Testing for Istanbul Release03102021-VES-TCA.txt | ||||||||||
| 6 | Interfaces | Verify SCH interface with Inventory (through Dashboard) | N/A |
| Validated and recorded Wll be validated under pair-wise test - DCAE Pair Wise Testing for Istanbul Release | |||||||||
DCAE MOD
No. | Test Scenario | Description | Status (Not Started, In-Progress, Pass, Fail) | Notes (Document results with Screenshots and/or logs) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | MOD Healthcheck | Verify all MOD components healthcheck and external API |
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)
| https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/2021-10/10_04-19/xtesting-smoke-usecases-robot/dcaemod/dcaemod/report.html Jira | server | ONAP JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | DCAEGEN2-2673 | ||||||||
| 2 | Onboard dataformat | Use onboardingAPI to add new data-formats for VESCollector & TCA-gen2 DCAE mS and verify if its shown up in the catalog |
| see above | ||||||||||||||||
| 3 | Onboard component spec | Use onboardingAPI to add new spec file for VESCollector & Tca-gen2 DCAE mS and verify if its shown up in the catalog |
| see above | ||||||||||||||||
| 4 | Create flow | Create flow on DesignUI for VESCollector and TCAgen2 and set connection |
| see above | ||||||||||||||||
| 5 | Add distribution target | Set the configuration for distributorAPI to point to DCAE runtimeAPI |
| see above | ||||||||||||||||
| 6 | Distribution | Verify if the blueprint are generated and loaded into DCAE InventoryAPI |
| see above | ||||||||||||||||
| 7 | Deployment | Perform deployment via Dashboard/Deployment-handler API to deploy using latest blueprint pushed. |
|
| ||||||||||||||||
| Jira | ||||||||||||||||||||
| server | ONAP JIRA | |||||||||||||||||||
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | |||||||||||||||||||
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | DCAEGEN2-2672||||||||||||||||||