1 個回答
- 最新
- 最多得票
- 最多評論
0
Hi:
Thank you for reaching out; sorry for the inconvenience you are having. I was able to look into the logs. From the console, you can download your test run artifacts to take a closer look at the errors. From the logs, the error I am observing is:
org.openqa.selenium.NoSuchElementException: Can't locate an element by this strategy: By.id: <ID>
The Appium server is starting successfully on the device, which implies that the search method for UI elements on the Android screen is not executing as expected in the test. I suggest reading this post (https://sqa.stackexchange.com/questions/20186/unable-to-locate-element-throwing-a-org-openqa-selenium-nosuchelementexception-i) to mitigate. Some key highlights:
- Assert with text or element to ensure you are on expected page/screen
- I will suggest to use wait.untill(element.isVisible()) before Click() /Assert()
- Have I provided a wrong value for searching the element?
Please let me know if you have any further questions; thanks.
Andy
已回答 4 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前