-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid xpath from Selenium when using find in Element subclass #3
Comments
It's not a bug. Most likely element with an id "del_name_4" doesn't exist on the page you requested. |
Hi Jakub, If I'm not fully mistaken (I'll take the time to review it again real soon): We had the same test code before (but without extending Element (instead I have also tried setting either xpath or CSS selector/locator pairs in Also, since it's not the case that null (no NodeElement object) is returned Again, I will take another look at this and see if I can find a possible Thanks, |
Could you paste the related part of the html? |
Hi @jakzal,
|
I can't see anything wrong. I'd rather explicitly specify that del_name_4 is an id: I'll have to debug it :) |
@MPV have you solved the issue eventually? |
Hi,
Is this a bug in BehatPageObjectExtension?
We get this error:
And this is the type of code we use:
The text was updated successfully, but these errors were encountered: