finding-nodes-by-tag-text-content

Locate Jetpack Compose semantics nodes using tag, text, or content description matchers.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill finding-nodes-by-tag-text-content-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-nodes-by-tag-text-content
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/compose/finders/finding-nodes-by-tag-text-content
Command: npx skills add https://github.com/trancee/MeshLink-template --skill finding-nodes-by-tag-text-content-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves common UI testing failures in Jetpack Compose, such as ambiguous matches, missing nodes, or brittle tests that break due to copy edits and locale changes.

Core Features & Use Cases

  • Robust Node Location: Provides guidance on using test tags over text-based matching to ensure test stability.
  • Tree Management: Explains when to toggle the useUnmergedTree flag to access inner composable elements.
  • Cardinality Handling: Offers patterns for using collection finders to verify expected node counts rather than relying on single-node assertions.

Quick Start

Use the finding-nodes-by-tag-text-content skill to identify the correct Compose finder and tree configuration for your specific UI test failure.

Frequently Asked Questions about finding-nodes-by-tag-text-content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix ambiguous node matches in Jetpack Compose UI testing?

To fix ambiguous node matches in Jetpack Compose UI testing, use production-defined test tags instead of text-based matchers to ensure stable, precise node location within the semantics tree.

Why does my Compose UI test fail to find a node by text?

Compose UI tests fail to find nodes by text when copy edits or locale changes alter the string. Use test tags for robust node location to prevent brittle test failures.

When should I use the useUnmergedTree flag in Compose UI tests?

Toggle the useUnmergedTree flag in Compose UI tests when you need to access inner composable elements that are hidden within merged tree structures during standard semantics tree traversal.

What is the best way to verify expected node counts in Compose test automation?

The best way to verify expected node counts in Compose test automation is using collection finders for cardinality handling, rather than relying on single-node assertions to check semantics nodes.

How do test tags improve Android development UI test stability?

Test tags improve Android development UI test stability by enforcing precise semantics tree traversal, bypassing brittle text matchers that break due to localization or copy edits.