I have a class which extends `AbstractComposeView` that wraps our Button component, to allow our leg...

# compose

[zsperske]

I have a class which extends AbstractComposeView that wraps our Button component, to allow our legacy XML pages to make use of the component. In our existing UI tests we have espresso calls like onView(withId(id)).perform(click()) . When using this method on the Compose view, no click event is triggered. Has anyone else run into this/know of a fix?

[Lisandro Di Meo]

Espresso cannot see elements inside compose views

[Lisandro Di Meo]

I dont know if this is exactly your problem, but maybe it could be that

[Lisandro Di Meo]

However, If you dont want to change your tests, you can use UiAutomation to find these elements

[zsperske]

An espresso version bump fixed it! I am curious though, if I run into other issues what would UiAutomation do for me?

[Lisandro Di Meo]

really? I didn't know that, so now with espresso you can find composables?

[zsperske]

I didn’t have to make any code changes, i think it may have just been a bug

[Lisandro Di Meo]

the famous flaky tests (? 😄

[zsperske]

// has a Composable inside
<OurComposeButton 
    android:id="@+id/ourButton" />

onView(withId(R.id.ourButton)).perform(click())

[Lisandro Di Meo]

UiAutomation (as far as I know) uses accessibility features to find widgets, so its more useful to test more general stuff (or in scenarios where you cant use espresso)

[zsperske]

ah got it

[Lisandro Di Meo]

OurComposeButton inherits from AndroidComposeView, right? if thats the case, it should work fine with espresso 👌

[zsperske]

yeah it does, once I got onto the latest espresso version the click started working

[Daniele Segato]

UIAutomator let you find elements on screen and interact with them, regardless of those elements been part of your app or the OS.
(for example you can press OS permissions buttons)