selenium-server-standalone | Composer distribution of Selenium Server Standalone | Automation library

When launching nodes:

So I found out what was wrong and I am posting the answer in case somebody else had similar problems:

It turns out there was nothing wrong with Selenium or Windows Terminal, we had to start using the latest stable release of Selenium Grid (we were still using 3.x.x version because it was the only one supported for a long time and only recently they released 4.x.x version) + change the scripts, because Selenium developers decided to change the switches in between versions, so the old scripts (posted in the question itself) will not work, and had to be updated like this:

The RSelenium package enables to remote control the comon web browsers from R. The following code opens a remote browser session in mozilla firefox(chrome should work as well) and works the login screen - with the correct usr and pw the next page will open. As I do not have access to the closed part I can not try nor debug my code after the login screen click so I just showed one upload:

You have to pass the driver location while registering node to hub.

You need to start your nodes without any additional path after server port. See documentation.

Sou your command would be:

FYI if you are using a go modules build - you are no longer using GOPATH - so that is not the issue.

If you want a custom build - and not have to create laborious git key access to repo's from within a docker build - you can leverage the replace directive in go.mod

So add to .../webCopy/go.mod the following line:

You are missing the most important part in your dockerfile. You need to copy all the files over into the container. You are running mkdir and then immediately running npm install but there is nothing in your protractor directory. It's empty.

What I will suggest is to create a create a new file for Nightwatch.conf.js and then start adding rest of the configuration from there. Below is an example which works for me:

These are only applicable when running on Flood - you will need to provide the Host and Port of your local Selenium WebDriver instance to test locally. you could even use instead of remote driver the following to run on your local:

WebDriver driver;