AI 助理
备案控制台
开发者社区 开发与运维 文章 正文

Appium日志分析总结Appium工作原理

2024-01-19 93
版权
版权声明：
本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《 阿里云开发者社区用户服务协议》和 《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写 侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
本文涉及的产品
阿里云百炼推荐规格 ADB PostgreSQL，4核16GB 100GB 1个月
推荐场景：
构建的企业专属Chatbot
日志服务 SLS，月写入数据量 50GB 1个月
简介： Appium日志分析总结Appium工作原理

一、写在前面


本文分析的 Appium Server 运行日志基于 Appium2.0 版本，以 Android 平台为例。

官方参考文档：

https://github.com/Appium/Appium-uiautomator2-server/wiki

https://github.com/appium/appium-uiautomator2-server/wiki/How-Server-module-works

https://github.com/appium/appium-uiautomator2-server

image.png


二、日志分析


# 启动Appium Server，并加载uiautomator2 driver
[Appium] Welcome to Appium v2.2.2
[Appium] Attempting to load driver uiautomator2...
[Appium] Requiring driver at C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver
# Appium 已成功启动，使用4723端口监听来自客户端的http请求
[Appium] Appium REST http interface listener started on http://0.0.0.0:4723
[Appium] You can provide the following URLs in your client code to connect to this server:
[Appium]        http://192.168.2.108:4723/
[Appium]        http://169.254.53.195:4723/
[Appium]        http://169.254.122.200:4723/
[Appium]        http://127.0.0.1:4723/ (only accessible from the same host)
# Appium的可用驱动
[Appium] Available drivers:
[Appium]   - uiautomator2@2.34.1 (automationName 'UiAutomator2')
[Appium] No plugins have been installed. Use the "Appium plugin" command to install the one(s) you want to use.
# 客户端发起get请求获取当前会话的信息，以避免重复创建相同的会话
[HTTP] --> GET /sessions
[HTTP] {}
# Server调用AppiumDriver获取会话信息（AppiumDriver充当客户端和移动设备之间的桥梁，它是一个抽象类，具体实现取决于目标移动平台。比如，对于 Android 应用，可以使用 AndroidDriver；对于 iOS 应用，可以使用 IOSDriver。）
[AppiumDriver@6243] Calling AppiumDriver.getSessions() with args: []
[AppiumDriver@6243] Responding to client with driver.getSessions() result: []
[HTTP] <-- GET /sessions 304 14 ms - -
# Request idempotency key 用于确保请求的幂等性,如果创建会话的请求由于某些原因失败，系统可以使用相同的 idempotency key 重试该请求，而无需担心产生意外的副作用。
[HTTP]
[HTTP] Request idempotency key: 863f3b69-42b2-4563-9f91-500d0e25b038
# Appium 客户端发起post请求，创建一个新的会话（请求主体中，指定了自动化引擎为 "uiautomator2"等信息）
[HTTP] --> POST /session
[HTTP] {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"Appium:automationName":"uiautomator2","platformName":"Android","Appium:deviceName":"127.0.0.1:62001","Appium:app":"D:\\resources\\imooc.apk"}}}
[AppiumDriver@6243] Calling AppiumDriver.createSession() with args: [null,null,{"firstMatch":[{}],"alwaysMatch":{"Appium:automationName":"uiautomator2","platformName":"Android","Appium:deviceName":"127.0.0.1:62001","Appium:app":"D:\\resources\\imooc.apk"}}]
[AppiumDriver@6243] Event 'newSessionRequested' logged at 1700836362705 (22:32:42 GMT+0800 (中国标准时间))
# 根据automationName='uiautomator2',指定使用的驱动为Appium-uiautomator2-driver
[Appium] Attempting to find matching driver for automationName 'uiautomator2' and platformName 'Android'
[Appium] The 'uiautomator2' driver was installed and matched caps.
[Appium] Will require it at C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver
[Appium] Requiring driver at C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver
# 成功创建AndroidUiautomator2Driver会话，session id: 05578622-580d-43b4-9fbf-9fe9411f9f4b,注意这个session id 是维持Appium Server 与 Appium Client 之间的会话关系，当下次客户端发出请求时就会自带session id为唯一标识。
[AppiumDriver@6243] Appium v2.2.2 creating new AndroidUiautomator2Driver (v2.34.1) session
[AppiumDriver@6243] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
[AppiumDriver@6243] Appium's BaseDriver version is 9.4.2
[AppiumDriver@6243] AndroidUiautomator2Driver's BaseDriver version is 9.4.2
[AndroidUiautomator2Driver@f1aa] Creating session with W3C capabilities: {
[AndroidUiautomator2Driver@f1aa]   "alwaysMatch": {
[AndroidUiautomator2Driver@f1aa]     "platformName": "Android",
[AndroidUiautomator2Driver@f1aa]     "Appium:automationName": "uiautomator2",
[AndroidUiautomator2Driver@f1aa]     "Appium:deviceName": "127.0.0.1:62001",
[AndroidUiautomator2Driver@f1aa]     "Appium:app": "D:\\resources\\imooc.apk"
[AndroidUiautomator2Driver@f1aa]   },
[AndroidUiautomator2Driver@f1aa]   "firstMatch": [
[AndroidUiautomator2Driver@f1aa]     {}
[AndroidUiautomator2Driver@f1aa]   ]
[AndroidUiautomator2Driver@f1aa] }
[AndroidUiautomator2Driver@f1aa (05578622)] Session created with session id: 05578622-580d-43b4-9fbf-9fe9411f9f4b
# 使用adb命令，将imooc.apk推送至Android设备（adb是一个C/S架构的应用程序，由三部分组成：adb客户端、adb服务端、adbd守护进程。adb客户端和adb服务端运行开发者的计算机上。当启动某个 adb 客户端时，该客户端会先检查是否有 adb 服务器进程已在运行。如果没有，它会启动服务器进程。服务器在启动后会与本地 TCP 端口 5037 绑定，并监听 adb 客户端发出的命令。adbd作为后台守护进程运行在Android设备上，Andorid设备通过usb或远程方式连接计算机。adb客户端将指令发送至adb服务端，adb服务端将来自客户端的指令传递给Android设备上的adbd，从而完成Android设备的交互和调试。）
[BaseDriver] Using local app 'D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk'
[AndroidUiautomator2Driver@f1aa (05578622)] Checking whether app is actually present
[ADB] Found 3 'build-tools' folders under 'D:\ProgramFiles\Android\android-sdk' (newest first):
[ADB]     D:\ProgramFiles\Android\android-sdk\build-tools\30.0.0-preview
[ADB]     D:\ProgramFiles\Android\android-sdk\build-tools\29.0.3
[ADB]     D:\ProgramFiles\Android\android-sdk\build-tools\26.0.0-preview
[ADB] Using 'adb.exe' from 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 start-server'
[AndroidDriver] Retrieving device list
[ADB] Trying to find connected Android devices
[ADB] Getting connected devices
[ADB] Connected devices: [{"udid":"127.0.0.1:62001","state":"device"}]
[AndroidDriver] Using device: 127.0.0.1:62001
[ADB] Using 'adb.exe' from 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 start-server'
[ADB] Setting device id to 127.0.0.1:62001
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell getprop ro.build.version.sdk'
[ADB] Current device property 'ro.build.version.sdk': 25
[ADB] Device API level: 25
[AndroidDriver] Parsing package and activity from app manifest
[ADB] Package name: 'cn.com.open.mooc'
[ADB] Main activity name: 'cn.com.open.mooc.index.splash.MCSplashActivity'
[AndroidDriver] Parsed package and activity are: cn.com.open.mooc/cn.com.open.mooc.index.splash.MCSplashActivity
# 使用adb命令，将settings_apk-debug.apk安装至Android设备（io.Appium.settings 是 Appium 提供的一个用于配置测试会话的应用程序，可以模拟网络连接、定位服务等测试环境）
[AndroidDriver] Pushing settings apk to device...
[ADB] Getting package info for 'io.Appium.settings'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell dumpsys package io.Appium.settings'
[ADB] App 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\io.Appium.settings\apks\settings_apk-debug.apk' is not installed
[ADB] Installing 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\io.Appium.settings\apks\settings_apk-debug.apk'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 help'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 features'
[ADB] The application at 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\io.Appium.settings\apks\settings_apk-debug.apk' will not be cached, because the device under test has confirmed the support of streamed installs
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 install -g C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\io.Appium.settings\apks\settings_apk-debug.apk'
[ADB] The installation of 'settings_apk-debug.apk' took 1382ms
[ADB] Install command stdout: Performing Streamed Install
[ADB] Success
[ADB] Getting IDs of all 'io.Appium.settings' processes
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:62001 shell 'pgrep --help; echo $?''
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:62001 shell 'pgrep ^Appium\\.settings$ || pgrep ^io\\.Appium\\.setti$''
[ADB] Getting IDs of all 'io.Appium.settings' processes
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:62001 shell 'pgrep ^Appium\\.settings$ || pgrep ^io\\.Appium\\.setti$''
# 启动Appium Settings app
[ADB] Starting Appium Settings app
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell am start -n io.Appium.settings/.Settings -a android.intent.action.MAIN -c android.intent.category.LAUNCHER'
[ADB] Getting IDs of all 'io.Appium.settings' processes
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:62001 shell 'pgrep ^Appium\\.settings$ || pgrep ^io\\.Appium\\.setti$''
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell appops set io.Appium.settings android:mock_location allow'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:62001 shell "[ -e '/data/local/tmp/mock_apps.json' ] && echo __PASS__"'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell cat /data/local/tmp/mock_apps.json'
[Logcat] Starting logs capture with command: D:\\ProgramFiles\\Android\\android-sdk\\platform-tools\\adb.exe -P 5037 -s 127.0.0.1\:62001 logcat -v threadtime
# 将UiAutomator2 Server的端口 6790 绑定至本地端口 8200（UiAutomator2 Server运行在Android设备上，将 UiAutomator2 Server的端口 6790 绑定至本地端口 8200，可以使Appium在本地使用该端口上监听并接收从UiAutomator2 Server发出的请求）
[AndroidUiautomator2Driver@f1aa (05578622)] Forwarding UiAutomator2 Server port 6790 to local port 8200
[ADB] Forwarding system: 8200 to device: 6790
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 forward tcp:8200 tcp:6790'
# 使用 apksigner 工具验证Appium-uiautomator2-server-v5.12.16.apk和Appium-uiautomator2-server-debug-androidTest.apk的签名证书，确保其完整性和可信度
[ADB] Checking app cert for C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\Appium-uiautomator2-server\apks\Appium-uiautomator2-server-v5.12.16.apk
[ADB] Checking app cert for C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\Appium-uiautomator2-server\apks\Appium-uiautomator2-server-debug-androidTest.apk
[ADB] Using 'apksigner.jar' from 'D:\ProgramFiles\Android\android-sdk\build-tools\30.0.0-preview\lib\apksigner.jar'
[ADB] Starting apksigner: 'C:\\Program Files\\Java\\jdk-21\\bin\\java.exe' -Xmx1024M -Xss1m -jar D:\\ProgramFiles\\Android\\android-sdk\\build-tools\\30.0.0-preview\\lib\\apksigner.jar verify --print-certs C:\\Users\\xyouw\\.Appium\\node_modules\\Appium-uiautomator2-driver\\node_modules\\Appium-uiautomator2-server\\apks\\Appium-uiautomator2-server-debug-androidTest.apk
[ADB] Starting apksigner: 'C:\\Program Files\\Java\\jdk-21\\bin\\java.exe' -Xmx1024M -Xss1m -jar D:\\ProgramFiles\\Android\\android-sdk\\build-tools\\30.0.0-preview\\lib\\apksigner.jar verify --print-certs C:\\Users\\xyouw\\.Appium\\node_modules\\Appium-uiautomator2-driver\\node_modules\\Appium-uiautomator2-server\\apks\\Appium-uiautomator2-server-v5.12.16.apk
[ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[ADB]
[ADB] sha256 hash did match for 'Appium-uiautomator2-server-debug-androidTest.apk'
[ADB] 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\Appium-uiautomator2-server\apks\Appium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificate
# 检查 appium-uiautomator2-server端的两个apk的安装状态（Appium-uiautomator2-server-v5.12.16.apk已安装，负责在设备上执行相应的 UI 自动化操作；Appium-uiautomator2-server-debug-androidTest.apk已安装，它包含一个单独的测试来启动server。官方文档说明：https://github.com/appium/appium-uiautomator2-server/wiki/How-Server-module-works）
[ADB] Getting install status for io.Appium.uiautomator2.server.test
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell pm path io.Appium.uiautomator2.server.test'
[ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[ADB]
[ADB] sha256 hash did match for 'Appium-uiautomator2-server-v5.12.16.apk'
[ADB] 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\Appium-uiautomator2-server\apks\Appium-uiautomator2-server-v5.12.16.apk' is signed with the default certificate
[ADB] Getting package info for 'io.Appium.uiautomator2.server'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell dumpsys package io.Appium.uiautomator2.server'
[ADB] The version name of the installed 'io.Appium.uiautomator2.server' is greater or equal to the application version name ('5.12.16' >= '5.12.16')
[ADB] 'io.Appium.uiautomator2.server.test' is installed
[AndroidUiautomator2Driver@f1aa (05578622)] Server packages status: [{"wasSigned":true,"installState":"sameVersionInstalled","appPath":"C:\\Users\\xyouw\\.Appium\\node_modules\\Appium-uiautomator2-driver\\node_modules\\Appium-uiautomator2-server\\apks\\Appium-uiautomator2-server-v5.12.16.apk","appId":"io.Appium.uiautomator2.server"},{"wasSigned":true,"installState":"sameVersionInstalled","appPath":"C:\\Users\\xyouw\\.Appium\\node_modules\\Appium-uiautomator2-driver\\node_modules\\Appium-uiautomator2-server\\apks\\Appium-uiautomator2-server-debug-androidTest.apk","appId":"io.Appium.uiautomator2.server.test"}]
[AndroidUiautomator2Driver@f1aa (05578622)] Server packages are not going to be (re)installed
[AndroidUiautomator2Driver@f1aa (05578622)] Waiting up to 30000ms for services to be available
# 检查androidx.test.runner.AndroidJUnitRunner是否可用，它用于启动Appium-uiautomator2-server（官方文档：https://github.com/appium/appium-uiautomator2-server）
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell pm list instrumentation'
[AndroidUiautomator2Driver@f1aa (05578622)] Instrumentation target 'io.Appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
# 将Appium的这3个apk添加至 Doze 白名单，确保省电模式下可用
[ADB] Adding packages ["io.Appium.settings","io.Appium.uiautomator2.server","io.Appium.uiautomator2.server.test"] to Doze whitelist
[ADB] Got the following command chunks to execute: [["dumpsys","deviceidle","whitelist","+io.Appium.settings",";","dumpsys","deviceidle","whitelist","+io.Appium.uiautomator2.server",";","dumpsys","deviceidle","whitelist","+io.Appium.uiautomator2.server.test",";"]]
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell dumpsys deviceidle whitelist +io.Appium.settings ; dumpsys deviceidle whitelist +io.Appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.Appium.uiautomator2.server.test ;'
# 检查imooc.apk的签名证书，确保其完整性和可信度
[ADB] Checking app cert for D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk
[ADB] Starting apksigner: 'C:\\Program Files\\Java\\jdk-21\\bin\\java.exe' -Xmx1024M -Xss1m -jar D:\\ProgramFiles\\Android\\android-sdk\\build-tools\\30.0.0-preview\\lib\\apksigner.jar verify --print-certs D:\\resources\\imooc.apk
[ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[ADB]
[ADB] sha256 hash did match for 'imooc.apk'
[ADB] 'D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk' is signed with the default certificate
# 安装imooc.apk
[ADB] Getting package info for 'cn.com.open.mooc'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell dumpsys package cn.com.open.mooc'
[ADB] App 'D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk' is not installed
[ADB] Installing 'D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk'
[ADB] The application at 'D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk' will not be cached, because the device under test has confirmed the support of streamed installs
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 install D:\BaiduSyncdisk\xyouwen-workspace\ddautotest\resources\imooc.apk'
[ADB] The installation of 'imooc.apk' took 3258ms
[ADB] Install command stdout: Performing Streamed Install
[ADB] Success
# Android Uiautomator2 驱动执行浅层清理（shallow cleanup）,检查是否存在不再需要的测试会话（obsolete sessions）
[AndroidUiautomator2Driver@f1aa (05578622)] Performing shallow cleanup of automation leftovers
[AndroidUiautomator2Driver@f1aa (05578622)] No obsolete sessions have been detected (socket hang up)
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell am force-stop io.Appium.uiautomator2.server.test'
# AndroidUiautomator2Driver发出指令，启动UIAutomator2 server
[AndroidUiautomator2Driver@f1aa (05578622)] Starting UIAutomator2 server 5.12.16
[AndroidUiautomator2Driver@f1aa (05578622)] Using UIAutomator2 server from 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\Appium-uiautomator2-server\apks\Appium-uiautomator2-server-v5.12.16.apk' and test from 'C:\Users\xyouw\.Appium\node_modules\Appium-uiautomator2-driver\node_modules\Appium-uiautomator2-server\apks\Appium-uiautomator2-server-debug-androidTest.apk'
[AndroidUiautomator2Driver@f1aa (05578622)] Waiting up to 30000ms for UiAutomator2 to be online...
# 通过 ADB 创建了一个子进程，这条命令是真正启动UIAutomator2 server的命令（官方文档：https://github.com/appium/appium-uiautomator2-server， 启动server的命令是：adb shell am instrument -w io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner）
[ADB] Creating ADB subprocess with args: ["-P","5037","-s","127.0.0.1:62001","shell","am","instrument","-w","-e","disableAnalytics","true","io.Appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
# AndroidUiautomator2Driver 尝试通过 HTTP 请求检查 UiAutomator2 Server 的状态，UiAutomator2 server 初始化耗时3051ms
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/status' to command name 'getStatus'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] socket hang up
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/status' to command name 'getStatus'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] socket hang up
[Instrumentation] io.Appium.uiautomator2.server.test.AppiumUiAutomator2Server:
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/status' to command name 'getStatus'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] socket hang up
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/status' to command name 'getStatus'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"None","value":{"message":"UiAutomator2 Server is ready to accept commands","ready":true}}
[AndroidUiautomator2Driver@f1aa (05578622)] The initialization of the instrumentation process took 3051ms
# AndroidUiautomator2Driver将来自客户端的请求（POST /session），代理至 UiAutomator2 Server
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/session' to command name 'createSession'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [POST /session] to [POST http://127.0.0.1:8200/session] with body: {"capabilities":{"firstMatch":[{"platformName":"Android","automationName":"uiautomator2","deviceName":"127.0.0.1:62001","app":"D:\\resources\\imooc.apk","platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","automationName":"uiautomator2","deviceName":"127.0.0.1:62001","app":"D:\\resources\\imooc.apk"},"deviceUDID":"127.0.0.1:62001","appPackage":"cn.com.open.mooc"}],"alwaysMatch":{}}}
# UiAutomator2 Server成功创建会话并返回相信信息，sessionId":"b339ede2-f5e2-4b68-b794-512addf83270，这个 sessionId 用来维护 AndroidUiautomator2Driver 与 UiAutomator2 Server之间的会话关系
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":{"capabilities":{"firstMatch":[{"platformName":"Android","automationName":"uiautomator2","deviceName":"127.0.0.1:62001","app":"D:\\resources\\imooc.apk","platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","automationName":"uiautomator2","deviceName":"127.0.0.1:62001","app":"D:\\resources\\imooc.apk"},"deviceUDID":"127.0.0.1:62001","appPackage":"cn.com.open.mooc"}],"alwaysMatch":{}},"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270"}}
[AndroidUiautomator2Driver@f1aa (05578622)] Determined the downstream protocol as 'W3C'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /Appium/device/pixel_ratio] to [GET http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/Appium/device/pixel_ratio] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/Appium/device/system_bars' to command name 'getSystemBars'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /Appium/device/system_bars] to [GET http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/Appium/device/system_bars] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/window/current/size' to command name 'getWindowSize'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /window/current/size] to [GET http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/window/current/size] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /Appium/device/info] to [GET http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/Appium/device/info] with no body
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell dumpsys window'
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":2}
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":{"statusBar":48}}
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":{"height":1920,"width":1080}}
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":{"androidId":"10cb49a7464148e8","apiVersion":"25","bluetooth":{"state":"OFF"},"brand":"HUAWEI","carrierName":"CMCC","displayDensity":320,"locale":"zh_CN","manufacturer":"HUAWEI","model":"TAS-AN00","networks":[{"capabilities":{"SSID":null,"linkDownBandwidthKbps":1048576,"linkUpstreamBandwidthKbps":1048576,"networkCapabilities":"NET_CAPABILITY_NOT_METERED,NET_CAPABILITY_NOT_RESTRICTED,NET_CAPABILITY_NOT_VPN,NET_CAPABILITY_NOT_ROAMING,NET_CAPABILITY_INTERNET,NET_CAPABILITY_TRUSTED,NET_CAPABILITY_VALIDATED","signalStrength":-55,"transportTypes":"TRANSPORT_WIFI"},"detailedState":"CONNECTED","extraInfo":"\"WiredSSID\"","isAvailable":true,"isConnected":true,"isFailover":false,"isRoaming":false,"state":"CONNECTED","subtype":0,"subtypeName":"","type":1,"typeName":"WIFI"}],"platformVersion":"7.1.2","realDisplaySize":"1080x1920","timeZone":"Asia/Shanghai"}}
# AndroidUiautomator2Driver调用adb命令启动被测应用并等待特定页面“cn.com.open.mooc/cn.com.open.mooc.index.splash.MCSplashActivity”被加载
[AndroidDriver] Screen already unlocked, doing nothing
[AndroidUiautomator2Driver@f1aa (05578622)] Starting 'cn.com.open.mooc/cn.com.open.mooc.index.splash.MCSplashActivity and waiting for 'cn.com.open.mooc/cn.com.open.mooc.index.splash.MCSplashActivity'
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell am start -W -n cn.com.open.mooc/cn.com.open.mooc.index.splash.MCSplashActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000'
[ADB] Waiting up to 20000ms for activity matching pkg: 'cn.com.open.mooc' and activity: 'cn.com.open.mooc.index.splash.MCSplashActivity' to be focused
[ADB] Possible activities, to be checked: 'cn.com.open.mooc.index.splash.MCSplashActivity', 'cn.com.open.mooc.cn.com.open.mooc.index.splash.MCSplashActivity'
[ADB] Getting focused package and activity
[ADB] Running 'D:\ProgramFiles\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:62001 shell dumpsys window windows'
[ADB] Found package: 'cn.com.open.mooc' and fully qualified activity name : 'cn.com.open.mooc.index.splash.MCSplashActivity'
[AppiumDriver@6243] New AndroidUiautomator2Driver session created successfully, session 05578622-580d-43b4-9fbf-9fe9411f9f4b added to master session list
[AppiumDriver@6243] Event 'newSessionStarted' logged at 1700836380436 (22:33:00 GMT+0800 (中国标准时间))
[AndroidUiautomator2Driver@f1aa (05578622)] Cached the protocol value 'W3C' for the new session 05578622-580d-43b4-9fbf-9fe9411f9f4b
# 将响应结果返回给客户端
[AndroidUiautomator2Driver@f1aa (05578622)] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"Android","automationName":"uiautomator2","deviceName":"127.0.0.1:62001","app":"D:\\resources\\imooc.apk","platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","automationName":"uiautomator2","deviceName":"127.0.0.1:62001","app":"D:\\resources\\imooc.apk"},"deviceUDID":"127.0.0.1:62001","appPackage":"cn.com.open.mooc","pixelRatio":"2","statBarHeight":48,"viewportRect":{"left":0,"top":48,"width":1080,"height":1872},"deviceApiLevel":25,"platformVersion":"7.1.2","deviceManufacturer":"HUAWEI","deviceModel":"TAS-AN00","deviceScreenSize":"1080x1920","deviceScreenDensity":320}}
[HTTP] <-- POST /session 200 17736 ms - 944
# 客户端发送“获取窗口尺寸”的请求，AndroidUiautomator2Driver携带表示与客户端关系的sessionid，将请求代理至UIAutomator2 Server
[HTTP]
[HTTP] --> GET /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/window/rect
[HTTP] {}
[AndroidUiautomator2Driver@f1aa (05578622)] Calling AppiumDriver.getWindowRect() with args: ["05578622-580d-43b4-9fbf-9fe9411f9f4b"]
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/window/current/size' to command name 'getWindowSize'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [GET /window/current/size] to [GET http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/window/current/size] with no body
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":{"height":1920,"width":1080}}
# UIAutomator2 Server将响应结果，返回给AndroidUiautomator2Driver
[AndroidUiautomator2Driver@f1aa (05578622)] Responding to client with driver.getWindowRect() result: {"width":1080,"height":1920,"x":0,"y":0}
[HTTP] <-- GET /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/window/rect 200 14 ms - 50
# 客户端发送“滑动页面”请求，AndroidUiautomator2Driver携带表示与客户端关系的sessionid，将请求代理至UIAutomator2 Server
[HTTP]
[HTTP] --> POST /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/actions
[HTTP] {"actions":[{"type":"pointer","parameters":{"pointerType":"touch"},"id":"touch","actions":[{"type":"pointerMove","duration":250,"x":810,"y":960,"origin":"viewport"},{"type":"pointerDown","duration":0,"button":0},{"type":"pointerMove","duration":500,"x":54,"y":960,"origin":"viewport"},{"type":"pointerUp","duration":0,"button":0}]}]}
[AndroidUiautomator2Driver@f1aa (05578622)] Calling AppiumDriver.performActions() with args: [[{"type":"pointer","parameters":{"pointerType":"touch"},"id":"touch","actions":[{"type":"pointerMove","duration":250,"x":810,"y":960,"origin":"viewport"},{"type":"pointerDown","duration":0,"button":0},{"type":"pointerMove","duration":500,"x":54,"y":960,"origin":"viewport"},{"type":"pointerUp","duration":0,"button":0}]}],"05578622-580d-43b4-9fbf-9fe9411f9f4b"]
[AndroidUiautomator2Driver@f1aa (05578622)] Received the following W3C actions: [
[AndroidUiautomator2Driver@f1aa (05578622)]   {
[AndroidUiautomator2Driver@f1aa (05578622)]     "type": "pointer",
[AndroidUiautomator2Driver@f1aa (05578622)]     "parameters": {
[AndroidUiautomator2Driver@f1aa (05578622)]       "pointerType": "touch"
[AndroidUiautomator2Driver@f1aa (05578622)]     },
[AndroidUiautomator2Driver@f1aa (05578622)]     "id": "touch",
[AndroidUiautomator2Driver@f1aa (05578622)]     "actions": [
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerMove",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 250,
[AndroidUiautomator2Driver@f1aa (05578622)]         "x": 810,
[AndroidUiautomator2Driver@f1aa (05578622)]         "y": 960,
[AndroidUiautomator2Driver@f1aa (05578622)]         "origin": "viewport"
[AndroidUiautomator2Driver@f1aa (05578622)]       },
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerDown",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 0,
[AndroidUiautomator2Driver@f1aa (05578622)]         "button": 0
[AndroidUiautomator2Driver@f1aa (05578622)]       },
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerMove",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 500,
[AndroidUiautomator2Driver@f1aa (05578622)]         "x": 54,
[AndroidUiautomator2Driver@f1aa (05578622)]         "y": 960,
[AndroidUiautomator2Driver@f1aa (05578622)]         "origin": "viewport"
[AndroidUiautomator2Driver@f1aa (05578622)]       },
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerUp",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 0,
[AndroidUiautomator2Driver@f1aa (05578622)]         "button": 0
[AndroidUiautomator2Driver@f1aa (05578622)]       }
[AndroidUiautomator2Driver@f1aa (05578622)]     ]
[AndroidUiautomator2Driver@f1aa (05578622)]   }
[AndroidUiautomator2Driver@f1aa (05578622)] ]
[AndroidUiautomator2Driver@f1aa (05578622)] Preprocessed actions: [
[AndroidUiautomator2Driver@f1aa (05578622)]   {
[AndroidUiautomator2Driver@f1aa (05578622)]     "type": "pointer",
[AndroidUiautomator2Driver@f1aa (05578622)]     "parameters": {
[AndroidUiautomator2Driver@f1aa (05578622)]       "pointerType": "touch"
[AndroidUiautomator2Driver@f1aa (05578622)]     },
[AndroidUiautomator2Driver@f1aa (05578622)]     "id": "touch",
[AndroidUiautomator2Driver@f1aa (05578622)]     "actions": [
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerMove",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 250,
[AndroidUiautomator2Driver@f1aa (05578622)]         "x": 810,
[AndroidUiautomator2Driver@f1aa (05578622)]         "y": 960,
[AndroidUiautomator2Driver@f1aa (05578622)]         "origin": "viewport"
[AndroidUiautomator2Driver@f1aa (05578622)]       },
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerDown",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 0,
[AndroidUiautomator2Driver@f1aa (05578622)]         "button": 0
[AndroidUiautomator2Driver@f1aa (05578622)]       },
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerMove",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 500,
[AndroidUiautomator2Driver@f1aa (05578622)]         "x": 54,
[AndroidUiautomator2Driver@f1aa (05578622)]         "y": 960,
[AndroidUiautomator2Driver@f1aa (05578622)]         "origin": "viewport"
[AndroidUiautomator2Driver@f1aa (05578622)]       },
[AndroidUiautomator2Driver@f1aa (05578622)]       {
[AndroidUiautomator2Driver@f1aa (05578622)]         "type": "pointerUp",
[AndroidUiautomator2Driver@f1aa (05578622)]         "duration": 0,
[AndroidUiautomator2Driver@f1aa (05578622)]         "button": 0
[AndroidUiautomator2Driver@f1aa (05578622)]       }
[AndroidUiautomator2Driver@f1aa (05578622)]     ]
[AndroidUiautomator2Driver@f1aa (05578622)]   }
[AndroidUiautomator2Driver@f1aa (05578622)] ]
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/actions' to command name 'performActions'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [POST /actions] to [POST http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/actions] with body: {"actions":[{"type":"pointer","parameters":{"pointerType":"touch"},"id":"touch","actions":[{"type":"pointerMove","duration":250,"x":810,"y":960,"origin":"viewport"},{"type":"pointerDown","duration":0,"button":0},{"type":"pointerMove","duration":500,"x":54,"y":960,"origin":"viewport"},{"type":"pointerUp","duration":0,"button":0}]}]}
# UIAutomator2 Server将响应结果，返回给AndroidUiautomator2Driver
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":null}
[AndroidUiautomator2Driver@f1aa (05578622)] Responding to client with driver.performActions() result: null
[HTTP] <-- POST /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/actions 200 876 ms - 14
# 客户端发送“定位元素”的请求，AndroidUiautomator2Driver携带表示与客户端关系的sessionid，将请求代理至UIAutomator2 Server
[HTTP]
[HTTP] --> POST /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/element
[HTTP] {"using":"id","value":"cn.com.open.mooc:id/viewpager"}
[AndroidUiautomator2Driver@f1aa (05578622)] Calling AppiumDriver.findElement() with args: ["id","cn.com.open.mooc:id/viewpager","05578622-580d-43b4-9fbf-9fe9411f9f4b"]
[AndroidUiautomator2Driver@f1aa (05578622)] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[AndroidUiautomator2Driver@f1aa (05578622)] Waiting up to 0 ms for condition
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/element' to command name 'findElement'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [POST /element] to [POST http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/element] with body: {"strategy":"id","selector":"cn.com.open.mooc:id/viewpager","context":"","multiple":false}
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":{"ELEMENT":"00000000-0000-0006-7fff-ffff00000003","element-6066-11e4-a52e-4f735466cecf":"00000000-0000-0006-7fff-ffff00000003"}}
# UIAutomator2 Server将响应结果，返回给AndroidUiautomator2Driver
[AndroidUiautomator2Driver@f1aa (05578622)] Responding to client with driver.findElement() result: {"element-6066-11e4-a52e-4f735466cecf":"00000000-0000-0006-7fff-ffff00000003","ELEMENT":"00000000-0000-0006-7fff-ffff00000003"}
[HTTP] <-- POST /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/element 200 123 ms - 137
# 客户端发送“点击元素”的请求，AndroidUiautomator2Driver携带表示与客户端关系的sessionid，将请求代理至UIAutomator2 Server
[HTTP]
[HTTP] --> POST /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/element/00000000-0000-0006-7fff-ffff00000003/click
[HTTP] {}
[AndroidUiautomator2Driver@f1aa (05578622)] Calling AppiumDriver.click() with args: ["00000000-0000-0006-7fff-ffff00000003","05578622-580d-43b4-9fbf-9fe9411f9f4b"]
[AndroidUiautomator2Driver@f1aa (05578622)] Matched '/element/00000000-0000-0006-7fff-ffff00000003/click' to command name 'click'
[AndroidUiautomator2Driver@f1aa (05578622)] Proxying [POST /element/00000000-0000-0006-7fff-ffff00000003/click] to [POST http://127.0.0.1:8200/session/b339ede2-f5e2-4b68-b794-512addf83270/element/00000000-0000-0006-7fff-ffff00000003/click] with body: {"element":"00000000-0000-0006-7fff-ffff00000003"}
# UIAutomator2 Server将响应结果，返回给AndroidUiautomator2Driver
[AndroidUiautomator2Driver@f1aa (05578622)] Got response with status 200: {"sessionId":"b339ede2-f5e2-4b68-b794-512addf83270","value":null}
[AndroidUiautomator2Driver@f1aa (05578622)] Responding to client with driver.click() result: null
[HTTP] <-- POST /session/05578622-580d-43b4-9fbf-9fe9411f9f4b/element/00000000-0000-0006-7fff-ffff00000003/click 200 19 ms - 14


三、总结


1、Appium 是一个 C/S 架构的自动化框架


几个核心概念：

1）Appium Client，它是使用 Appium API 编写和运行脚本的地方，比如我们使用 python 编写的自动化脚本。

2）Appium Server，它负责代理来自 Appium Client 的测试请求，调用 Google UIAutomator 与移动设备进行通信。Appium2.0 包括两个核心模块：

  • UIAutomator2 Driver模块，它负责与 Appium Client 通信创建会话，使用 adb 将 uiautomtor2 server 的两个 APK 包安装至 Android 设备上，启动 UIAutomator2 Server；
  • UIAutomator2 Server 模块，它负责处理来自 uiautomtor2 driver 的请求，调用调用 Google UIAutomator 与移动设备进行通信完成测试。


2、Appium2.0 的工作流程


1）Appium Server, 开启 4723 端口，监听来自 Appium Client 的请求；

2）Appium Client 发起 Post 请求，Appium Server 根据请求体中的 automationName 参数来启动相应的 driver（默认是 Appium-android-driver；如果 automationName 为 UIAutomator2，则启动 appium-uiautomator2-driver）；

3）AndroidUiautomator2Driver 创建 session，并将 session id 返回给 Appium Client，当下次 Client 发出请求时就会携带 session id 为唯一标识；

4）AndroidUiautomator2Driver 调用 adb 命令将相关 apk 文件推送至 Android 设备，包括：imooc.apk(测试包)、settings_apk-debug.apk（用于模拟网络连接、定位服务等测试环境）、appium-uiautomator2-server-v5.12.16.apk（负责执行自动化操作）appium-uiautomator2-server-debug-androidTest.apk（用于启动 uiautomator2 server），使用 apksigner 签名验证后，安装至设备

5）AndroidUiautomator2Driver 创建 adb 子进程，执行命令 adb shell am instrument -w io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner 启动 uiautomator2 server，并将 UiAutomator2 Server 的端口 6790 绑定至本地端口 8200，使 Appium Server 在 8200 端口上监听并接收从 UiAutomator2 Server 发出的请求；

6）AndroidUiautomator2Driver 携带 sessiond id 将来自客户端的请求，代理转至 UiAutomator2 Server，UiAutomator2 Server 创建 session 与 AndroidUiautomator2Driver 建立连接；

7）UiAutomator2 Server 调用底层的 Google UIAutomator V2 在 Android 设备上执行操作，并将响应结果返回给 AndroidUiautomator2Driver；

8）AndroidUiautomator2Driver 将响应结果，返回给 Appium Client，完成闭环。

文章标签：
日志服务
云原生数据仓库 AnalyticDB PostgreSQL版
监控
Android开发
Shell
测试技术
API
关键词：
日志服务原理
Appium工作原理
相关实践学习
日志服务之使用Nginx模式采集日志
本文介绍如何通过日志服务控制台创建Nginx模式的Logtail配置快速采集Nginx日志并进行多维度分析。
kind-tester
目录
相关文章
liuyunshengsir
|
6月前
|
SQL 关系型数据库 MySQL
Mysql 的binlog日志的原理【4月更文挑战第1天】
【4月更文挑战第1天】 MySQL的binlog（二进制日志）是一个记录数据库更改的日志文件，它主要用于复制和恢复操作。以下是binlog日志的工作原理的简要概述： **事件写入**：当MySQL服务器执行一个事务时，它会将该事务中所有对数据库的修改操作（如INSERT、UPDATE和DELETE等）记录为一个事件（event）。这些事件包含了修改操作的相关信息，如操作类型、涉及的表、修改的行等。
liuyunshengsir
140 1
阿里云开发者
|
6月前
|
存储 缓存 Java
浅析JAVA日志中的几则性能实践与原理解释
本篇文章通过几个技术点说明日志记录过程中的性能实践，计算机领域的性能往往都遵循着冰山法则，即你能看得见的、程序员能感知的只是其中的一小部分，还有大量的细节隐藏在冰山之下。
阿里云开发者
853 1
技术自由圈/原疯狂创客圈
|
1月前
|
SQL 存储 关系型数据库
美团面试：binlog、redo log、undo log的底层原理是什么？它们分别实现ACID的哪个特性？
老架构师尼恩在其读者交流群中分享了关于 MySQL 中 redo log、undo log 和 binlog 的面试题及其答案。这些问题涵盖了事务的 ACID 特性、日志的一致性问题、SQL 语句的执行流程等。尼恩详细解释了这些日志的作用、所在架构层级、日志形式、缓存机制以及写文件方式等内容。他还提供了多个面试题的详细解答，帮助读者系统化地掌握这些知识点，提升面试表现。此外，尼恩还推荐了《尼恩Java面试宝典PDF》和其他技术圣经系列PDF，帮助读者进一步巩固知识，实现“offer自由”。
技术自由圈/原疯狂创客圈
33 1
美团面试：binlog、redo log、undo log的底层原理是什么？它们分别实现ACID的哪个特性？
绿水长流*z
|
1月前
|
存储 缓存 关系型数据库
MySQL事务日志-Redo Log工作原理分析
事务的隔离性和原子性分别通过锁和事务日志实现，而持久性则依赖于事务日志中的`Redo Log`。在MySQL中，`Redo Log`确保已提交事务的数据能持久保存，即使系统崩溃也能通过重做日志恢复数据。其工作原理是记录数据在内存中的更改，待事务提交时写入磁盘。此外，`Redo Log`采用简单的物理日志格式和高效的顺序IO，确保快速提交。通过不同的落盘策略，可在性能和安全性之间做出权衡。
绿水长流*z
1636 14
古明地盆
|
2月前
|
存储 缓存 关系型数据库
redo log 原理解析
redo log 原理解析
古明地盆
40 0
redo log 原理解析
丰宝宝
|
2月前
|
设计模式 SQL 安全
PHP中的设计模式：单例模式的深入探索与实践在PHP的编程实践中，设计模式是解决常见软件设计问题的最佳实践。单例模式作为设计模式中的一种，确保一个类只有一个实例，并提供全局访问点，广泛应用于配置管理、日志记录和测试框架等场景。本文将深入探讨单例模式的原理、实现方式及其在PHP中的应用，帮助开发者更好地理解和运用这一设计模式。
在PHP开发中，单例模式通过确保类仅有一个实例并提供一个全局访问点，有效管理和访问共享资源。本文详细介绍了单例模式的概念、PHP实现方式及应用场景，并通过具体代码示例展示如何在PHP中实现单例模式以及如何在实际项目中正确使用它来优化代码结构和性能。
丰宝宝
46 2
最好zzz
|
2月前
|
存储 关系型数据库 MySQL
binlog、redolog、undo log底层原理及ACID特性实现分享
在数据库管理系统中，日志机制是确保数据一致性、完整性和可靠性的关键组件。MySQL数据库中的binlog、redolog和undolog作为其核心日志系统，各自扮演着不同但同样重要的角色。本文将深入探讨这三种日志的底层原理以及它们如何分别实现ACID（原子性、一致性、隔离性、持久性）特性的不同方面。
最好zzz
55 0
服务端技术栈
|
3月前
|
消息中间件 监控 搜索推荐
OpenFeign日志组件Logger原理与应用
该文章详细解释了如何在OpenFeign中配置并使用请求和响应的GZIP压缩功能。
服务端技术栈
125 2
萝卜丝丸子
|
4月前
|
运维 中间件 数据库
浅析JAVA日志中的性能实践与原理解释问题之元信息打印会导致性能急剧下降问题如何解决
浅析JAVA日志中的性能实践与原理解释问题之元信息打印会导致性能急剧下降问题如何解决
萝卜丝丸子
81 0
萝卜丝丸子
|
4月前
|
开发框架 缓存 Java
浅析JAVA日志中的性能实践与原理解释问题之"Garbage Free"技术的实现方式问题如何解决
浅析JAVA日志中的性能实践与原理解释问题之"Garbage Free"技术的实现方式问题如何解决
萝卜丝丸子
60 0

热门文章

最新文章

  • 1
    MQC功能测试大揭秘（2）- Appium环境搭建
  • 2
    Appium环境抢建(for web browser test)
  • 3
    Appium Studio 初体验（windows做ios自动化，录制appium脚本）
  • 4
    启动appium服务的2种方法(python脚本&cmd窗口)
  • 5
    appium自动化通过索引操作字段
  • 6
    Python+Appium2.0的APP自动化环境搭建
  • 7
    appium自动化属性使用一
  • 8
    Python + Appium 自动化操作微信入门看这一篇就够了
  • 9
    Python+Appium自动化测试(3)-编写自动化脚本
  • 10
    Appium 实践 | 让测试更快更稳更可靠：片状测试
  • 1
    编程日志01:个人网站更新用户头像
    50
  • 2
    编程日记02：个人站优化数据库和日志
    47
  • 3
    关于日志的清理
    61
  • 4
    Spring日志框架
    44
  • 5
    日志解析神器——Logstash中的Grok过滤器使用详解
    518
  • 6
    一文详解K8s环境下Job类日志采集方案
    175
  • 7
    logcat 只打印符合包名的log
    54
  • 8
    JNI Log 日志输出
    125
  • 9
    聊聊日志硬扫描，阿里 Log Scan 的设计与实践
    351
  • 10
    【Docker专栏】Docker日志管理与监控的最佳方法
    907

    • 相关课程

    更多
  • 基于MongoDB构建实时日志分析平台
  • 日志服务SLS实现云产品可观测
  • 日志服务 SLS 可观测数据分析平台介绍
  • 大数据知识图谱系列—基于ELK+Flink日志全观测最佳实践
  • 场景实践-基于阿里云Quick BI 对MOOC网站日志分析

    • 相关电子书

    更多
  • PostgresChina2018_赖思超_PostgreSQL10_hash索引的WAL日志修改版final
  • Kubernetes下日志实时采集、存储与计算实践
  • 日志数据采集与分析对接

    • 相关实验场景

    更多
  • 通过日志服务实现云资源OSS的安全审计
  • 如何将OSS数据导入至SLS中进行分析
  • 日志服务之使用Nginx模式采集日志
  • 日志服务之数据清洗与入湖
  • 揭秘如何通过日志服务实现个人敏感信息保护
    • 下一篇
    阿里云OSS设置跨域访问