traversing-the-semantics-tree

To find a parent or sibling node in Jetpack Compose UI testing, traverse the semantics tree using relationship operators like onParent(), onSibling(), and onAncestors() instead of relying on brittle index-based assumptions. This locates relative nodes structurally when single matchers fail.

The best way to test a Compose node without a stable testTag is navigating the semantics tree by structural relationships. You can use operators like onChildren() or onChildAt() alongside filterToOne(matcher) to safely narrow down and assert the target node.

onChildren() does not find all items in a LazyColumn because LazyColumn and LazyRow only include currently composed children in the semantics tree. The onChildren() operator captures a snapshot, meaning off-screen items that are not composed will not be found.

You should traverse the semantics tree when dealing with complex structural relationships like finding an nth child or sibling. Prefer semantics matchers like hasAnyAncestor or hasAnyDescendant when checking for specific properties across the tree, and add a stable testTag whenever possible to avoid brittle navigation.

You can apply useUnmergedTree for semantics traversal, but it is sticky across subsequent navigation operations. Once enabled, it persists throughout the node traversal chain, affecting how all downstream parent, child, and sibling nodes are evaluated in the semantics tree.