真的醉了,appium死活启动不了应用...

已于 2023-04-13 23:43:03 修改
阅读量1.2k 收藏
点赞数
文章标签： appium android android studio python
于 2023-04-13 23:36:56 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/xuejian_tian/article/details/130142854
版权 
[HTTP] Waiting until the server is closed
[HTTP] Received server close event
[Appium] Welcome to Appium v1.20.2
[Appium] Non-default server args:
[Appium]   relaxedSecurityEnabled: true
[Appium]   allowInsecure: {
[Appium]   }
[Appium]   denyInsecure: {
[Appium]   }
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session
[HTTP] {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"platformName":"Android"}}}
[W3C] Calling AppiumDriver.createSession() with args: [null,null,{"firstMatch":[{}],"alwaysMatch":{"platformName":"Android"}}]
[BaseDriver] Event 'newSessionRequested' logged at 1681399953584 (23:32:33 GMT+0800 (中国标准时间))
[Appium] 
[Appium] ======================================================================
[Appium]   DEPRECATION WARNING:
[Appium] 
[Appium]   The 'automationName' capability was not provided in the desired 
[Appium]   capabilities for this Android session
[Appium] 
[Appium]   Setting 'automationName=UiAutomator2' by default and using the 
[Appium]   UiAutomator2 Driver
[Appium] 
[Appium]   The next major version of Appium (2.x) will **require** the 
[Appium]   'automationName' capability to be set for all sessions on all 
[Appium]   platforms
[Appium] 
[Appium]   In previous versions (Appium <= 1.13.x), the default was 
[Appium]   'automationName=UiAutomator1'
[Appium] 
[Appium]   If you wish to use that automation instead of UiAutomator2, please 
[Appium]   add 'automationName=UiAutomator1' to your desired capabilities
[Appium] 
[Appium]   For more information about drivers, please visit 
[Appium]   http://appium.io/docs/en/about-appium/intro/ and explore the 
[Appium]   'Drivers' menu
[Appium] 
[Appium] ======================================================================
[Appium] 
[Appium] Appium v1.20.2 creating new AndroidUiautomator2Driver (v1.61.2) session
[Appium] Applying relaxed security to 'AndroidUiautomator2Driver' as per server command line argument. All insecure features will be enabled unless explicitly disabled by --deny-insecure
[BaseDriver] Creating session with W3C capabilities: {
[BaseDriver]   "alwaysMatch": {
[BaseDriver]     "platformName": "Android"
[BaseDriver]   },
[BaseDriver]   "firstMatch": [
[BaseDriver]     {}
[BaseDriver]   ]
[BaseDriver] }
[BaseDriver] Session created with session id: e1722508-8837-428b-af84-46daa0fbb83d
[UiAutomator2] Neither 'app' nor 'appPackage' was set. Starting UiAutomator2 without the target application
[ADB] Using 'adb.exe' from 'D:\android-sdk\platform-tools\adb.exe'
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 start-server'
[AndroidDriver] Retrieving device list
[ADB] Trying to find a connected android device
[ADB] Getting connected devices
[ADB] Connected devices: [{"udid":"127.0.0.1:21503","state":"device"}]
[AndroidDriver] Using device: 127.0.0.1:21503
[ADB] Using 'adb.exe' from 'D:\android-sdk\platform-tools\adb.exe'
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 start-server'
[ADB] Setting device id to 127.0.0.1:21503
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell getprop ro.build.version.sdk'
[ADB] Current device property 'ro.build.version.sdk': 25
[ADB] Device API level: 25
[AndroidDriver] No app sent in, not parsing package/activity
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 wait-for-device'
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell echo ping'
[AndroidDriver] Pushing settings apk to device...
[ADB] Getting install status for io.appium.settings
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell dumpsys package io.appium.settings'
[ADB] 'io.appium.settings' is installed
[ADB] Getting package info for 'io.appium.settings'
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell dumpsys package io.appium.settings'
[ADB] The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('3.2.1' >= '3.2.1')
[ADB] There is no need to install/upgrade 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk'
[ADB] Getting IDs of all 'io.appium.settings' processes
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:21503 shell 'pgrep --help; echo $?''
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1\:21503 shell 'pgrep ^appium\\.settings$ || pgrep ^io\\.appium\\.setti$''
[AndroidDriver] io.appium.settings is already running. There is no need to reset its permissions.
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell appops set io.appium.settings android:mock_location allow'
[Logcat] Starting logs capture with command: D:\\android-sdk\\platform-tools\\adb.exe -P 5037 -s 127.0.0.1\:21503 logcat -v threadtime
[UiAutomator2] Forwarding UiAutomator2 Server port 6790 to local port 8200
[ADB] Forwarding system: 8200 to device: 6790
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 forward tcp:8200 tcp:6790'
[ADB] Getting install status for io.appium.uiautomator2.server
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell dumpsys package io.appium.uiautomator2.server'
[ADB] 'io.appium.uiautomator2.server' is installed
[ADB] Getting package info for 'io.appium.uiautomator2.server'
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 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 ('4.17.4' >= '4.17.4')
[UiAutomator2] io.appium.uiautomator2.server installation state: sameVersionInstalled
[ADB] Checking app cert for C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.17.4.apk
[ADB] Using 'apksigner.jar' from 'D:\android-sdk\build-tools\27.0.1\lib\apksigner.jar'
[ADB] Starting apksigner: 'D:\\Program Files\\jdk1.8.0_66\\bin\\java.exe' -Xmx1024M -Xss1m -jar D:\\android-sdk\\build-tools\\27.0.1\\lib\\apksigner.jar verify --print-certs 'C:\\Program Files\\Appium\\resources\\app\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-v4.17.4.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-v4.17.4.apk'
[ADB] 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.17.4.apk' is signed with the default certificate
[ADB] Getting install status for io.appium.uiautomator2.server.test
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell dumpsys package io.appium.uiautomator2.server.test'
[ADB] 'io.appium.uiautomator2.server.test' is installed
[ADB] Checking app cert for C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[ADB] Starting apksigner: 'D:\\Program Files\\jdk1.8.0_66\\bin\\java.exe' -Xmx1024M -Xss1m -jar D:\\android-sdk\\build-tools\\27.0.1\\lib\\apksigner.jar verify --print-certs 'C:\\Program Files\\Appium\\resources\\app\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-debug-androidTest.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:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificate
[UiAutomator2] Server packages are not going to be (re)installed
[UiAutomator2] Waiting up to 30000ms for services to be available
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell pm list instrumentation'
[UiAutomator2] Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[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:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;'
[UiAutomator2] No app capability. Assuming it is already on the device
[UiAutomator2] Performing shallow cleanup of automation leftovers
[UiAutomator2] No obsolete sessions have been detected (read ECONNRESET)
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell am force-stop io.appium.uiautomator2.server.test'
[UiAutomator2] Starting UIAutomator2 server 4.17.4
[UiAutomator2] Using UIAutomator2 server from 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.17.4.apk' and test from 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk'
[UiAutomator2] Waiting up to 30000ms for UiAutomator2 to be online...
[ADB] Creating ADB subprocess with args: ["-P",5037,"-s","127.0.0.1:21503","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[WD Proxy] Matched '/status' to command name 'getStatus'
[WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8200/wd/hub/status] with no body
[WD Proxy] Error: read ECONNRESET
[WD Proxy]     at TCP.onStreamRead (internal/stream_base_commons.js:183:27)
[Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
[WD Proxy] Matched '/status' to command name 'getStatus'
[WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8200/wd/hub/status] with no body
[WD Proxy] Error: read ECONNRESET
[WD Proxy]     at TCP.onStreamRead (internal/stream_base_commons.js:183:27)
[WD Proxy] Matched '/status' to command name 'getStatus'
[WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8200/wd/hub/status] with no body
[WD Proxy] Got response with status 200: {"sessionId":"None","value":{"message":"UiAutomator2 Server is ready to accept commands","ready":true}}
[UiAutomator2] The initialization of the instrumentation process took 2027ms
[WD Proxy] Matched '/session' to command name 'createSession'
[WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8200/wd/hub/session] with body: {"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android"},"platformName":"Android","deviceName":"127.0.0.1:21503","deviceUDID":"127.0.0.1:21503"}],"alwaysMatch":{}}}
[WD Proxy] Got response with status 200: {"sessionId":"f6ad3d0d-f0b5-42db-b198-e1f3c626b773","value":{"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android"},"platformName":"Android","deviceName":"127.0.0.1:21503","deviceUDID":"127.0.0.1:21503"}],"alwaysMatch":{}},"sessionId":"f6ad3d0d-f0b5-42db-b198-e1f3c626b773"}}
[WD Proxy] Determined the downstream protocol as 'W3C'
[WD Proxy] Proxying [GET /appium/device/info] to [GET http://127.0.0.1:8200/wd/hub/session/f6ad3d0d-f0b5-42db-b198-e1f3c626b773/appium/device/info] with no body
[WD Proxy] Got response with status 200: {"sessionId":"f6ad3d0d-f0b5-42db-b198-e1f3c626b773","value":{"androidId":"8def579170fb9575","apiVersion":"25","bluetooth":{"state":"OFF"},"brand":"samsung","carrierName":"China Mobile GSM","displayDensity":360,"locale":"zh_CN","manufacturer":"samsung","model":"SM-S9010","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":"\"twxmok1321\"","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"}}
[ADB] Running 'D:\android-sdk\platform-tools\adb.exe -P 5037 -s 127.0.0.1:21503 shell dumpsys window'
[AndroidDriver] Screen already unlocked, doing nothing
[WD Proxy] Proxying [GET /appium/device/pixel_ratio] to [GET http://127.0.0.1:8200/wd/hub/session/f6ad3d0d-f0b5-42db-b198-e1f3c626b773/appium/device/pixel_ratio] with no body
[WD Proxy] Got response with status 200: {"sessionId":"f6ad3d0d-f0b5-42db-b198-e1f3c626b773","value":2.25}
[WD Proxy] Matched '/appium/device/system_bars' to command name 'getSystemBars'
[WD Proxy] Proxying [GET /appium/device/system_bars] to [GET http://127.0.0.1:8200/wd/hub/session/f6ad3d0d-f0b5-42db-b198-e1f3c626b773/appium/device/system_bars] with no body
[WD Proxy] Got response with status 200: {"sessionId":"f6ad3d0d-f0b5-42db-b198-e1f3c626b773","value":{"statusBar":54}}
[WD Proxy] Matched '/window/current/size' to command name 'getWindowSize'
[WD Proxy] Proxying [GET /window/current/size] to [GET http://127.0.0.1:8200/wd/hub/session/f6ad3d0d-f0b5-42db-b198-e1f3c626b773/window/current/size] with no body
[WD Proxy] Got response with status 200: {"sessionId":"f6ad3d0d-f0b5-42db-b198-e1f3c626b773","value":{"height":1920,"width":1080}}
[Appium] New AndroidUiautomator2Driver session created successfully, session e1722508-8837-428b-af84-46daa0fbb83d added to master session list
[BaseDriver] Event 'newSessionStarted' logged at 1681399957559 (23:32:37 GMT+0800 (中国标准时间))
[W3C (e1722508)] Cached the protocol value 'W3C' for the new session e1722508-8837-428b-af84-46daa0fbb83d
[W3C (e1722508)] Responding to client with driver.createSession() result: {"capabilities":{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android"},"platformName":"Android","deviceName":"127.0.0.1:21503","deviceUDID":"127.0.0.1:21503","deviceApiLevel":25,"platformVersion":"7.1.2","deviceScreenSize":"1080x1920","deviceScreenDensity":360,"deviceModel":"SM-S9010","deviceManufacturer":"samsung","pixelRatio":2.25,"statBarHeight":54,"viewportRect":{"left":0,"top":54,"width":1080,"height":1866}}}
[HTTP] <-- POST /wd/hub/session 200 3977 ms - 655
[HTTP] 
Appium server stopped successfully

以上是appium日志

import unittest
from appium import webdriver
from appium.webdriver.common.mobileby import MobileBy
from appium import webdriver
import time

caps = {
    'platformName': 'Android',
    'platformVersion': '7.1.2',
    'deviceName': '127.0.0.1:21503',
    'appPackage': 'com.xiaomi.shop',
    'appActivity': 'com.xiaomi.shop2.activity.MainActivity'}
dr = webdriver.Remote('http://localhost:4723/wd/hub', caps)
time.sleep(4)

# dr.find_element(MobileBy.ID, "com.xiaomi.shop.plugin.homepage:id/fragment_search_swither").send_keys("电视")
# dr.find_element(MobileBy.ID, "com.xiaomi.shop2.plugin.search: id / search_fragment_search_btn").click()

以上是pycharm代码,adb连接没问题,第一次运行代码时候,模拟器上的appiumsetting也会启动然后再退出那么一瞬间,但是按照老师的要求启动一下小米商城app,就是启动不了,也试了chrom等应用,都不行,但是逍遥模拟器上成功的自动安装了appiumsetting,从中午捣鼓到现在都没弄好,求大哥们帮忙看下T T

xj.thia
关注
关于appium踩坑 selenium.common.exceptions.WebDriverException: Message: An unknown server-side error（已解决）
易编橙 · 终身成长社群，相遇已是上上签！
06-26 4万+
点进来的小伙伴一定要先仔细看一下自己的报错详情是否与博主的一致，该 "WebDriverException" 异常类型很多，请仔细核查该文的报错信息是否与你的一致。
appium无法启动app的常见原因、解决方案
hzau_boy的博客
12-29 2107
把系统的adb安装目录（例如D:\android-sdk-windows\platform-tools）的platform-tools目录中的adb程序复制出来，改名为nox_adb，然后替换掉夜神模拟器安装目录/bin下的nox_adb。可以尝试添加参数 “automationName” = “UiAutomator2”因为当前的appActivity设置的不是app首次进入的appActivity。由于我使用的夜神模拟器，它本身自带了一个adb，和系统的adb起了冲突。开启后，再试试可能不会报这个错。
Failed to launch Appium Settings app
weixin_43730921的博客
10-07 701
报错：Failed to launch Appium Settings app: Condition unmet after 5364 ms. Timing
Appium UIAutomator2 Server 使用指南
最新发布
gitblog_00851的博客
08-21 657
Appium UIAutomator2 Server 使用指南 appium-uiautomator2-serverAppium UiAutomator/UiObject2-based server for Android UI automation. This module is used by appium-uiautomator2-driver component项目地址:https://...
appium启动app失败_实战演练：Appium脚本转换+自动化测试实例
weixin_39603132的博客
11-02 264
移动端APP的测试处于不断探索，不断进化的过程中，而手机银行是目前各大银行金融科技战争的主要阵地，如何更好更快地对手机银行进行测试是个热门话题，也是个值得深入研究的课题。本文以某行手机银行测试为例，描述了SoloPi用例执行录制转为Appium脚本后集成至jenkins，并完成自动化部署后的真机并发执行实践流程，并对Appium 1.15.1和安卓10使用中存在的一些问题提供了解决方法，希望能够对...
appium启动app失败_Appium做自动化测试，chromedriver/chrome问题与技巧集锦
weixin_39968410的博客
11-25 371
一、前言APP的 webview 自动化是依赖于 chromedriver 的，并且每个APP的 webview 版本号都不太一样，这就导致了每次都需要重新去下载对应的chromedriver 版本。如何根据当前的 webdriver 版本去匹配对应 chromedriver 版本，这是一个难题。根据官方文档翻译过来看，版本不匹配的话一般会报错：An unknown server-side err...
appium启动app失败_Python学下教程：另辟蹊径，appium抓取app应用数据了解一下
weixin_39900468的博客
11-24 1058
作为爬虫工程师，没有价格不知道selenium的。什么是selenium？Selenium原本是一个用于Web应用程序自动化测试工具。Selenium测试直接运行在浏览器中，就像真正的用户在操作一样。支持的浏览器包括IE(7, 8, 9, 10, 11)，Mozilla Firefox，Safari，Google Chrome，Opera等。我们爬虫工程师使用selenium来抓取动态web页面。...
appium启动app失败_一套完整的Appium自动化测试环境搭建过程
weixin_39799561的博客
11-12 841
前言Appium是一个开源的自动化测试框架，支持跨平台，支持多种编程语言，可用于原生，混合和移动web应用程序，使用webdriver驱动ios，android应用程序、那么为了学习app自动化测试首要任务肯定就是搭建测试开发环境， 因此在这里记一次搭建Appium自动化测试环境的完整过程，文章较长，需要花费一定的时间，请耐心阅读，如果文中有什么错误请指正。安装Java JDKJDK环境...
Appium-windows-1.19.1.exe
01-15
Appium 移动端自动化测试 Windows版本Appium-windows-1.19.1.exe Appium Server and Inspector in Desktop GUIs for Mac, Windows, and Linux
Appium-Inspector-2023.2.1 windows linux mac
03-03
Appium Inspector 2023.2.1是一款强大的自动化测试工具，专为移动应用程序而设计，支持Windows、Linux和Mac操作系统。这个版本的更新带来了更先进的功能和优化，以帮助开发者和测试工程师高效地进行Appium自动化测试...
Appium-windows-1.13.0.exe
06-05
appium-desktop for windows 安装包，应用于安卓、iosUI自动化，native hybrid h5都兼容
Appium-windows-1.20.0.exe
02-26
Appium1.20 windows版本
appium踩坑：Error: Failed to launch Appium Settings app: Cannot start the ‘io.appium.settings‘ applicat
weixin_48229148的博客
01-20 4388
appium server完整报错信息： Error: Failed to launch Appium Settings app: Cannot start the ‘io.appium.settings’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Origina
appium启动app失败_一文带你趟过mac搭建appium测试环境的遇到的坑
weixin_39615596的博客
11-26 1097
做UI自动化，最难的一步就是在环境搭建上，怎么去搭建一个UI自动化测试的环境，会难住很多人，在Mac上搭建appium如何搭建呢，本文带着大家去领略如何在mac上搭建appium测试环境。下面就是详细的搭建的过程。如果没有安装过Homebrew,先安装homebrew/usr/bin/ruby -e "$(curl -fsSL https://raw.gi...
appium做app自动化无法启动的问题（Original error: Unable to find an active device or emulator with OS 8）等问题
weixin_45922111的博客
06-23 8535
一、appium做app自动化遇到的问题汇总 1、Android版本填写错误 ‘platformVersion’：’11’ 我手机上的版本明明是11，但是填了之后，居然不对，报错： selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Unable to find an active
Appium Server 启动失败常见原因及解决办法
kindtester的博客
12-21 1081
错误原因：Appium 默认的4723端口被占用。
Appium自动化测试：通过appium的inspector功能无法启动app的原因_appium inspector链接ios真机后,无法点击
2401_84240742的博客
04-15 1243
业感兴趣的新人，都欢迎加入我们的的圈子（技术交流、学习资源、职场吐槽、大厂内推、面试辅导），让我们一起学习成长！出现这样的错误一定是因为当前的appActivity设置的不是app首次进入的appActivity。获取首次应用的活动名称可以通过 启动一次随机 monkey命令来获取。adb shell monkey -p 包名 -v -v -v 1。
Appium自动化测试：通过appium的inspector功能无法启动app的原因
dad22211的博客
11-19 1286
Python接口自动化测试零基础入门到精通（2023最新版）
Appium环境启动失败解决方法
我管它叫“知勤者笔记”，主要用来记录和分享我的日常生活与学习经历
11-10 1417
Appium环境启动失败解决方法
appium-windows-1.18.0.zip下载 -csdn
10-13
appium-windows-1.18.0.zip下载 -csdn是指在CSDN网站上下载appium-windows-1.18.0.zip文件。Appium是一款开源的移动应用自动化工具，用于在移动设备上自动化测试移动应用程序。1.18.0是Appium的版本号，用于指代该版本的Appium工具。zip文件是一种常见的压缩文件格式，可以用于存储和传输大量文件。在CSDN网站上，你可以找到并下载Appium的压缩包文件（appium-windows-1.18.0.zip）。 在下载Appium之前，你需要确保已经安装了适用于Windows操作系统的下载和解压缩zip文件的工具，如WinRAR或7-Zip等。访问CSDN网站的下载页面，搜索并找到appium-windows-1.18.0.zip文件的下载链接。点击下载链接，选择保存文件。下载完成后，你可以在保存的位置找到下载的zip文件。 要使用下载的Appium工具，你需要解压缩zip文件。右键点击下载的zip文件，选择使用相应的解压缩工具进行解压缩。解压缩后，你将得到一个包含Appium工具的文件夹。在文件夹中，你可以找到运行Appium的可执行文件以及相关的配置文件和文档。根据需要，你可以根据Appium的官方文档和指南来配置和使用这个工具。 总结来说，appium-windows-1.18.0.zip是Appium的一个版本的压缩文件，你可以在CSDN网站上下载并使用它来进行移动应用自动化测试。
评论 7
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值