We were thinking with some of our QA engineers to ...

# compose

[Stylianos Gakis]

We were thinking with some of our QA engineers to look into starting an effort to have them write some UI tests with something like appium (or whatever alternative) but I was worried that now that our App is a hybrid of View/Compose this might be more tricky than it already is. Has someone gone down that road? Got any resources to share regarding it? Maybe I’m missing some part of the official docs. Everything I’ve tried to look regarding such tests with Appium (Maybe appium is the wrong path for them to take) seems to be from 4+ years ago so no mention of compose whatsoever.

[Carson Holzheimer]

Can't confirm with Appium exactly, but Espresso works well. To be honest, the Compose UI is better to test than the View code, because Compose has better matchers.
Didn't run into many problems with shared Compose + View testing, but you need to know (or inspect) what the UI is made of, to know which matchers to use.

[Stylianos Gakis]

Hmm Espresso, and is this something that your QA engineers have been able to do themselves? Our have had some past experience with Appium so we were looking into smth that can potentially make it so that they require as little help from the Android devs as possible.
And have you had luck trying to test screens with a mix of Compose and Views? Any troubles there?

[Carson Holzheimer]

No trouble with mix of compose and views. We have intended to, but haven't yet got any qa team writing espresso / XCUITest tests. I'm also curious how Appium works with Compose

[Stylianos Gakis]

Yeah thanks a lot for sharing your story, we might have to go with that approach as well after all. If you don’t mind, do you know of any sources/articles (even official docs) that you might’ve used to try that out?
And yes I’m also very curious about how Appium could work but have had a very hard time to gather any information regarding it 🙈