selenium-grid | Selenium Grid is a tool that dramatically speeds | Functional Testing library

There are multiple problems with your code. In a nutshell, you are hardcoding a lot of the OS platform information only in your Desired Capabilities object that you are using to create the WebDriver but the Grid Hub is not having those changes.

I also noticed that your code base is trying to talk to a hub running in a different port but your hub is running in a different port.

I also noticed that your test code is not waiting for the Node to be registered to the hub. I have as a quick hack added a sleep to facilitate that, but you can employ sophisticated mechanisms such as polling the hub to see if the node is registered or not etc.,

You need to create a patch file with the below git diff contents and then you can apply it to your codebase.

Here's a git diff that you can apply to your project to fix the problem

You need to add the environment variable NODE_MAX_CONCURRENT_SESSIONS for the node you would like to set the concurrency for.. For example:

The process is similar to what you are doing locally.

The only thing you have to make sure of is that the grid is accessible in the runner container from where the execution is happening. For running the maven command, ensure your runner container has required tools like JDK and maven installed and appropriate environment variables like JAVA_HOME, etc.., are setup.