search

seleniumkit / gridrouter

Selenium-based solution to serve 1000+ browsers
Other
152 stars 36 forks source link

Verifying compatibility with Selenium 3.x #36

Open Shnitzelil opened 7 years ago

Shnitzelil commented 7 years ago

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

innokenty commented 7 years ago

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.

vania-pooh commented 7 years ago

Selenium 3 has two main differences: 1) Old Selenium RC code was removed and compatibility layer is now using Selenium 2.x code base. 2) Firefox 48+ is using Geckodriver instead of uploading an XPI extension to browser.

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.