-
Notifications
You must be signed in to change notification settings - Fork 36
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
Verifying compatibility with Selenium 3.x #36
Comments
Hi! Thanks for watching. Looking at the changes I don't see any reason we need to adjust, since GridRouter is only proxying requests to selenium hubs, nothing more. If someone is experiencing issues and found this thread — please share! Thanks P.S. To actually verify this ourselves is anyway a good idea, agree here. |
Selenium 3 has two main differences:
Having said that Selenium Server becomes useless for 90% of cases (Firefox, Chrome, Opera Blink, Appium-based mobile browsers) because standalone drivers or Appium do all the work. More than that Selenium Server has manually implemented proxying logic that suffers from unexpected timeout issues. We're currently working on an alternative lightweight Selenium hub implementation here: http://github.com/aandryashin/selenoid A first stable release will come in a few weeks. |
Hey,
Not sure, but there are few changes in Selenium 3.x, see Selenium Changelog.
So, it will be useful to verify (and to adjust if needed) Selenium 3.x.
Thanks
The text was updated successfully, but these errors were encountered: