| Sl.No | Sanity tested on | Status |
| 1 | onewifi systemd service should be RUNNING in ctrl and Extender | Pass |
| 2 | No core files won't be observed in /tmp folder in ctrl and Extender | Pass |
| 3 | systemctl status ieee1905_em_ctrl should be RUNNING state in ctrl | Pass |
| 4 | systemctl status em_ctrl should be RUNNING state in ctrl | Pass |
| 5 | systemctl status ieee1905_em_agent should be RUNNING state in ctrl and Extender | Pass |
| 6 | systemctl status em_agent should be RUNNING state in ctrl and Extender | Pass |
| 7 | check default db values are updated in mariadb | Pass |
| 8 | EasyMesh and ieee1905 logs files should be generated in /tmp folder for Controller and Extender | Pass |
| 9 | All configured VAPs(fronthaul,backhaul,iot) should be UP and Running - to be confirm by iw dev command for both controller and Extender | Pass |
| 10 | VAPs should be broadcasting EasyMesh default SSIDs(eg, private_ssid, mesh_backhaul) for both controller and Extender | Pass |
| 11 | Able to connect clients via fronthaul vaps for both controller and extender | Pass |
| 12 | Able to get IP for fronthaul connected clients | Pass |
| 13 | Able to get Internet for fronthaul connected clients | Pass |
| 14 | mld0 interface should be created - to confirm by iw dev for both controller and Extender | Pass |
| 15 | Mld0 interface should have linked with all private vaps for both controller and Extender | Pass |
| 16 | In Extender ,Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface .
iw dev wifi1.3 info – use this command to confirm in Extender | Pass |
| 17 | Verify mesh backhaul connection in EM-Contrller side as well. iw dev wifi1.1.sta<i> info iw dev wifi1.1.sta<i> station dump
## This command gives information on connected client ie Extender1. | Pass |
| 18 | In Extender , ping 10.0.0.1 -c 5 | Pass |
| 19 | Able to launch RDKB CLI in browser by using ctrl wan ip (i.e erouter0_IP:8888) | Pass |
| 20 | Able to Navigate all the tab in RDKB CLI | Pass |
| 21 | In iw dev , Able to see the updated ssid in ctrl and Extender when we changing the ssid names from RDKB CLI | Pass |
| 22 | Able to change password from RDKB CLI | Pass |
| 23 | Able to change the channel from RDKB CLI for all available radio bands | Fail |
| 24 | Able to do wifi reset from RDKB CLI | Fail |
| 25 | Able to see the N/W topology in CLI | Fail |
| 26 | Able to connect clients with updated ssid for both controller and Extender | Pass |
| 27 | Able to take ssh for both controller and Extender | Pass |
| 28 | Able to make daisy chain and STAR Topology | Pass |
| 29 | Able to get IP for lan clients for both controller and Extender | Pass |
| 30 | Able to get internet for connected lan clients | Pass |
