Mobile Appium Test

Android UI automation testing using Appium with USB-connected real devices. Use when the user wants to run Appium tests on physical Android devices connected...

Security Scan

The skill is an instruction-only guide for running Appium/ADB on USB Android devices; its requirements and instructions align with that purpose and it does not request unrelated credentials or perform hidden installs.

Purpose & Capability

Name/description ask for Appium + ADB usage and the SKILL.md exclusively references those tools and operations; declared tool requirements (adb, appium) match the stated purpose.

Instruction Scope

Instructions are limited to ADB/Appium commands, device checks, and common test flows (install, screenshots, logs). One potentially sensitive recommendation is starting Appium with --relaxed-security, which broadens server capabilities and should be used intentionally. The guide does not attempt to read unrelated system files, env vars, or external endpoints beyond the local Appium server.

Install Mechanism

No install spec or code is included (instruction-only). The guide suggests installing Appium Doctor via npm for user setup, which is appropriate for the purpose and not enforced by the skill itself.

Credentials

No environment variables, credentials, or config paths are requested. All operations require local developer tools and device access only, which is proportional to device testing.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent presence or system-wide configuration changes. Be aware that an agent permitted to execute these instructions could run local adb/appium commands if given that capability.

Assessment

This appears to be a straightforward how-to for local Appium/ADB testing and is internally consistent. Before using: ensure adb and Appium are installed from official sources; only run app installs (adb install) and APKs you trust; avoid enabling --relaxed-security on a machine you don’t control or expose to untrusted networks; and be mindful that if you allow an agent to run these instructions autonomously it could execute adb/appium commands against devices connected to your host—only grant that capability if you understand and trust the agent.

Android UI automation testing using Appium with USB-connected real devices.

Prerequisites

Required tools (must be installed):

• ADB (Android Debug Bridge) - part of Android SDK
• Appium Server (v2.x recommended)
• Appium Doctor (npm install -g @appium/doctor)

Verify installation:

adb version
appium --version
appium doctor

Quick Reference

Device Connection

Goal	Command
List connected devices	adb devices
Get device info	adb shell getprop ro.build.version.release
Restart ADB server	adb kill-server && adb start-server
USB debug authorization	Check phone for authorization prompt

Appium Server

Goal	Command
Start Appium	appium --address 127.0.0.1 --port 4723
Start with relaxed security	appium --relaxed-security
Check Appium status	curl http://127.0.0.1:4723/status

Common Appium Operations

Goal	Endpoint/Action
Start session	POST /session with capabilities
Find element	POST /session/{id}/element
Click element	POST /session/{id}/element/{id}/click
Send keys	POST /session/{id}/element/{id}/value
Take screenshot	GET /session/{id}/screenshot
Get page source	GET /session/{id}/source
Quit session	DELETE /session/{id}

Typical Workflow

1. Verify Device Connection

adb devices

Ensure device shows device status (not unauthorized or offline).

2. Start Appium Server

appium --address 127.0.0.1 --port 4723 --relaxed-security

3. Run Test

Use desired capabilities for USB device:

{
  "platformName": "Android",
  "deviceName": "device",
  "udid": "<device-udid>",
  "app": "/path/to/app.apk",
  "automationName": "UiAutomator2",
  "noReset": true
}

4. Common Test Scenarios

• Install app: adb install app.apk
• Launch app: Appium appActivity capability
• Find element by ID: find_element("id", "com.example:id/button")
• Find element by text: find_element("xpath", "//*[@text='Submit']")
• Swipe: Appium touch action
• Get logs: adb logcat

Error Handling

Error	Cause	Solution
device not found	USB connection issue	Check adb devices, restart ADB server
unauthorized	USB debug not authorized	Unlock phone, authorize the computer
no such element	Element not found	Use find_elements with wait, check page source
session not created	Capability mismatch	Verify UDID, platform version, app path

Notes

• Always use UdID from adb devices for real device testing
• Use UiAutomator2 as automation engine for Android
• noReset: true preserves app state between sessions
• For WiFi debugging: adb tcpip 5555 then adb connect <IP>:5555