Deployment
| # | Sub Module | Test Cases | Status | Notes |
|---|---|---|---|---|
| 1 | Deployment | Verify all DCAE services can be deployed via helm and passing healthcheck | ||
| 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 - 0: Integration Weather Board for Jakarta Release | |
| 5 | Event Flow | Verify data flow into TCAgen2 and CL o/p | ||
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/2022-04/13_02-39/xtesting-smoke-usecases-robot/dcaemod/dcaemod/report.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 Helm charts are generated and loaded into Chartmuseum registry | see above | |
| 7 | Deployment | Perform deployment via Helm for generated charts and verify container comes up successfully |
| see above |