-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
"waitForElementNotPresent" always waits till the timeout value #2066
Comments
Can you send a full log? |
Until there's a fix you can try using |
@beatfactor I will be able to give full log in the evening but this should be very easy to reproduce (if it doesn't happen on my side only ofc) |
Does this happen in v1.0.19 as well? |
I am seeing this with version 1.2.4, and it applies to all cases of waitForElementNotPresent and also expect.element().not.present |
@bethcodes can you open a new issue please? |
Nightwatch version: 1.1.0
When using "waitForElementNotPresent" this command always waits till the timeout value and only then returns result. Checked using page-objects and directly in test code.
Element for sure is not present but command is keeping wait till timeout
Logs:
→ Running command: waitForElementNotPresent ('test locator', 10000) Request POST /wd/hub/session/'...'/elements { using: 'css selector', value: 'test locator' } Response 200 POST /wd/hub/session/'...'/elements (31ms) { sessionId: '', status: 0, value: [] } Request POST /wd/hub/session/'...'/elements { using: 'css selector', value: 'test locator' } Response 200 POST /wd/hub/session/'...'/elements (16ms) { sessionId: '', status: 0, ...
The text was updated successfully, but these errors were encountered: