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
7.反馈最开始POST的请求结果
> info: <-- POST /wd/hub/session 303 10052.520 ms - 74
- Appium Server 源码分析之启动运行Express http服务器
通过上一个系列Appium Android Bootstrap源码分析我们了解到了appium在安卓目标机器上是如何通过bootstrap这个服务来接收appium从pc端发送过来的命令,并最终使用u ...
- Appium Android Bootstrap源码分析之启动运行
通过前面的两篇文章<Appium Android Bootstrap源码分析之控件AndroidElement>和<Appium Android Bootstrap源码分析之命令解析 ...
- Appium Android Bootstrap源代码分析之启动执行
通过前面的两篇文章<Appium Android Bootstrap源代码分析之控件AndroidElement>和<Appium Android Bootstrap源代码分析之命令 ...
- 老李推荐:第5章7节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 循环获取并执行事件 - runMonkeyCycles
老李推荐:第5章7节<MonkeyRunner源码剖析>Monkey原理分析-启动运行: 循环获取并执行事件 - runMonkeyCycles poptest是国内唯一一家培养测试开 ...
- 老李推荐:第5章6节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 初始化事件源
老李推荐:第5章6节<MonkeyRunner源码剖析>Monkey原理分析-启动运行: 初始化事件源 poptest是国内唯一一家培养测试开发工程师的培训机构,以学员能胜任自动化测试 ...
- 老李推荐:第5章3节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 启动脚本
老李推荐:第5章3节<MonkeyRunner源码剖析>Monkey原理分析-启动运行: 启动脚本 poptest是国内唯一一家培养测试开发工程师的培训机构,以学员能胜任自动化测试,性 ...
- 老李推荐:第5章5节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 获取系统服务引用
老李推荐:第5章5节<MonkeyRunner源码剖析>Monkey原理分析-启动运行: 获取系统服务引用 上一节我们描述了monkey的命令处理入口函数run是如何调用optionP ...
- 老李推荐:第5章2节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 启动流程概览
老李推荐:第5章2节<MonkeyRunner源码剖析>Monkey原理分析-启动运行: 启动流程概览 每个应用都会有一个入口方法来供操作系统调用执行,Monkey这个应用的入口方法就 ...
- 老李推荐:第5章1节《MonkeyRunner源码剖析》Monkey原理分析-启动运行: 官方简介
老李推荐:第5章1节<MonkeyRunner源码剖析>Monkey原理分析-启动运行: 官方简介 在MonkeyRunner的框架中,Monkey是作为一个服务来接受来自Monkey ...
随机推荐
- 6.28 Windows Serviece
描述: A 软件,已经注册了一个windows服务并启用,现在需要在服务自己的一个类B里增加一个字段,服务的作用是返回一个该类型B的实例 做法 增加字段,替换服务文件,重新注册服务并开启,但是在A软件 ...
- selenium chromedriver与谷歌浏览器版本映射表 (更新至v2.32)
----------ChromeDriver v2.32 (2017-08-30)---------- Supports Chrome v59-61最新的ChromeDriver 2.32 支持谷歌浏 ...
- 数据库学习任务二:数据库连接对象SqlConnection
数据库应用程序的开发流程一般主要分为以下几个步骤: 创建数据库 使用Connection对象连接数据库 使用Command对象对数据源执行SQL命令并返回数据 使用DataReader和DataSet ...
- 32位汇编第四讲,干货分享,汇编注入的实现,以及快速定位调用API的数量(OD查看)
32位汇编第四讲,干货分享,汇编注入的实现,以及快速定位调用API的数量(OD查看) 昨天,大家可能都看了代码了,不知道昨天有没有在汇编代码的基础上,实现注入计算器. 如果没有,今天则会讲解,不过建议 ...
- Vue项目搭建基础之Vue-cli模版测试
第一步安装node,nodejs.org下载node稳定版安装包.node -v (查看node版本)npm install -g vue-cli(安装Vue脚手架环境)vuevue listvu ...
- 【Beta】Daily Scrum Meeting——Day7
站立式会议照片 1.本次会议为第七次Meeting会议: 2.本次会议在中午12点,在陆大楼召开,本次会议为30分钟讨论今天要完成的任务以及接下来的任务安排. 燃尽图 每个人的工作分配 成 员 昨天已 ...
- 201521145048《Java程序设计》第14周学习总结
1. 本周学习总结 1.1 以你喜欢式(思维导图或其他)归纳总结多数据库相关内容. 1.数据库的定义:是为了实现一定目的按某种规则组织起来的"数据"的"集合". ...
- 201521123027 <java程序设计>第九周学习总结
1.本周学习总结 1.1 以你喜欢的方式(思维导图或其他)归纳总结异常相关内容. 2.书面作业 Q1.常用异常 题目5-1 1.1 截图你的提交结果(出现学号) 1.2 自己以前编写的代码中经常出现什 ...
- Hyperledger Fabric 1.0 从零开始(八)——Fabric多节点集群生产部署
6.1.平台特定使用的二进制文件配置 该方案与Hyperledger Fabric 1.0 从零开始(五)--运行测试e2e类似,根据企业需要,可以控制各节点的域名,及联盟链的统一域名.可以指定单独节 ...
- HashMap 学习心得
1.构造 HashMap 底层数据结构线性数组,HashMap有一个静态内部类Entry,Entry有四个属性,key,value,next,hash Entry就是HashMap键值对实现的一个基础 ...