The purpose of this page is to identify the test cases that are targeted for automation, plus identify other test cases that are planned to be executed as part of Amsterdam release that may not necessarily be candidates for automation. They may be attempted as a stretch goal, but not committed for R1.
Test Cases for Automation identified at M2
| No | Test Description | Notes | Planned for Automation | JIRA Link | Comments? |
|---|---|---|---|---|---|
| 1 | Run a simple “docker ps” to check if all the containers needed to be up are up | Yes | APPC-111 - Getting issue details... STATUS | ||
| 2 | Validate ODL Installation | Yes | APPC-112 - Getting issue details... STATUS | ||
| 3 | Validate required bundles are present | Validate SLI, APPC & Config Management , etc... | Yes | APPC-115 - Getting issue details... STATUS | |
| 4 | Verify APPC karaf bundles are Active | Test is completed via command line on ODL node. Check that all karaf features have been installed correctly (from the APPC side and the SDNC karaf features/bundles that utilized by APPC) | Yes | APPC-116 - Getting issue details... STATUS | |
| 5 | Verify property files | Yes | APPC-117 - Getting issue details... STATUS | ||
| 6 | Validate MySql Nodes | Yes | APPC-118 - Getting issue details... STATUS | ||
| 7 | Run a simple netstat check APPC ports | APPC ports that are expected to be up are active and available | Yes | APPC-119 - Getting issue details... STATUS | |
| 8 | Run a telnet test to check if the ports that APPC has shown as active can be reached | Yes | APPC-120 - Getting issue details... STATUS | ||
| 9 | Test Health Check API's | RestConf healthcheck | Yes | APPC-113 - Getting issue details... STATUS | |
| 10 | Test APIs are up via Swaggar API | Yes | APPC-124 - Getting issue details... STATUS | ||
| 11 | Test A&AI Connectivity | Yes | APPC-114 - Getting issue details... STATUS | ||
| 12 | Test DMaaP Connectivity | Yes | APPC-125 - Getting issue details... STATUS | ||