...
| # | 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 0: Integration Weather Board for Jakarta Release | ||||||||||
| 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 Release | 6 | Interfaces | Verify SCH interface with Inventory (through Dashboard) | |||||||
| Status | ||||||||||||||
| colour | Grey | title | NOT
| Validated and recorded 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 |
| |||||||
| 2 | Onboard dataformat | Use onboardingAPI to add new data-formats for DCAE mS and verify if its shown up in the catalog |
| https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/20212022-1004/1013_0402-1939/xtesting-smoke-usecases-robot/dcaemod/dcaemod/report.html | ||||||
| 2 | Onboard dataformat | Use onboardingAPI to add new data-formats for DCAE mS and verify if its shown up in the catalog |
| see above | ||||||
| html#suites?s1 | ||||||||||
| 3 | Onboard component spec | Use onboardingAPI to add new spec file for DCAE mS and verify if its shown up in the catalog |
| see above | ||||||
| 4 | Create flow | Create flow on DesignUI 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 Helm charts are generated and loaded into DCAE InventoryAPIChartmuseum registry |
| see above | ||||||
| 7 | Deployment | Perform deployment via Dashboard/Deployment-handler API to deploy using latest blueprint pushed.Helm for generated charts and verify container comes up successfully |
| see above | ||||||