Android & Wear OS Testing Guide
This skill provides comprehensive workflows, guidelines, and ADB commands to
test Android applications reliably across both mobile phones and Wear OS
devices. It focuses particularly on triggering system state changes, validating
real-time synchronization, implementing robust UI automation, and simulating
complex edge cases (like Doze mode, data layer disconnection, and Fused Location
spoofing limits).
How to use this skill
- Review the testing tasks or edge cases required for your application.
- Load the relevant reference file for specific guidelines, architectural
constraints, and ADB workflows.
- Cross-reference other active skills to automate system manipulations.
References
- UI Automation Guidelines:
references/ui-automation-guidelines.md
(Generalized "Behave Like a Real User" and "Visual Timeline" policies for
robust, non-flaky UI testing).
- System States & Connectivity:
references/system-states-and-connectivity.md (Bluetooth proxy bottlenecks,
Wi-Fi failovers, Doze mode, and battery simulation).
- Location & Sensors:
references/location-and-sensors.md (Fused Location
Provider security, Mock Location App requirements, Wear OS Health Services
synthetic data, and One-Handed Gestures (Double-Pinch) simulation/overrides).
- Permissions & OS Behavior:
references/permissions-and-os-behavior.md
(Foreground Service types, API 30-36 changes, and Wear OS granular health
permissions).
- Wear Surfaces:
references/wear-surfaces.md (Interacting with Tiles,
Watchfaces, and Complications using DEBUG_SURFACE and DEBUG_SYSUI).
- Testability Patterns:
references/testability-patterns.md (App-side debug
receivers, data seeding, OOBE race conditions, and standby buckets).
Source: ithinkihaveacat/dotfiles — distributed by TomeVault.
1---2name: ithinkihaveacat-dotfiles-dotfiles3description: Android & Wear OS Testing Guide4---56# Android & Wear OS Testing Guide78This skill provides comprehensive workflows, guidelines, and ADB commands to9test Android applications reliably across both mobile phones and Wear OS10devices. It focuses particularly on triggering system state changes, validating11real-time synchronization, implementing robust UI automation, and simulating12complex edge cases (like Doze mode, data layer disconnection, and Fused Location13spoofing limits).1415## How to use this skill16171. Review the testing tasks or edge cases required for your application.181. Load the relevant reference file for specific guidelines, architectural19 constraints, and ADB workflows.201. Cross-reference other active skills to automate system manipulations.2122## References2324- **UI Automation Guidelines**: `references/ui-automation-guidelines.md`25 (Generalized "Behave Like a Real User" and "Visual Timeline" policies for26 robust, non-flaky UI testing).27- **System States & Connectivity**:28 `references/system-states-and-connectivity.md` (Bluetooth proxy bottlenecks,29 Wi-Fi failovers, Doze mode, and battery simulation).30- **Location & Sensors**: `references/location-and-sensors.md` (Fused Location31 Provider security, Mock Location App requirements, Wear OS Health Services32 synthetic data, and One-Handed Gestures (Double-Pinch) simulation/overrides).33- **Permissions & OS Behavior**: `references/permissions-and-os-behavior.md`34 (Foreground Service types, API 30-36 changes, and Wear OS granular health35 permissions).36- **Wear Surfaces**: `references/wear-surfaces.md` (Interacting with Tiles,37 Watchfaces, and Complications using `DEBUG_SURFACE` and `DEBUG_SYSUI`).38- **Testability Patterns**: `references/testability-patterns.md` (App-side debug39 receivers, data seeding, OOBE race conditions, and standby buckets).4041---42> Source: [ithinkihaveacat/dotfiles](https://github.com/ithinkihaveacat/dotfiles) — distributed by [TomeVault](https://tomevault.io).43<!-- tomevault:4.0:skill_md:2026-06-30 -->
tomevault-io