cross-app-tests-with-uiautomator

Automate cross-process Android UI tests with UiAutomator 2.3.0.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill cross-app-tests-with-uiautomator-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-app-tests-with-uiautomator
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/instrumentation/uiautomator/cross-app-tests-with-uiautomator
Command: npx skills add https://github.com/trancee/MeshLink-template --skill cross-app-tests-with-uiautomator-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the limitation where standard Android test frameworks like Espresso fail when interacting with system-level UI or foreign applications, preventing tests from spanning across process boundaries.

Core Features & Use Cases

  • Cross-Process UI Interaction: Enables automation of system settings, notifications, and third-party app interfaces that are inaccessible to standard view-based testing.
  • Robust Element Handling: Provides advanced mechanisms for managing UI element lifecycles, including automatic recovery from StaleObjectException and precise waiting conditions.
  • Use Case: Use this skill to verify that your application correctly handles a share-sheet interaction or to automate a test flow that requires toggling Wi-Fi settings via the system menu.

Quick Start

Use the cross-app-tests-with-uiautomator skill to initialize the UiDevice singleton and perform a system-level action like opening the notification shade or navigating to the device home screen.

Frequently Asked Questions about cross-app-tests-with-uiautomator

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

FAQPage Schema
How do I automate cross-app UI testing on Android when Espresso fails to interact outside my process?

Android cross-app UI testing requires the UiAutomator framework to drive interactions across process boundaries. It automates system settings, notifications, and third-party app interfaces where standard view-based testing frameworks cannot access elements.

What is the best way to test system-level UI flows like the notification shade on Android?

Testing system-level UI flows involves initializing the UiDevice singleton via instrumentation to control the device. You can open the notification shade, navigate home, or toggle system settings, verifying cross-process interactions robustly.

How do I handle StaleObjectException during Android system-UI test automation?

Handling StaleObjectException during system-UI test automation requires advanced element lifecycle management mechanisms. UiAutomator provides automatic recovery from stale object exceptions and precise waiting conditions to ensure robust element lookup.

Can I use UiAutomator to verify a share-sheet interaction with third-party apps?

Yes, you can use UiAutomator to verify share-sheet interactions or automate flows involving third-party apps. It targets scenarios requiring navigation across application boundaries and system settings inaccessible to standard testing frameworks.

When do I need to use UiAutomator instead of Espresso for Android testing?

You need UiAutomator instead of Espresso when your tests span across process boundaries. Use it to automate system settings, notification shade management, and foreign application interfaces that standard view-based testing cannot access.