While setting up Selenium Grid:
Windows as Hub
Mac as Node
While registering node in mac, the below error is displayed:
Couldn't register this node: The hub is down or not responding: The hub responded with 305: Use Proxy
Note:
(1) Able to setup Selenium Grid successfully, By
-> Windows as Hub and Node
-> Mac as Hub and Node.
-> Mac as Hub and Windows as Node
(2) Able to connect RDP from Windows to Mac
Related
So I'm trying to setup an automated build and test flow, with Jenkins and Selenium grid on a central EC2-instance and nodes on physical machines located at my office.
I don't have port forwarding available at my office.
So I was thinking that I could use a VPN (not a proxy) to connect the machines, as though they were on the same network.
So my setup is currently:
The hub (EC2) with Wireguard
java -jar selenium-server-4.7.2.jar hub --host 0.0.0.0 --allow-cors true --bind-host false
A linux-laptop node
java -jar selenium-server-4.7.2.jar node --hub http://<wireguard-hub>:4444 --host <wireguard-ip> --port 5555 --bind-host false
A windows desktop node
java -jar selenium-server-4.7.2.jar node --hub http://<wireguard-hub>:4444 --host <wireguard-ip> --port 5555 --bind-host false
The nodes are able to do a GET-request to the hub and get a proper json response and the hub is able to do the opposite. But the Selenium software get stuck on [NodeServer$1.lambda$start$1] - Sending registration event....
I've tried running all parties with --log-level FINEST, but all I see is that the hub isn't receiving the request. Both from linux and windows.
I've tried running both nodes as hubs too and they are able to connect to themselves, but not each other (through WireGuard).
So can anyone tell me why I can, but at the same time can't, connect my grid?
EDIT (4. jan 2022):
I have now tried running the node on the same EC2-instance with docker as the Webdriver and that doesn't work either.
The node starts, connects to docker and gets stuck at the same spot.
This (in my mind) points to it being an issue with the EC2-instance.
For now I'll be running it in standalone mode, to get the rest of the pipeline working.
I am running the Selenium Grid Server on my Mac and I'm trying to add my Raspberry Pi as a node to it with the command:
java -jar selenium-server.jar node --detect-drivers true --publish-events tcp://192.168.3.45:4442 --subscribe-events tcp://192.168.3.45:4443
On the Pi it keeps logging out "Sending registration event..." and on the Mac in the Selenium event bus it says io.netty.channel.ConnectTimeoutException: connection timed out: /169.254.110.233:5555
Does anyone have an idea why it's saying this or has anyone been able to add a Pi as a Selenium node?
I'm trying to connect 2 vm machines with each other (running both on win10).
I've downloaded java JDK 15 and
selenium-server-4.0.0-alpha-6.jar
I'm running my hub, copying the TCP URL I get there (tcp://hub:4442/3) to my second machine.
But after running the node command I'm getting this message:
Starting registration process for node ID X
and everything hangs...
I've tried testing if there is a connection using Test-NetConnection and it seems that there is communication between them
How can I debug this?
OK found the solution.
It seems that in alpha 6, if you don't have a browser web driver installed it won't work
I'm trying to execute automation scripts using selenium grid
But in hub there is no node request is sent when hub machine windows firewall is enabled
Im using hub machine as master & nodes are 2 different machines
I would like to check my selenium grid test cases on a server(any machine other than localhost).I need chrome , firefox and IE browsers in the server. Is there any way to do this ? I checked few sites like koding.com , but it is only offering me unix interface,I need full windows/Ubuntu interface.
Please let me know if there is any other method to execute my test cases ?
VirtualBox is good and works well for grid tests, I expect it to be a fairly common solution. Same IP is not a problem as you make it work with port forwarding on your desktop. For example you should manage to build a grid like the following:
-role hub on your Windows host on port 4444
-role node on an Ubuntu VM with port forward 5556 in VirtualBox, for Firefox
-role node on an OSX VM with port forward 5557 in VirtualBox, for Safari
-role node on a Windows VM with port forward 5558 in VirtualBox, for IE and Chrome
node with socat+flynnid.py on an Android emulator with port forward 5559
maybe also iPhone Simulator from inside OSX VM (I don't remember if I made it work with grid)
The Selenium Grid "user interface" as you say, is the same , whether it is Linux or Windows. The only difference is that on Linux you won't have an IE driver.
What you do is run a Grid Hub on your local machine and then register "Node" servers on each remote machine. Each Node server can run any combination of web browsers that you mentioned and it is also capable of running them simultaneously (if your test suite was programmed carefully).
The .jar file that you start the Grid Hub with is the same .jar file you use to start the Nodes. The only difference is that each Node will have a .json config file with it that explains the configuration of that server such as where the IE and Chrome binary files are located at on the remote server, what browsers it supports, and how many threads it can handle.
Look at the documentation I wrote (for Grid hub config) on the GitHub "Selenium documentation" site.