android e2e testing

Engineering Community

Skill notes

When to Use

After implementing or modifying native Android UI components (toolbars, tabs, menus) When verifying Jetpack Compose components (@expo/ui/jetpack-compose) When running the native-navigation or other E2E apps on Android Before opening a PR that touches Android-specific behavior

Prerequisites

An Android emulator must be running. Prefer Pixel emulators over tablet ones for standard phone-sized testing.

Router E2E apps

Package name: dev.expo.routere2e Each app in apps/router-e2e/__e2e__/ has a corresponding yarn android:<name> script. Check apps/router-e2e/package.json for available scripts. If the app is already built, relaunch it: To find the package name of any installed app:

Step 2: Navigate Using UI Dump

CRITICAL: Always use uiautomator dump for element coordinates. Screenshot pixel coordinates have display scaling factors that make them unreliable for adb shell input tap. The UI dump provides actual device coordinates.

Dump the view hierarchy

This returns XML with every UI element including: text — displayed text content-desc — accessibility description (useful for icon buttons) bounds — position as [left,top][right,bottom] clickable — whether the element responds to taps

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@expo · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview android-e2e-testing.preview
# Step 5: Report Results

After testing, summarize results in a table: | Test | Result | |------|--------| | Navigation to screen | PASS/FAIL | | Component renders correctly | PASS/FAIL | | Interaction works | PASS/FAIL | | No JS errors in logcat | PASS/FAIL | Include details for any failures: what was expected vs what happened, relevant logcat output, and screenshots. Preferably attach screenshots for features you tested.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.