Public | Automated Build

Last pushed: a month ago
Short Description
Short description is empty for this repo.
Full Description

Selenium Grid Hub

The Hub receives a test to be executed along with information on which browser and 'platform' where the test should be run. The hub will use this information and delegate to a node that can service those needs.

Dockerfile

selenium/hub Dockerfile

How to use this image

$ docker run -d -P --name selenium-hub selenium/hub

Note: You can optionally override default configuration settings using environment variables.
See the Hub's Dockerfile to view the list of variables and their default values.

$ docker run -d -P --name selenium-hub -e GRID_TIMEOUT=10 selenium/hub

Once the hub is up and running will want to launch nodes that can run tests. You can run as many nodes as you wish.

$ docker run -d --link selenium-hub:hub selenium/node-chrome
$ docker run -d --link selenium-hub:hub selenium/node-firefox

What is Selenium?

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.

Selenium has the support of some of the largest browser vendors who have taken (or are taking) steps to make Selenium a native part of their browser. It is also the core technology in countless other browser automation tools, APIs and frameworks.

See the Selenium site for documation on usage within your test code.

License

View license information for the software contained in this image.

Getting Help

User Group

The first place where people ask for help about Selenium is the Official User Group. Here, you'll find that most of the time, someone already found the problem you are facing right now, and usually reached the solution for which you are looking.

Note: Please make sure to search the group before asking for something. Your question likely won't get answered if it was previously answered in another discussion!

Chat Room

The best place to ask for help is the user group (because they also keep the information accessible for others to read in the future). However, if you have a very important (or too simple) issue that needs a solution ASAP, you can always enter the IRC chat room. You might just find someone ready to help on #selenium at Freenode.

Issues

If you have any problems with or questions about this image, please contact us through a Github issue. If you have any problems with or questions about Selenium, please contact us through Selenium's Bug Tracker.

Contributing

There are many ways to contribute whether by answering user questions, additional docs, or pull request we look forward to hearing from you.

If you do supply a patch we will need you to sign the CLA. We are part of SFC

Docker Pull Command
Owner
selenium
Source Repository

Comments (4)
polimediaupv
4 months ago

I start the hub and a node like the instructions says:

$ docker run -d -P --name selenium-hub selenium/hub
$ docker run -d --link selenium-hub:hub selenium/node-chrome

but I see this in the hub log:

12:40:27.545 INFO - Selenium Grid hub is up and running
12:40:33.186 INFO - Registered a node http://172.17.0.5:5555
12:40:43.527 INFO - Marking the node http://172.17.0.5:5555 as down: cannot reach the node for 2 tries
12:41:43.658 INFO - Unregistering the node http://172.17.0.5:5555 because it's been down for 60131 milliseconds
12:41:43.659 WARN - Cleaning up stale test sessions on the unregistered node http://172.17.0.5:5555
12:41:48.363 INFO - Registered a node http://172.17.0.5:5555
12:41:58.396 INFO - Marking the node http://172.17.0.5:5555 as down: cannot reach the node for 2 tries
12:42:58.498 INFO - Unregistering the node http://172.17.0.5:5555 because it's been down for 60102 milliseconds
12:42:58.498 WARN - Cleaning up stale test sessions on the unregistered node http://172.17.0.5:5555
12:43:03.515 INFO - Registered a node http://172.17.0.5:5555
12:43:13.541 INFO - Marking the node http://172.17.0.5:5555 as down: cannot reach the node for 2 tries

How can i solve this?

at88mph
9 months ago

In case anyone is using docker compose and still using links and needs to update, add the:

    environment:
      - "HUB_PORT_4444_TCP_ADDR=<HUB_NAME>"
      - "HUB_PORT_4444_TCP_PORT=4444"

to your nodes, and replace HUB_NAME with the name of your hub service. I've just upgrade and I couldn't find this documented anywhere.

rajivbhati12
9 months ago

Thanks this is exactly what I was looking for

rodrigojmartin
2 years ago

Thank you guys!