@günther as I understand Appium works as follows: TestScript—W3C_WebDriver_protocol—>Appium_Server—UiAutomator2_Driver—>Android_APK. The UiAutomator2 driver (executed on Appium Server) relies on the UiAutomator technology (from Google) + ADB + Android SDK and makes automation mapping from W3C WebDriver calls to Google UiAutomator technology. Because Felago uses custom UI Qt Quick elements to provide a richer user experience therefore that elements won’t provide automatic accessibility support for UiAutomator (https://developer.android.com/training/testing/other-components/ui-automator#ensure-activity) and consequently Appium. But Squish can do it. Is my understanding correct?
Yes, Qt (and Felgo) have a custom rendering, so everything is drawn by the Qt application based on the Qt/Felgo controls and layout in your QML UI. The tech stack is thus a bit different, so I am not sure if the Android UiAutomator is usable in some way.
Want to find out if Felgo is a good fit for your company?
As part of the free Business evaluation, we offer a free welcome call for companies, to talk about your requirements, and how the Felgo SDK & Services can help you. Just sign up and schedule your call.
Sign up now to start your free Business evaluation: