莫问天涯路几重,轻衫侧帽且从容。这篇文章主要讲述appium启动运行log分析相关的知识,希望能为你提供帮助。
1、手动启动appium 服务
>
Launching Appium server with command: C:\Program Files (x86)\Appium\node.exe lib\server\main.js --address 127.0.0.1 --port 4723 --platform-name android --platform-version 22 --automation-name Appium --device-name "lge-nexus_4-005475cbccd279d4" --log-no-color>
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)>
info: Appium REST http interface listener started on 127.0.0.1:4723>
info: [debug] Non-default server args: {"address":"127.0.0.1","logNoColors":true,"deviceName":"lge-nexus_4-005475cbccd279d4","platformName":"Android","platformVersion":"22","automationName":"Appium"}>
info: Console LogLevel: debug
2、【TestScript】发送带json数据(Capabilities)的POST请求到/wd/hub/session来创建session>
info: -->
POST /wd/hub/session {"desiredCapabilities":{"appPackage":"com.edusoho.kuozhi","appActivity":"com.edusoho.kuozhi.KuozhiActivity","platformVersion":"5.1.1","automationName":"Appium","sessionOverride":true,"unicodeKeyboard":true,"platformName":"Android","deviceName":"red note3","resetKeyboard":false},"requiredCapabilities":{},"capabilities":{"desiredCapabilities":{"appPackage":"com.edusoho.kuozhi","appActivity":"com.edusoho.kuozhi.KuozhiActivity","platformVersion":"5.1.1","automationName":"Appium","sessionOverride":true,"unicodeKeyboard":true,"platformName":"Android","deviceName":"red note3","resetKeyboard":false},"requiredCapabilities":{}},"alwaysMatch":{"appPackage":"com.edusoho.kuozhi","appActivity":"com.edusoho.kuozhi.KuozhiActivity","platformVersion":"5.1.1","automationName":"Appium","sessionOverride":true,"unicodeKeyboard":true,"platformName":"Android","deviceName":"red note3","resetKeyboard":false},"firstMatch":[]}>
info: Client User-Agent string: Apache-HttpClient/4.5.2 (java/1.8.0_111)>
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : sessionOverride
初始化APP应用(没有获取到APP但是又Android包(取决于脚本配置的Capabilities参数))>
info: [debug] Didn‘t get app but did get Android package, will attempt to launch it on the device
新建appium session>
info: [debug] Creating new appium session 2ac0e18a-9120-4e90-a066-c6ddb1a1deaf
3、启动Android appium>
info: Starting android appium
检查JDK>
info: [debug] Getting Java version>
info: Java version is: 1.8.0_111
检查adb>
info: [debug] Checking whether adb is present>
info: [debug] Using adb from D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe>
warn: No app capability, can‘t parse package/activity
4、检查并连接设备device>
info: [debug] Using fast reset? true>
info: [debug] Preparing device for session>
info: [debug] Not checking whether app is present since we are assuming(假定) it‘s already on the device
检查设备信息>
info: Retrieving device>
info: [debug] Trying to find a connected android device
连接设备>
info: [debug] Getting connected devices...>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe devices
设备连接成功>
info: [debug] 1 device(s) connected>
info: Found device 5977b8a3>
info: [debug] Setting device id to 5977b8a3>
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 wait-for-device>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "echo ‘ready‘"
开启logcat>
info: [debug] Starting logcat capture>
info: [debug] Getting device API level
获取设备系统API版本>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "getprop ro.build.version.sdk">
info: [debug] Device is at API Level 22>
info: Device API level is: 22
获取设备系统语言>
info: [debug] Extracting strings for language: default>
info: [debug] Apk doesn‘t exist locally>
info: [debug] Could not get strings, but it looks like we had an old strings file anyway, so ignoring>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "rm -rf /data/local/tmp/strings.json"
5、检查APP安装和相关配置信息没有卸载已存在APP,因为appium服务器未设置--full-reset>
info: [debug] Not uninstalling app since server not started with --full-reset>
info: [debug] Skipping install since we launched with a package instead of an app path
把系统的4724端口映射到测试设备的4724端口>
info: [debug] Forwarding system:4724 to device:4724>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 forward tcp:4724 tcp:4724
把bootstrap.jar push到设备
>
info: [debug] Pushing appium bootstrap to device...>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 push "C:\\Program Files (x86)\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
让Unicode键盘可用
>
info: [debug] Enabling Unicode keyboard support
把unicode ime输入法 push 到设备中>
info: [debug] Pushing unicode ime to device...>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 install "C:\Program Files (x86)\Appium\node_modules\appium\build\unicode_ime_apk\UnicodeIME-debug.apk"
获取设备当前输入法
>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "settings get secure default_input_method"
取消设备当前输入法(百度输入法小米V6版)>
info: [debug] Unsetting IME ‘com.baidu.input_miv6/.ImeService‘
设置Unicode输入法为设备当前输入法>
info: [debug] Setting IME to ‘io.appium.android.ime/.UnicodeIME‘>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "ime enable io.appium.android.ime/.UnicodeIME">
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "ime set io.appium.android.ime/.UnicodeIME"
安装setting和unlock apk到测试设备安装setting apk到测试设备>
info: [debug] Pushing settings apk to device...>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 install "C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk"
安装unlock.apk到测试设备>
info: [debug] Pushing unlock helper app to device...>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 install "C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk">
info: Starting App>
info: [debug] Attempting to kill all ‘uiautomator‘ processes>
info: [debug] Getting all processes with ‘uiautomator‘>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "ps ‘uiautomator‘">
info: [debug] No matching processes found
6、运行测试机上的bootstrap>
info: [debug] Running bootstrap>
info: [debug] spawning: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.edusoho.kuozhi -e disableAndroidWatchers false>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=>
info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1>
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
appium socket server在4724端口打开>
info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724>
info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready>
info: [debug] [BOOTSTRAP] [debug] Loading json...
注册crash监听器>
info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
如果设备锁屏,则唤醒设备>
info: [debug] Waking up device if it‘s not alive
把wake命令push到appium工作队列>
info: [debug] Pushing command to appium work queue: ["wake",{}]>
info: [debug] [BOOTSTRAP] [debug] Client connected>
info: [debug] [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"wake","params":{}}>
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION>
info: [debug] [BOOTSTRAP] [debug] Got command action: wake>
info: [debug] [BOOTSTRAP] [debug] Returning result: {"status":0,"value":true}>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "dumpsys window">
info: [debug] Screen already unlocked, continuing.
把getDataDir命令push到appium工作队列>
info: [debug] Pushing command to appium work queue: ["getDataDir",{}]>
info: [debug] [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}>
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION>
info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir>
info: [debug] [BOOTSTRAP] [debug] Returning result: {"status":0,"value":"\/data\/local\/tmp"}>
info: [debug] dataDir set to: /data/local/tmp
把compressedLayoutHierarchy命令push到appium工作队列>
info: [debug] Pushing command to appium work queue: ["compressedLayoutHierarchy",{"compressLayout":false}]>
info: [debug] [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"compressedLayoutHierarchy","params":{"compressLayout":false}}>
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION>
info: [debug] [BOOTSTRAP] [debug] Got command action: compressedLayoutHierarchy>
info: [debug] [BOOTSTRAP] [debug] Returning result: {"status":0,"value":false}
再次检查设备API版本>
info: [debug] Getting device API level>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "getprop ro.build.version.sdk">
info: [debug] Device is at API Level 22
启动APP>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.edusoho.kuozhi/com.edusoho.kuozhi.KuozhiActivity"
让待测试APP获取焦点>
info: [debug] Waiting for pkg "com.edusoho.kuozhi" and activity "com.edusoho.kuozhi.KuozhiActivity" to be focused>
info: [debug] Getting focused package and activity>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "dumpsys window windows"
获取设备系统版本>
info: [debug] executing cmd: D:\Software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -s 5977b8a3 shell "getprop ro.build.version.release">
info: [debug] Device is at release version 5.1.1
设备初始化成功,准备接收testscript->
appium 服务器传过来的命令>
info: [debug] Device launched! Ready for commands
设置命令默认超时时间为60秒>
info: [debug] Setting command timeout to the default of 60 secs>
info: [debug] Appium session started with sessionId 2ac0e18a-9120-4e90-a066-c6ddb1a1deaf【appium启动运行log分析】
7.反馈最开始POST的请求结果>
info: <
-- POST /wd/hub/session 303 10052.520 ms - 74
推荐阅读
- TeamViewer app案例分析
- Android Studio 入门级教程
- unity发布安卓lua路径不存在问题
- java eclipse 安卓环境配置
- Check failed: status == CUBLAS_STATUS_SUCCESS (11 vs. 0) CUBLAS_STATUS_MAPPING_ERROR
- Java JFileChooser
- Java JEditorPane
- Java JDesktopPane
- Java JColorChooser