y

    yschimke

    6 months ago
    The UiAutomator code in Compose Macrobenchmarks makes me a bit sad. I do wonder whether there could be say a Compose aware higher level API, since I suspect we are going to replicate various bespoke implementations of actions scroll through list.
    Maybe there are things we can put into compose to make it easier for benchmark tests to activate this? More detail in content desc, some state? Do we know if anyone is already trying to make UiAutomator better for Compose generally?
    cc @Steve Bower [G]
    Steve Bower [G]

    Steve Bower [G]

    6 months ago
    I am aware of an edge case where device.findObject is failing and we're looking at that, but other than that, not aware of specific efforts on adding a Compose layer over UiAutomator. If there are things that you can't get to work using the existing API, let us know.
    y

    yschimke

    6 months ago
    Well, like the scrolling code being occasionally a click, makes the tests flaky.
    And I don't full understand the drag logic, be nice if there were operations like scroll list one page (up/down). I guess back is easy because of button events.
    Steve Bower [G]

    Steve Bower [G]

    6 months ago
    Update on device.findObject - the error was explained by running
    adb shell uiautomator dump
    which showed that the bounds of one of the components on the screen was taking up the whole screen - so no UI elements underneath were 'findable'.