Upgrade & Secure Your Future with DevOps, SRE, DevSecOps, MLOps!

We spend hours on Instagram and YouTube and waste money on coffee and fast food, but won’t spend 30 minutes a day learning skills to boost our careers.
Master in DevOps, SRE, DevSecOps & MLOps!

Learn from Guru Rajesh Kumar and double your salary in just one year.


Get Started Now!

SQL

How to run a selenium-server-standalone and grid/hub mode?

July 2, 2020 comments off

What is Selenium Server (Grid)?
The Selenium Server is needed in order to run Remote Selenium WebDriver (Grid).

Download Location – Click Here
https://www.selenium.dev/downloads/

As per GridRole class – Selenium server can run in one of the following roles:

  • NOT_GRID [If -role option is omitted the server runs standalone not being a part of a grid]>
  • HUB [as a hub of a Selenium grid]
  • NODE [as a node of a Selenium grid]

NOT_GRID RC (Selenium interface)- IP:Port/selenium-server:

Selenium Remote Control (RC) requires server to be started before executing the test scripts. RC server injects Selenium core (JavaScript) into the browser. The core (daemon process) receives commands from the server by your test scripts and executes them in a browser then results to your program. But cannot handle moving mouse cursors & mobile execution.

Java Client Driver: Client-Configures your browser to use the Selenium Server as an HTTP proxy and passes browser commands to server through “/selenium-server/RemoteRunner.html?sessionId=1234”, clients may send Driver Command requests to selenium server over HTTP as follows:

Code & Requests: RC Server continuously runs. we create a daemon and from that communicate with the browser.

# As of 3.8.1, specifying the driver is no longer necessary:
$ java -jar seleniumjar.jar
$ java -jar seleniumjar.jar -Dwebdriver.chrome.driver=./chromedriver 

If you want to specifiy the port do
$ java -jar seleniumjar.version.jar -Dwebdriver.chrome.driver=./chromedriver -port 4545

HUB – Grid HUB Running as a standalone server:

Hub is a central point which distributing tests on several node-machines, which are registered to it for parallel execution.

$ java -jar selenium-server-standalone-2.53.0.jar -host 127.0.0.1 -port 4454 -role hub -log "D:\\HUB_Log.txt"

Grid: [ - IP:Port/grid/console]

NODE – [RC] has to post a request to HUB in order to register with it, by this URL – IP:Port//grid/register



$ java -jar selenium-server-standalone-2.53.0.jar -host 127.0.0.1 -port 4458 -role node 
-hub http://127.0.0.1:4454/grid/register -hubHost 127.0.0.1 -hubPort 4454 
-browser browserName=firefox,version=24.0, maxinstance=1,platform=WINDOWS7 
-browser  browserName=chrome,version=53.0,platform=WINDOWS 
-Dwebdriver.chrome.driver=D:\\Drivers\\chromedrivers\.24\\chromedriver.exe

$ D:\SeleniumJar_Source>java -jar selenium-server-standalone-2.53.0.jar -role node 
-hub http://127.0.0.1:4454/grid/register 
-nodeConfig registerNode.json 
-Dwebdriver.chrome.driver="D:\\Drivers\\chromedrivers\.24\\chromedriver.exe" 
-Dwebdriver.ie.driver="D:\\Drivers\\IEDrivers\\iedriver64\\IEDriverServer.exe" 
-Dwebdriver.firefox.logfile="D:\\FirefoxInstance.txt" 
-Dwebdriver.chrome.logfile="D:\\ChromeInstance.txt" 
-Dwebdriver.ie.logfile="D:\\IEInstance.txt"