RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
The steps for configuring connected clients is same configuring standalone device as mentioned in section 1. Configure device details in Device Manager except that it requires additional data like device login details etc to be included while adding the device.
For eg: For wifi clients, the extra properties should have following fields.
Wifi Clients
Property Required | Description |
---|---|
username | User name to login to client device |
password | Password to login to client device |
connectionType | Expected value: "Wi-Fi" |
wifiCapability | Wifi Capability eg: Dual Band |
wifiMacAddress | Wifi Mac Address |
ethernetMacAddress | Ethernet mac address, which is same as value configured in field ecm mac address/estb mac address |
deviceIp | Ip address of the device, which is same as value configured in field estb ip address/ecm ip address |
devicePort | Tests can connect to client using deviceIp and devicePort |
osType | OS running in client. Eg: Linux, Windows |
nodePort | Node Port |
For Automatics to use devices from partner's inventory, device groups have to be configured. The device group name in inventory should be added here so that user can execute tests on devices within these groups only. Admin user can map device groups to users so that only those users mapped to device group can execute tests on device.
...