Feature Requests

We would like to request a change to the Suitest HTTP API, specifically the Get device detail endpoint (/devices/{deviceId}). Currently, the API does not return information about platform-related errors, making it difficult to identify errored devices since their status remains ready. By exposing this data via the API, we can improve automation, monitor device health more effectively, and reduce manual intervention when platform-related issues occur.

We would like to have a feature to reserve the device for specific user without disabling it, or being connected to it. This would help to use the device and launch a short tests without being interupted by other users. For example - we want to keep the application up and running for a specifc amount of time and during that we want to launch an automated test to quick check if app is working fine. We cannot do such a case disabling the device.

Can we add Test re-runs, sometimes the test cases fail and we have to come back and run the failed test cases. Can we add something so that all the failed testcases are re run again.

Add the feature to uninstall an app package from a device (just like the @install test pack tag installs, an @uninstall tag would be useful, e.g. for app cleanup after a testing period, no need to clutter a device with multiple app versions).

Because only one user can be connected to a device at a time, it's often the case that someone might be connected to a device you need to use. It would be very useful if Suitest actually told us who was connected to the device, so we can easily contact them and ask them to release it.

It would be nice if there was a way to send custom adb commands to the device being tested via the suitest API and receive the response. This would help to cover 2 similar situations: 1. When the Suitest API doesn't support certain actions on android, this would help us bridge the gap by implementing some custom solution until that time. And 2: Allow a potential custom back-channel into the app so we can instruct it to do certain things that would be impossible via the UI.

I did not have a toke id

https://suite.st/docs/testing/test-subjects/view-element-subject/#validating-element-visibility Looks like it is possible on some platforms to see whether an element is visible or not. Would be great to have on Apple TV as well.

As a TV Lab admin, during adding device (test existing remote), i want to chose which buttons i want to test AND in which order. 1)show virtual remote, so user can navigate TV to actually be able to test all of the buttons w/o need of using actual remote (eg. to navigate to place where numbers or play / pause / fwd can be tested) 2)show virtual remote. Instruct user to click on desired button. After user clicks button, wizzard asks if TV received a command ad acted accordingly. (eg. on the start user clicks power button, wizzard asks if user confirms power button is set up correctly) 3) here also add a option to skip rest of buttons. Buttons non tested here should be unactive / grayed out.

Suitest contains remote control mappings for many common TV models (LG, Samsung..). However, mapping needs to be tested button by button when adding a device. Would it be possible to skip this step, since most of the times existing button mapping is 100% correct?