RDKB Automatics Test - Connected Client Environment Setup

Scope

The coverage of automatics includes standalone device testing as well as testing on connected setup. This document specifies the minimal setup required for testing connected client scenarios.

Hardware Requirements

• DUT
• Wifi Chamber
• Connected Clients
  • 2 NUC [Windows Client connected via WIFI]
  • 1 RbPi [Linux Client connected via Ethernet]
• In Chamber Cables
  • Mgmt Device cabling
  • Serial Cables
• Switch
• Power Module

Software Requirements

Points to note while using Linux based client (Connected via WIFI)

1. Need to disable password prompt while giving the Sudo commands. This can be disabled by following the below steps:
   1. edit /etc/sudoers file - "sudo visudo"
   2. add  "<YOUR_USERNAME_HERE> ALL=(ALL) NOPASSWD: ALL " to the file. 
   3. save the file.

Design

Points to note:

1. Dedicated IP will be assigned to individual chamber setup.
2. Each connected devices within the chamber will be assigned unique ports to access individual services like one for SSH/Selenium/VNC/RDP etc.

With the IP and port combination we can access any service in any connected device. 

Configurations

All the connected devices in the setup will be added to a single home account in Device Manager.

Framework Workflow

When connected scenario  test is triggered in automatics 

1. Framework will check the accessibility of Dut and will lock the device if accessible.
2. Secondarily framework will try to fetch the details of connected devices linked to the home account. 
3. Then a check for the accessibility of the connected devices will be performed by trying SSH to the devices.
4. All the devices that are SSHable will be locked and the tests are triggered.

Device Mapping Template

Below table will give an idea about how the port mapping and connectivity is done to connect clients with DUT.