Skip to content
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

Selenium python test against selenium grid created from SeleniumHQ docker images #521

Closed
namgivu opened this issue Jul 16, 2017 · 4 comments

Comments

@namgivu
Copy link

namgivu commented Jul 16, 2017

Today I failed to run tests against selenium grid i.e. the sub+node containers - though I can run the same test with the standalone one

My demo test can view here

Would be lovely as you may show me how to get a test run against the grid!

Thank you,
Nam

p.s. I also asked on stackoverflow here
https://stackoverflow.com/q/45127482/248616

@lmtierney
Copy link
Member

lmtierney commented Jul 17, 2017

I'm guessing you're running into SeleniumHQ/selenium#3808. For python you can downgrade to 3.3.1 (that's bindings, not grid) until the fix for that is released.

@namgivu
Copy link
Author

namgivu commented Jul 17, 2017

Confirmed that my test works now after installing python selenium 3.3.1

pip uninstall selenium ; pip install selenium==3.3.1

@qiuyimo
Copy link

qiuyimo commented Jul 18, 2017 via email

@VireshDoshi
Copy link

Hi
my setup: centos7, docker-compose, python 2.7, virtualenv, selenium==3.9.0
I have the latest selenium grid up and running ( version: 3.9.1-actinium ) but it failed to run a test against the selenium grid. The following did the trick! :-)
$ pip uninstall selenium ; pip install selenium==3.3.1

@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants