Low Level Android Automation With ADB
summary
Chooses ADB over Appium for a non‑GUI Android service because it runs faster, touches fewer layers and is more reliable; builds a tiny automation stack in Python using subprocess plus three helpers (adb_command, adb_shell, adb_push/pull) in about 5 minutes. Uses pm install/uninstall, monkey to launch, dumpsys and logcat to check logcat for activity and verify behavior, screencap + pull to collect evidence, and remote ADB server to target devices in an internal cloud. The scripted scenario installs the APK, confirms activity in logs, captures a screenshot and succeeds.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:02About Tomer Cohen
- 6:07What is Low Level Automation
- 8:52Layered Architecture
- 9:26Debug Bridge
- 10:13Architecture
- 11:21Demo
- 13:07ADB Architecture
- 15:04Live Demo
- 18:48Basic Infrastructure
- 20:13Scenario
- 20:50Implementation
related talks
15mAutomate Any App with Appium #AAAA
57mAutomating Android: Command line controls
52mBuilding an Advanced Automation Solution Based on Appium
43mTracing the path of Appium command
57mAppium: Automation for Apps
19mAutomation for mobile games with Appium & AltUnity Tester
18mHow AI Can Act as Top Layer of Appium Automation Runs
44mAppium Dockerization: From Scratch to Advanced Implementation
