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
JavaScript execution timeout improvements #458
Milestone
Comments
FYI that's the thread dump of where it's hanging:
|
@kutzi I've tried to reproduce the issue and it doesn't occur. What I'm seeing on your example is you are using your own JS executor. Could you please String script = "arguments[0].click()";
FluentJavascript fluentJavascript = executeScript(script, find(".notExistingOne").first().getElement()); I'm adding a unit test to our integration tests suite. The test fails quickly w/ following error, which is expected:
|
filipcynarski
added a commit
that referenced
this issue
Jan 13, 2017
filipcynarski
added a commit
that referenced
this issue
Jan 13, 2017
Unit test added for issue reported in #458
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@kutzi had an issue where we were doing something like
js.executeScript("arguments[0].click()", find(SELECTOR_POPUP_CLOSE_BUTTON).first().getElement());
That seemed to have stopped because of Lazy Locators (BTW: it was hanging forever! Is there some way to make it fail (fast)?)
The text was updated successfully, but these errors were encountered: