adb/atx测试-＞总结

7.当adb安装成功以后，会在后台启动一个adb server 程序，与移动设备上的adbd程序相对应，adbd是在安卓系统后台中启动的一个程序。（这个adbd应该跟atx没关系，虽然都是守护进程，用没有安装atx 的手机试试，atx 应该是为了uiautomator2自动化框架服务的)
先连adb再连atx服务u2.connect(“192.168.1.12”)则成功；
adb没有连接之前直接连atx服务u2.connect(“192.168.1.12”)会失败；
直接u2.connect_adb_wifi(‘192.168.1.12’)这个connect_adb_wifi是先连了adb再连了atx；
说明atx依赖于adb成功连接的基础上。

import uiautomator2 as u2
先连adb再连atx服务u2.connect(“192.168.1.12”)则成功
u2.connect(“192.168.1.12”)
[W 220514 10:35:40 init:218] [pid:48570] atx-agent has something wrong, auto recovering
[I 220514 10:35:40 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(3.0s)
[D 220514 10:35:40 init:322] [pid:48570] [192.168.1.12] device 192.168.1.12 is online
[I 220514 10:35:41 init:156] uiautomator2 version: 2.16.13
[D 220514 10:35:41 init:167] Shell: (‘/data/local/tmp/atx-agent’, ‘server’, ‘–stop’)
[I 220514 10:35:42 init:285] skip version check for atx-agent dev
[D 220514 10:35:42 init:167] Shell: (‘/data/local/tmp/atx-agent’, ‘server’, ‘–nouia’, ‘-d’, ‘–addr’, ‘127.0.0.1:7912’)
[I 220514 10:35:42 init:350] Check atx-agent version
[D 220514 10:35:42 init:359] Forward: local:tcp:52119 -> remote:tcp:7912
[D 220514 10:35:43 init:359] Forward: local:tcp:52123 -> remote:tcp:7912
[D 220514 10:35:43 init:362] atx-agent version dev
[D 220514 10:35:43 init:365] device wlan ip: 192.168.1.12
<uiautomator2.Device object at 0x105b29f98>
adb没有连接之前直接连atx服务u2.connect(“192.168.1.12”)会失败
u2.connect(“192.168.1.12”)
[W 220514 10:46:12 init:218] [pid:48570] atx-agent has something wrong, auto recovering
[I 220514 10:46:12 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(3.0s)
[I 220514 10:46:13 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(2.0s)
[I 220514 10:46:14 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(1.0s)
Traceback (most recent call last):
File “”, line 1, in
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 1914, in connect
return connect_usb(addr)
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 1955, in connect_usb
return Device(serial)
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 262, in init
wlan_ip = self.wlan_ip
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 453, in wlan_ip
ip = self.http.get(“/wlan/ip”).text.strip()
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/requests/sessions.py”, line 555, in get
return self.request(‘GET’, url, **kwargs)
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 223, in request
self.__client._prepare_atx_agent()
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 321, in _prepare_atx_agent
raise RuntimeError(“USB device %s is offline” % self._serial)
RuntimeError: USB device 192.168.1.12 is offline
u2.connect(“192.168.1.12”)
[W 220514 10:46:18 init:218] [pid:48570] atx-agent has something wrong, auto recovering
[I 220514 10:46:18 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(3.0s)
[I 220514 10:46:19 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(2.0s)
[I 220514 10:46:20 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(1.0s)
Traceback (most recent call last):
File “”, line 1, in
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 1914, in connect
return connect_usb(addr)
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 1955, in connect_usb
return Device(serial)
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 262, in init
wlan_ip = self.wlan_ip
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 453, in wlan_ip
ip = self.http.get(“/wlan/ip”).text.strip()
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/requests/sessions.py”, line 555, in get
return self.request(‘GET’, url, **kwargs)
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 223, in request
self.__client._prepare_atx_agent()
File “/Users/shiwy/.pyenv/versions/3.6.0/lib/python3.6/site-packages/uiautomator2/init.py”, line 321, in _prepare_atx_agent
raise RuntimeError(“USB device %s is offline” % self._serial)
RuntimeError: USB device 192.168.1.12 is offline
直接u2.connect_adb_wifi(‘192.168.1.12’)这个connect_adb_wifi是先连了adb再连了atx；说明atx依赖于adb成功连接的基础上。
u2.connect_adb_wifi(‘192.168.1.12’)
connected to 192.168.1.12:5555
[W 220514 10:47:01 init:218] [pid:48570] atx-agent has something wrong, auto recovering
[I 220514 10:47:01 init:362] [pid:48570] [192.168.1.12] wait-for-device, time left(3.0s)
[D 220514 10:47:01 init:322] [pid:48570] [192.168.1.12] device 192.168.1.12 is online
[I 220514 10:47:01 init:156] uiautomator2 version: 2.16.13
[D 220514 10:47:01 init:167] Shell: (‘/data/local/tmp/atx-agent’, ‘server’, ‘–stop’)
[I 220514 10:47:02 init:285] skip version check for atx-agent dev
[D 220514 10:47:02 init:167] Shell: (‘/data/local/tmp/atx-agent’, ‘server’, ‘–nouia’, ‘-d’, ‘–addr’, ‘127.0.0.1:7912’)
[I 220514 10:47:02 init:350] Check atx-agent version
[D 220514 10:47:02 init:359] Forward: local:tcp:52406 -> remote:tcp:7912
[D 220514 10:47:02 init:359] Forward: local:tcp:52410 -> remote:tcp:7912
[D 220514 10:47:03 init:362] atx-agent version dev
[D 220514 10:47:03 init:365] device wlan ip: 192.168.1.12
<uiautomator2.Device object at 0x105bbd208>

adb/atx测试-＞总结相关推荐

ADB稳定性测试教程干货
文章目录前言一.直接上干货前言 ADB稳定性测试新手教程提示:以下是本篇文章正文内容,下面案例可供参考一.直接上干货 adb devices 查看连接设备名 adb shell dumpsy ...
Android手机app的adb命令测试电量
Android手机app电量测试 Android 5.0及以上的设备, 允许我们通过adb命令dump出电量使用统计信息第一步:手机安装要测试的应用,打开手机开发者模式-USB模式,运行cmd.ex ...
android手机连接AS的adb wifi测试教程
1.确认本机PC没有任何adb设备连接,包括模拟器和usb连接 adb devices命令(AS上面的Terminal)回车查看当前PC端连接有多少设备 2.将远程android设备接入Wi-Fi,并 ...
Android测试中常用的adb命令、monkey命令
Android调试桥,一种多功能命令行工具,与设备进行通信查看adb版本:adb version 关闭和启动adb服务:adb kill-server // adb start-server 安装a ...
Android Monkey测试入门（摘）
Monkey是一款通过命令行来对我们APP进行测试的工具,可以运行在模拟器里或真机上.它向系统发送伪随机的用户事件流,实现对正应用程序进行压力测试. 官方介绍 :https://developer.a ...
“开源”vs“商业”，差别到底有多大？这篇测试一目了然
近些年来在数据分析领域,涌现出很多开源的技术方案,例如Presto.Spark.Impala等.面对多种选择,客户往往会比较困惑.无从下手.此外,MySQL生态非常火热,但对于数据分析类场景,使用此类 ...
android连接程序,android程序如何连接真机进行测试
android 如何连真机测试个人认为第三种方法更易理解 1. 设置android手机为USB调试模式.步骤: menu---> 设置 ---> 应用程序 ---> 开发 , 选择 ...
Win10 WSL adb使用
1.屏幕打印缓冲区大小设置,调大可以看到更多log信息 2.在LInux子系统里fastboot deiveces找不到设备的情况,以下解决方式: # sudo ln -s /mnt/c/Windo ...
1.Android稳定性测试
工具 adb monkey 测试前提 1)PC端已安装adb环境及做好配置注:需要安装JDK.Android SDK并分别进行环境变量配置(此不为本次重点,不提供安装细则,可以参考本文档底部提供的参 ...

adb/atx测试-＞总结

adb/atx测试-＞总结相关推荐

最新文章

热门文章