Im trying to put an email address on email field but everytime I run my test script it says “web element not found” (full image below) I tried using xpath , css , attributes, adding waitForElement, used ChroPath to validate xpath but nothing works. Please help.
I reproduced your problem, frankly I can’t explain why your XPath is not working because when I open the inspection tool on Chrome and enter the XPath it detects successfully the element.
Anyway, I recommend this XPath instead since I tried it on playback and it works.
(.//*[normalize-space(text()) and normalize-space(.)='Email address'])/following::input
It feels strange. I think the problem is not your XPath : I tried loading directly the forgot-password page to validate the xpath , used setText, and it is working with your xPath.
In order to reproduce (because your screen capture is real), I repeated every step you did. I was able to get the same message “Unable to find the element located by xpath…” with Chrome (but not Firefox) because the click on “forgot pass” didn’t load the forgot-password page. Your waitForPageLoad is valid, because even if your click wasn’t working, your page is fully loaded ^^ Can you confirm that the forgot-password page isn’t loaded after the click on “forgot password” when you have the error message ?
Yes, I’ve observed too when I played back my script, forgot password-page was not loaded after clicking the Forgot Password link. That’s also another thing I did not understand , after performing the action=click(automated) it should be redirected to the Forgot password-page right?
Anyways, thank you so much for taking time to replicate and answer my question. I tried adding Delay before clicking the forgot pass link and yeahh its working, thank you so much its highly appreciated
It does if your element has something to do with the click ^^ In your case, the logic behind the click of your element is not fully loaded. I had similar issues with Angular and Chrome : it is beyond my knowledge. A new function has been introduced to adress this kind of issues (WebUI.waitForAngularLoad(0)), but in my case it is only working when Chrome is not running of first plan (very strange !) So this is a work in progress