Error occurs on step 90, but now i deleted a href attribute from object properties and it started working, now it gives error on step 92, saying same thing unable to find the element located by xpath PFA screenshots of object properties of step 90 and 92 and also test code
Looking at the XPath, I have a very high concern about its correctness. You can verify the correctness of an XPath in Chrome is tool open the inspection tool, navigate to Elements tab, ctrl + F and paste the XPath in. If your target element is highlighted then the problem elsewhere, otherwise you’d need to choose a more robust XPath.
From personal experience though, XPaths with long attribute values are very fragile, so I’d advise choosing a different XPath anyway.
It worked finally by absolute xpath
It accepted the whole x path right from html tag, previously i was giving it from middle starting from td which it was not accepting
xpath that worked is : /html/body/form/section/div/div/table/tbody/tr/td/table/tbody/tr/td/table/tbody/tr/td/div/table/tbody/tr/td/table/tbody/tr/td/div/table/tbody/tr/td/a
Relative path did not work
Relative path worked but only for that session as i tried new session it failed
Problem with relative path is all attributes are dynamic even parent sibling, following child all seemed dynamic…there is no any reference point so i used absolute path
chropath suggested this absolute path…the short one which i was trying to use it did not accept
@Amruta.bagle Can you share the relative xpath for this object? There should be a way to use relative xpath using conditions in object selector properties. As said in above post absolute path would not work in the long run and may also break if you try to run your test on a mobile device.