
The error message given "Element with locator '...' not found."
indicates that it can not find the element. This is generally a
pretty trustworthy error message so it tends to indicate a
specific set of problems. [If it were another error like "element
not interactable" that would be indicating another set of
problems.]
In such cases the first thing I do is to manual check to make sure
the xpath is valid. The technique I use is outlined in this
stackoverflow answer - https://stackoverflow.com/a/22573161. If
this finds that xpath then the next item I check is to see if it
is a timing issue. That is is my script running faster then the
page or the page running some javascript and "not ready" yet.
A general technique to discover this is to put a Sleep keyword, making sure I get it enough time for the page to "settle", just before the input text keyword. and run the script several times over. If it passes every time then I tend to think it is a timing issues. To resolve timing issues there are several techniques including an explicit wait using the "Wait For ..." keywords or using one of the external third party libraries for implicit waiting, like Selenium Testibility - https://github.com/rasjani/robotframework-seleniumtestability - or if Angular site, the AngularJS Library - https://github.com/Selenium2Library/robotframework-angularjs.
That is my general steps to start debugging such an issue.
Ed
--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/robotframework-users/8d203a2d-7b08-4699-9b10-ecc7d54eb520n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/robotframework-users/fa6672af-0ae1-3ef6-a407-6f3c77a737e5%40verizon.net.