[Android] Testing Compose layout

The problem

I haven’t checked well yet, but maybe do we need something in espresso driver? https://developer.android.com/jetpack/compose/testing

---

Update: Espresso driver https://github.com/appium/appium-espresso-driver is getting compse support. UIA2 driver cannot support it because of technical differences.

---

Updated

• Espresso driver
  • https://github.com/appium/appium-espresso-driver#jetpack-compose-support
• UIA2 driver (via extra)
  • https://github.com/appium/appium-uiautomator2-server/pull/467

---

Updated

• UIA2 driver also can find a compose element if the element had testTagsAsResourceId . You can access to the element as resource-id.
  • Appium 1 can access to these elements via XPath https://github.com/appium/appium/issues/15138#issuecomment-1127658653 (since the version autocomplete its package name as valid resource-id rule.)
  • disableIdLocatorAutocompletion settings api helps to disable package name autocomplete in case you set an arbitrary name as the testTagsAsResourceId, without the package name in compose.

[omar-leyva]

Google updated their AccessibilityNodeInfo to include testTag in the AccessibilityNodeInfo.extras object starting in compose UI 1.1.0-beta01. https://android-review.googlesource.com/c/platform/frameworks/support/+/1853077

Is this something that can be used to expose testTag in UIA2?

[davidgalindo]

My company’s QA team is making extensive use of Appium for their automated tests. I recently wrote a few sections of our app using Jetpack Compose, and QA has stated that it has completely broken the tests that deal with UI generated with Compose. They are unable to find any views by using their resource ID or content description. Apparently when I set a content description on a view using Modifier.semantics{ contentDescription = "my ID" }, QA is unable to focus in on the exact view. For example, take this piece of code:

        OutlinedTextField(
            email,
            modifier = Modifier
                .fillMaxWidth()
                .layoutId(R.id.textInputEmail)
                .semantics { contentDescription = getString(R.string.sign_in_email_input) }
                .padding(start = 16.dp, end = 16.dp, top = 8.dp, bottom = 4.dp),
            onValueChange = { email = it },
            label = { Text(getString(R.string.email)) },
        )

QA is only able to see this: Note that the content description is on a subview, not on the editText itself. The layoutId doesn’t help much, either.

Compose just hit its release version yesterday, and as a developer it is so much easier to work with than the declarative XML approach. We need Appium to work with compose since, in my opinion, the benefits to using Compose over XML are far too great. I appreciate the Appium team’s quick attention to this matter 😄