-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 支持 "elementByXPath" #36
Comments
Android 暂不支持 xpath,可以先用 ByClass 吗? |
谢谢!是不是 |
@codingfishman 能稍微描述下什么样的场景吗 |
谢谢,好的。 底部的菜单栏最底层叫做 我们主要是想把我们这个工具交给QA来使用,希望他们通过Appium能比较方便的找到对应元素的selector,也可以让测试代码更直观一些。所以如果能够支持 再次感谢! |
@codingfishman 先用source-id 可以吗?elementById |
@kobe990 xpath功能好了吗? |
Darwin fishmanadeMBP.lan 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_6
Hi There,
I tried to locate the element in Android with xpath but failed all the time. I got the xpath from Appium, something like :
//android.widget.TextView[@text="消息"]
, and I tested in Appium it can get the target element.But when I reach to macaca, the xpath doesn't work. If I tried to
elementByClassName
it will return all the elements, but for the QA guys, they are unable to find the target index of the element, as there could be a lot.The xpath works fine with iOS app, maybe I made something wrong in android?
Thanks in advance!
The text was updated successfully, but these errors were encountered: