1 Answer
- Newest
- Most votes
- Most comments
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
answered 4 years ago
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago