Added test to verify TOAST messages #520
Conversation
|
|
||
| MobileElement popUpElement = driver.findElement(MobileBy.AccessibilityId("Make a Popup!")); | ||
| popUpElement.click(); | ||
| driver.findElement(By.xpath(".//*[@text='Search']")).click(); |
There was a problem hiding this comment.
Cool. I did tested (from latest android server) this from your branch yesterday :) I think it failed for me here. After adding wait it failed to find the TOAST on next step. Will retest again today.
There was a problem hiding this comment.
Ohh, I would request you test with this test. Typically UiAutomator2 driver works faster then old driver, adding implicit wait would be more appropriate to avoid sync issues.
There was a problem hiding this comment.
Sure will do that. Between can you please fix codacy issues?
There was a problem hiding this comment.
how to write it by testng , it can not find wait.until
|
@sravanmedarapu This PR is in the conflicted state. Could you update it? |
|
Thanks @sravanmedarapu |
|
@TikhomirovSergey you are error |
Change list
Added test to verify TOAST messages
Req: #appium/appium#4824
Types of changes
What types of changes are you proposing/introducing to Java client?
Put an
xin the boxes that applyDetails
Should work with appium-uiautomator2-driver v0.0.9
Note:
Because of the google UiAutomaor2 limitation, it is not possible to perform any operation on TOAST element, performing any operations [ex:
getText()] will throwStaleObjectExecption. i.e It is only possible to verify the TOAST message.@SrinivasanTarget please review