or delete wda app and run test
@patrickinminneapolis ^^^
Hello. Could anyone indicate a good report to use with Appium running tests in parallel? I currently run my tests with pytest-xdist using the Allure report (each test case runs on 3 different devices), but the problem is that in the allure report it is difficult to differentiate when the tests are running in parallel.
Does anyone know how to avoid this?
we have installed *.ipa files in iphone..
Ex:
For Android FindBy(id = "com.abc.xx:id/sign_in_btn") . For iOS @FindBy(xpath="//XCUIElementTypeButton[@name='sign_in']")
For Android FindBy(id = "com.abc.xx:id/sign_in_btn") . For iOS @FindBy(xpath="//XCUIElementTypeButton[@name='sign_in']")
But only accesibility names only displayed for iOS .. not actuall Object IDs..
Is there any way for get the "Object IDs" in iOS as well ?
Help me.
Hi , We are newly started using appium tool for automating both iOS and Android Apps.. In iOS, we are observing only "NAMEs" are Object IDs. In otherwords, both "text" and Object ID attributes are same.. How to access the object IDs in iOS Appium
Any suggestions ?
hello sir.
do you have genymotion personal free?
@balaji-sachidanandam
Just for an overview: in appium you can use absolute xpath, accessibility id and xpath.
Using appium inspector or Xcode accessibility inspector you can determine
xpath: //XCUIElementTypeStaticText[@label=''];
Accesssinlity id: use directly.
XPATH: driver.findElement(by.xpath(//XCUIElementTypeStaticText[@label='XYZ']));
Access id: driver.findElement(MobileBy.id("XYZ"))
And try to avoild absolute xapth!
Just for an overview: in appium you can use absolute xpath, accessibility id and xpath.
Using appium inspector or Xcode accessibility inspector you can determine
xpath: //XCUIElementTypeStaticText[@label=''];
Accesssinlity id: use directly.
XPATH: driver.findElement(by.xpath(//XCUIElementTypeStaticText[@label='XYZ']));
Access id: driver.findElement(MobileBy.id("XYZ"))
And try to avoild absolute xapth!
@hardik-plume for iOS 13.0, appium has an issue
Refer: appium/appium#13072
This will be fixed in appium release 1.15.0
Refer: appium/appium#13072
This will be fixed in appium release 1.15.0
Hey Guys,
I am facing an issue with Appium 1.14 & 1.13 , I am using Mac catilana and xcode version 11 . the problem i have is, the appium desktop is getting stuck while starting the session, though it does launch the app but in inspector, it just shows "Gathering initial app source…"
I am facing an issue with Appium 1.14 & 1.13 , I am using Mac catilana and xcode version 11 . the problem i have is, the appium desktop is getting stuck while starting the session, though it does launch the app but in inspector, it just shows "Gathering initial app source…"
any idea
?
@drawat71
XCODE 11 needs Appium 1.15.x. We are currently busy with the last things for 1.15 and it will be released very soon. In the meantime you can do the following
npm install -g appium@1.15.0-rc.4- start the appium server through the command line on for example port
4723 - start appium desktop on port
4724 - then select a customer server, see below image, and start a simulator
I tried $('.myQbAppList') gives element not found
I
Hey all! Wanted to see if anyone has automated against AV Player in the past. I am looking at trying to get the captions which AV Player creates but I cannot inspect them via Appium. Does anyone know of another way to get that element? It might not be possible I know this but I wanted to ask.
AV Player is iOS internal video playback library.
To save value
I have used driver.pressKeycode(66) but no luck
@mikesalvia @drawat71 @skamineni
