Jetpack compose compatibility

[google]

Jetpack compose compatibility

[oknirb]

When ATF is used within an Espresso test, it is not possible for it to inspect Compose content from using the currently released versions. However, API 34 adds new functionality that will make this feasible.

[bassettsj]

Wanted to follow up here asking what is the scope of work to enable support for ATF?

It has been a big blocker for us at Airbnb to enable accessibility checks for our Jetpack Compose components and would love to find a solution if possible.

[nishanth043]

+1 on this. I can only run these checks on a Jetpack Compose rootView. But when I run it, I only get suggestions for the rootView of the screen and it does not go through all the child Composables like it would on a view based application.

But, I see that the "Accessibility Scanner" app somehow gives me correct results on Compose screens as well.

Could you please give some guidance on how to run the checks in the repo on Compose screens? Any documentation on this would help greatly.

[foster55ff]

I have the same Question. Are there any plans to support Jetpack Compose with this tool?

[yschimke]

I assume this, so devices and emulators, but not robolectric?

Accessibility-Test-Framework-for-Android/src/main/java/com/google/android/apps/common/testing/accessibility/framework/uielement/AccessibilityHierarchyAndroid.java

Line 644 in 858625c

if (BuildCompat.isAtLeastU() && !isRobolectric()) {

    public AccessibilityHierarchyAndroid build() {
      AccessibilityHierarchyAndroid result;
      if (fromRootView != null) {
        if (BuildCompat.isAtLeastU() && !isRobolectric()) {
          result =
              buildHierarchyFromViewAndItsNodeInfo(
                  fromRootView, getAccessibilityNodeInfoExtraDataExtractor());
        } else {
          result =
              buildHierarchyFromView(fromRootView, getAccessibilityNodeInfoExtraDataExtractor());
        }

[oknirb]

That's correct. The Nov 2023 commit added support for UIs containing Compose content when running with Android 10 (API 34), but not on Robolectric.

It also added ElementMatchers (similar to Espresso's ViewMatchers) and matchesElements to support matching AccessibilityViewCheckResults with ViewHierarchyElements that are not from Views.

This is still a work in progress.

[yschimke]

Specifically for Robolectric, is the bulk of the technical work in robolectric or ATF?