05-09-22 10:32 AM
06-09-22 12:54 PM
06-09-22 03:18 PM
12-09-22 09:45 PM
14-09-22 07:30 AM
Hi Daniel,
Modern websites are quite dynamic in nature. This means elements spied at one time may not still be valid when the page state has changed. Such change can be caused by you performing navigation, triggering JavaScripts and etc. The most difficult part is that you often need to learn it the hard way and then look back into how you can optimise your attributes to work for the specific website.
One common culprit is to include Web Path attribute, which is built based on HTML DOM hierarchy at the time when you spied the element. You should try avoiding Web Path using a fixed value, or not using it completely if possible for such websites. XPath and CSS Selector can be really useful ally in this kind of situation, due to their ability to focus on a small part of the HTML that uniquely identifies the element, as opposed to everything from the top of the hierarchy to the element in question.
There may be other factos in play. A good approach when you encounter this issue is to spy the web element again in a new element and compare it with what you spied before. That may often reveal the reason for the discrepency.
Hope this helps.
15-09-22 04:33 PM