安卓端到端测试
- 作者仓库星标 49,853
- 作者仓库 expo
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @expo · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 2 步:使用 UI 转储进行导航
关键:始终使用 `uiautomator dump` 作为元素坐标。屏幕截图像素坐标具有显示缩放因子,这使得它们对于`adb shell input tap`来说不可靠。 UI 转储提供实际的设备坐标。
第 5 步:报告结果
测试后,将结果总结在表格中: 测试 · 结果导航到屏幕 · 通过/失败 组件正确渲染 · 通过/失败 交互工作 · 通过/失败
# Android E2E Testing for Expo Router
Use `adb` to manually test Expo Router screens and components on Android emulators.
## 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.
```bash
# Verify emulator is connected
adb devices
# Check which emulator is running
adb -s DEVICE_ID emu avd name
# Check screen resolution (important for coordinate calculations)
adb -s DEVICE_ID shell wm size
```
## Step 1: Build and Launch
### 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.
```bash
cd apps/router-e2e
yarn android:[APP_NAME] # e.g. yarn android:native-navigation
```
If the app is already built, relaunch it:
```bash
adb shell monkey -p dev.expo.routere2e -c android.intent.category.LAUNCHER 1
```
To find the package name of any installed app:
```bash
adb shell pm list packages | grep -i <keyword>
```
## 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
```bash
adb shell uiautomator dump /sdcard/ui.xml && adb shell cat /sdcard/ui.xml
```
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
- `class` — Android view class
### Find and tap an element
1. Search the XML for your target element by `text` or `content-desc`
2. Extract the `bounds` attribute: `bounds="[left,top][right,bottom]"`
3. Calculate center: `x = (left + right) / 2`, `y = (top + bottom) / 2`
4. Tap:
```bash
adb shell input tap <x> <y>
```
**Example:** For `bounds="[367,498][714,633]"`:
- x = (367 + 714) / 2 = 540
- y = (498 + 633) / 2 = 565
```bash
adb shell input tap 540 565
```
### Wait for navigation to settle
After tapping a navigation element, wait before verifying:
```bash
sleep 1
```
For slow transitions or heavy screens, use `sleep 2`.
## Step 3: Interact
### Tap items
```bash
adb shell input tap <x> <y>
```
### Scroll
```bash
# Scroll down
adb shell input swipe 540 1500 540 500 300
# Scroll up
adb shell input swipe 540 500 540 1500 300
# Scroll further (larger distance)
adb shell input swipe 540 1500 540 200 500
```
### Type text
```bash
adb shell input text "hello%sworld" # %s = space
```
### Press hardware buttons
```bash
adb shell input keyevent 4 # Back
adb shell input keyevent 3 # Home
adb shell input keyevent 82 # Menu / React Native dev menu
```
### Long press
```bash
adb shell input swipe <x> <y> <x> <y> 1000
```
## Step 4: Verify
### Visual verification via screenshot
```bash
adb shell screencap -p /sdcard/screenshot.png && adb pull /sdcard/screenshot.png /tmp/screenshot.png
```
Then use the `Read` tool to view `/tmp/screenshot.png`. Screenshots are useful for:
- Confirming visual appearance (colors, layout, styling)
- Verifying toolbar/tab positioning
- Checking selection states and visual feedback
**Note:** Use screenshots for *visual* verification only. For element positions and tapping, always use `uiautomator dump`.
### Programmatic verification via UI dump
```bash
adb shell uiautomator dump /sdcard/ui.xml && adb shell cat /sdcard/ui.xml
```
Search the XML for expected content:
- Verify text content appears
- Check `content-desc` for accessibility labels
- Confirm element presence after navigation
- Verify selection states (look for checkmarks, content-desc changes)
### Check for errors
```bash
# React Native JS errors
adb logcat -d -s ReactNativeJS:E | tail -20
# Crash logs
adb logcat -b crash -d
# All recent errors
adb logcat -d *:E | tail -30
```
## 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.
## Testing Jetpack Compose Components
Components from `@expo/ui/jetpack-compose` (like `HorizontalFloatingToolbar`, `IconButton`, `Host`) render as Compose views inside React Native. In UI dumps they appear as:
- `androidx.compose.ui.platform.ComposeView` — the Compose container
- `android.widget.HorizontalScrollView` — inside toolbar layouts
- `android.widget.Button` — Compose buttons
- `android.view.View` with `content-desc` — icon buttons with accessibility labels
When testing Compose components:
1. Look for `content-desc` attributes to identify buttons (e.g., `content-desc="Clear selection"`)
2. The `ComposeView` wrapper may have different bounds than the inner interactive elements
3. Tap the interactive element's bounds, not the container's
## Troubleshooting
### uiautomator dump fails or returns empty
This can happen during animations or transitions. Wait and retry:
```bash
sleep 2 && adb shell uiautomator dump /sdcard/ui.xml && adb shell cat /sdcard/ui.xml
```
### Tap doesn't register
- Recalculate coordinates from a fresh UI dump — the layout may have shifted
- Ensure you're tapping a `clickable="true"` element
- Try tapping the parent element if the child isn't clickable
### App navigated to wrong screen or went to home
- The Back button (`keyevent 4`) can exit the app entirely if on the root screen
- Use `monkey` command to relaunch: `adb shell monkey -p dev.expo.routere2e -c android.intent.category.LAUNCHER 1`
- Wait 2 seconds after launch before interacting
### Metro bundler not connecting
```bash
adb reverse tcp:8081 tcp:8081
```
### App crashes on launch
```bash
# Check crash buffer
adb logcat -b crash -d
# Look for fatal exceptions
adb logcat -d | grep -A 10 "FATAL EXCEPTION"
```
### Reload the app
```bash
# Open React Native dev menu and tap Reload
adb shell input keyevent 82
# Or force-stop and relaunch
adb shell am force-stop dev.expo.routere2e && adb shell monkey -p dev.expo.routere2e -c android.intent.category.LAUNCHER 1
```
## Disable Animations (Recommended for Testing)
Disabling animations prevents flaky UI dumps and makes testing more reliable:
```bash
adb shell settings put global window_animation_scale 0
adb shell settings put global transition_animation_scale 0
adb shell settings put global animator_duration_scale 0
```
Re-enable when done:
```bash
adb shell settings put global window_animation_scale 1
adb shell settings put global transition_animation_scale 1
adb shell settings put global animator_duration_scale 1
```
## Complete Example: Testing a Toolbar Screen
```bash
# 1. Launch app
adb shell monkey -p dev.expo.routere2e -c android.intent.category.LAUNCHER 1
sleep 2
# 2. Dump UI to find navigation button
adb shell uiautomator dump /sdcard/ui.xml && adb shell cat /sdcard/ui.xml
# Find: content-desc="Android Toolbar" bounds="[367,498][714,633]"
# Center: (540, 565)
# 3. Navigate to screen
adb shell input tap 540 565
sleep 1
# 4. Take screenshot to verify visual appearance
adb shell screencap -p /sdcard/screenshot.png && adb pull /sdcard/screenshot.png /tmp/screenshot.png
# 5. Dump UI to find toolbar buttons
adb shell uiautomator dump /sdcard/ui.xml && adb shell cat /sdcard/ui.xml
# Find buttons by content-desc: "Clear selection", "Select all", "Delete", "Add"
# 6. Test toolbar interactions
adb shell input tap 457 2233 # "Select all" button center
sleep 1
# 7. Verify state changed
adb shell screencap -p /sdcard/screenshot.png && adb pull /sdcard/screenshot.png /tmp/screenshot.png
# 8. Check for errors
adb logcat -d -s ReactNativeJS:E | tail -20
```
章节与文件索引
按说明文件中的顺序排列。
何时使用
先决条件
路由器端到端应用
第 2 步:使用 UI 转储进行导航
转储视图层次结构
文件/命令 -> adb · @expo/ui/jetpack-compose · native-navigation · dev.expo.routere2e · apps/router-e2e/__e2e__/ · yarn android:<name> · apps/router-e2e/package.json · uiautomator dump
内容校验值 -> c702bda406d3
当前原文的自动摘译,尚未人工审校。
何时使用
实现或修改本机 Android UI 组件(工具栏、选项卡、菜单)后 验证 Jetpack Compose 组件 (
@expo/ui/jetpack-compose) 时 在 Android 上运行native-navigation或其他 E2E 应用程序 在打开涉及 Android 特定行为的 PR 之前先决条件
Android 模拟器必须正在运行。对于标准手机大小的测试,更喜欢使用 Pixel 模拟器而不是平板电脑模拟器。
路由器端到端应用
包名称:
dev.expo.routere2e``apps/router-e2e/__e2e__/中的每个应用程序都有一个对应的yarn android:<name>脚本。检查apps/router-e2e/package.json是否有可用的脚本。如果应用程序已构建,请重新启动它: 要查找任何已安装应用程序的包名称:转储视图层次结构
这将返回每个 UI 元素的 XML,包括:
text— 显示文本content-desc— 可访问性描述(对图标按钮有用)bounds— 位置为[left,top][right,bottom]clickable— 元素是否响应点击