Remote Testing of Large-screen Devices

The SmartTUBE allows you remote performing of test scenarios on large-screen devices and analyze the results in the QoS system SmartCARE. These tests simulate pressing buttons on the remote control, causing the corresponding reactions of the SmartTUBE apps.

This instruction applies to SmartTUBE app of versions JUNG 7.0.xx and later.

Now let’s do it step-by-step.

Create a JSON file with a test script of the following format:

{

“steps”: [ // List of steps to be fired sequentially in the SmartTUBE app on the end-user device

{

“keyPress”: “KEY_1”, // Simulate pressing a button on the remote control. Allowable values: KEY_N (numeric button) CH_UP, CH_DOWN, RIGHT, DOWN, LEFT, UP, ENTER, BACK, HOME.
“sleep”: 5000 // Delay (pause), in msec.
},
{
“sleep”: 900000
},
{
“keyPress”: “KEY_2”,
“sleep”: 5000
},
{
“sleep”: 900000
},
{
“keyPress”: “KEY_3”,
“sleep”: 5000
}
]
}

Upload the file to SmartTUBE Device Manager for the type and device group to which the tested device belongs (in the same way you upload the configuration file setup.json).
Run the SmartTUBE app on the device.

f it is already running, restart the app by sending the following notification via a web browser, for example:

${BACKEND_HOST}/api/v1/notifications/notify?uuid=${TESTED_DEVIСE_UUID}&notification=command%3FcommandType=Control%26commmandName=Reboot%26requestDelay=0

where ${BACKEND_HOST} and ${TESTED_DEVIСE_UUID} should be replaced with the relevant values.

Example:

https://sdp.some.tv/api/v1/notifications/notify?uuid=9558-4434-a0e4-e4297840db15&notification=command%3FcommandType=Control%26commandName=Reboot%26requestDelay=0

Tests can only be run from devices of the same service account. Therefore, you should first link the PC, from which you will run the tests, and the tested device to one service account. To do this, send two notifications:

${BACKEND_HOST}/api/v1/multiroom/link?login=${LOGIN}&password=${PASSWORD}&uuid=${ADMIN_DEVICE_UUID}&deviceType=WEB

${BACKEND_HOST}/api/v1/device/authorize?uuid=${ADMIN_DEVICE_UUID}&appVersion=6.10.29&stbType=&deviceType=WEB&demo=0&useSameSite=true&lang=en

${ADMIN_DEVICE_UUID} is uuid of the PC from which you will run the tests. ADMIN_DEVICE_UUID and TESTED_DEVIDE_UUID cannot be the same.

Example:

https://sdp.some.tv/api/v1/multiroom/link?login=jung_channel_zapping&password=12345&uuid=test-123&deviceType=WEB

https://sdp.some.tv/api/v1/device/authorize?uuid=test-123&appVersion=6.10.29&stbType=&deviceType=WEB&demo=0&useSameSite=true&lang=en

Now run the test by sending the following notification:

${BACKEND_HOST}/api/v1/notifications/notify?uuid=${TESTED_DEVIСE_UUID}&notification=command?commandType=Control%26commandName=runTest%26name=${TESTS_FILE}

${TESTS_FILE} — the name of the JSON file with the test script.

Example:

https://sdp.some.tv/api/v1/notifications/notify?uuid=9558-4434-a0e4-e4297840db15&notification=command?commandType=Control%26commandName=runTest%26name=autotests_channels_buffering.json

The device downloads the script file every time when you send the runTest notification. So you can edit it in the SmartTUBE Device Manager, fire the notification and analyze the results in the SmartCARE very quickly.

You can also stop the test performing by sending the runTest notification with the empty name argument.

See the results in the SmartCARE > Main menu > Device list by finding the device by UID.

Remote Testing of Large-screen Devices

CONTENTS