Bug Report: UIAutomator Fails to Find Test Tags in Navigation Suite Items

Issue Description

When using material3-adaptive-navigation-suite:1.3.1 with composeBom: 2025.01.00, we observed that UIAutomator cannot locate test tags applied to navigation suite items (Modifier.testTag("item0")), while Espresso Compose Test can. Additionally, UIAutomator can locate a control test tag (e.g., Modifier.testTag("HomeScreenTextTag")) applied to a composable outside of the navigation suite.

---

Expected Behavior

• UIAutomator should detect the testTag on navigation suite items (e.g., "item0") in the same way as Espresso.
• The test tags should be exposed in the view hierarchy for accessibility by UIAutomator.

---

Observed Behavior

1. Espresso Compose Tests:

   • Successfully locate the navigation suite item test tag (e.g., "item0").
   • Successfully locate the control test tag (e.g., "HomeScreenTextTag").

2. UIAutomator:

   • Successfully locates the control test tag ("HomeScreenTextTag").
   • Fails to locate the test tag on navigation suite items ("item0").

---

Steps to Reproduce

1. Download and open the attached project in Android Studio.
2. Run the NavigationSuiteEspressoTest to confirm that Espresso can detect both the navigation suite item ("item0") and the control tag ("HomeScreenTextTag").
3. Run the NavigationSuiteUiAutomatorTest to confirm that:
   • UIAutomator can find the control tag ("HomeScreenTextTag").
   • UIAutomator fails to find the navigation suite item ("item0").

---

Reproducible Code

Navigation Suite Test Tag Assignment

In the MainActivity:

NavigationSuiteScaffold(
    navigationSuiteItems = {
        AppDestinations.entries.forEachIndexed { index, destination ->
            item(
                label = {
                    Text(
                        text = stringResource(destination.label),
                        modifier = Modifier.testTag("item$index") // Assign test tag
                    )
                },
                icon = {
                    Icon(
                        imageVector = destination.icon,
                        contentDescription = stringResource(destination.contentDescription)
                    )
                },
                selected = destination == currentDestination,
                onClick = { currentDestination = destination }
            )
        }
    }
)

Control Test Tag

In HomeDestination:

@Composable
fun HomeDestination() {
    Text(
        text = "Home Screen",
        modifier = Modifier.testTag(HOME_SCREEN_TEXT_TAG) // Control test tag
    )
}

Test Classes

• NavigationSuiteEspressoTest: Confirms Espresso can detect all tags.
• NavigationSuiteUiAutomatorTest: Highlights that UIAutomator fails to detect navigation suite tags.

---

Environment

• Library Version: material3-adaptive-navigation-suite:1.3.1
• Compose BOM: 2025.01.00
• Android Studio: Android Studio Ladybug Feature Drop | 2024.2.2
• Device: Nexus 5 Emulator (API 29)

---

Additional Notes

This issue suggests that test tags on navigation suite items may not be exposed in the view hierarchy in a way that UIAutomator can access. This affects test automation workflows that rely on UIAutomator to interact with navigation components in Compose applications.