- \n
- <\/li>\n
- <\/li>\n
- <\/li>\n<\/ul>\n<\/div>\n
\r\njava -jar selenium-server-standalone-3.141.59.jar\r\n<\/pre>\n<\/div>\n
By default, Selenium Standalone Server runs on port 4444. You can use the below snippet to launch the browser.<\/p>\n
\n\n- \n
- <\/li>\n
- <\/li>\n
- <\/li>\n<\/ul>\n<\/div>\n
\r\nDesiredCapabilities capability = new DesiredCapabilities();\r\ncapability.setBrowserName("chrome");\r\n\r\nRemoteWebDriver driver = new RemoteWebDriver(new URL("http:\/\/localhost:4444\/wd\/hub"),capability);\r\n<\/pre>\n<\/div>\nSelenium Standalone Server Configuration<\/h3>\n
- \n
- BrowserTimeout<\/b> – You can use this option to make the WebDriver Browser Session wait while a WebDriver command is being executed. Let\u2019s say driver.get(url) is being executed with BrowserTimeout=60 secs. The WebDriver Session will wait for 60 secs and quit the session if the command is not complete within the given timeframe. Note: If the BrowserTimeout is not specified when starting the server, then the session will wait indefinitely if a command request does not get a response.<\/li>\n
- Config<\/b> – If you have the Standalone Server configurations in a Json file, you can use the config option to mention the json file path. If the config option is not used, it will take the default values.<\/li>\n
- Port<\/b> – As we mentioned earlier, Selenium Server\u2019s default port is 4444. If you would like to override, you can do it using the Port option.<\/li>\n
- Role – Selenium WebDriver has three roles for the server. (Standalone, Hub, and Node)<\/li>\n
- Timeout\/SessionTimeout<\/b> – The Selenium Standalone server has multiple session slots. Each slot should be released for other test executions. Let\u2019s say a session is idle for 240 seconds (i.e., The Remote WebDriver session is not receiving any commands from the client for 240 seconds). In this case, the standalone server will release the session slot for other tests. 240 seconds is not a default value. You can mention any value based on your requirement.<\/li>\n<\/ul>\n
Why Selenium Grid?<\/h3>\n
Selenium Standalone server is not sufficient for distributed execution. If you have 5 testbeds for automated test script execution, then you have to manage 5 Selenium Servers. Moreover, each server has its own URL. So you need to update the test suites with 5 server URLs as well. All of this can be easily simplified when using the Selenium Grid.<\/p>\n
Selenium Grid has only two components, one is Hub and another one is Node. All your tests point Hub. The Hub acts as a centralized server that is responsible for assigning a Node for WebDriver session initialization and command execution requests.<\/p>\n
Let\u2019s assume you have three Windows machines and one Mac machine. One of the Windows machines is used for Hub & its nodes. The other three machines (2 Windows & 1 Mac) are used for the other Node setup.<\/p>\n
Refer to the below diagram.<\/p>\n
![\"Selenium](\"https:\/\/codoid.com\/wp-content\/uploads\/2021\/01\/selenium-grid-tutorial.png\" "\\"Selenium")
<\/p>\nTo run your Selenium test scripts on Safari using a Mac machine, you can use any of the following port numbers 5564, 5565, and 5566 as per the diagram. Since this is a Selenium Grid Architecture, you can use the Hub URL instead of Node\u2019s URL.<\/p>\n
When you use the Hub URL, all the session creations and command requests will go to the Hub. The Hub will decide which node is suitable for the client request. Desired Capabilities plays a crucial role in node allocation.<\/p>\n
If you are planning to add or remove any node, you need not change the Remote URL in your test suite, because all your scripts are using Hub URL not Node URL.<\/p>\n
Selenium Grid helps you in setting up a cross-browser testing infrastructure and it eases the Selenium Server management using Hub and Node roles. When you have a simple execution architecture, you can go with the Selenium Standalone server. If you are planning for parallel execution, cross-browser testing execution, and performance test script execution on local browsers, then the Selenium Grid setup is a must.<\/p>\n
As an automation testing company<\/b>, we use Selenium Grid for multiple automation testing projects to enable parallel execution.<\/p>\n
Starting Hub<\/h3>\n
Starting a Selenium Grid Hub is easy. Just run the below command in Terminal\/Command Prompt and it will start Hub on port 4444.<\/p>\n
\n\n- \n
- <\/li>\n
- <\/li>\n
- <\/li>\n<\/ul>\n<\/div>\n
\r\njava -jar selenium-server-standalone-3.141.59.jar -role hub\r\n<\/pre>\n<\/div>\n
Hub Configuration<\/h3>\n
- \n
- Matcher\/CapabilityMatcher<\/b> – Hub has its own logic to select a node to start a WebDriver session. However, you can override this logic using the Matcher option. All you need to do is create a class and write the logic. Refer DefaultCapablityMatcher<\/a> Java class to write a custom matcher.<\/li>\n
- CleanUpCycle<\/b> – Hub needs to check & kill the idle sessions at frequent intervals. How often the cleanup needs to be carried out is determined using the CleanUpCycle option. The default value is 5000 milliseconds.<\/li>\n
- Log<\/b> – If you want all the Hub logs in a file instead of STDOUT, then pass the filename in the log option.<\/li>\n
- MaxSession<\/b> – MaxSession is used at the Hub level to mention how many WebDriver sessions are allowed in parallel on a node. The default max session at Node level is 5. If Hub has Max Session configuration, then it will override the Node\u2019s Max Session.<\/li>\n
- NewSessionWaitTimeout<\/b> – Sometimes Nodes may not be available for a new session request. You can use the NewSessionWaitTimeout option to make your test wait for the specified milliseconds instead of waiting for a Node indefinitely.<\/li>\n
- ThrowOnCapabilityNotPresent<\/b> – If ThrowOnCapabilityNotPresent=true and no node is available for the specified desired capabilities, then your test will throw an error else the test will wait until the supporting node is registered under the hub.<\/li>\n
- Registry<\/b> – Hub\u2019s Kernel logic is written in DefaultGridRegistry.java which is responsible to check free & used nodes and assign nodes to the incoming client requests. If you would like to override this logic, use the Registry option.<\/li>\n
- JettyThreads<\/b> – The default value is 200. Let\u2019s say you are going to attach 50 nodes under a Hub. Then JettyThreads=200 is not sufficient. You need to increase the JettyThreads. 50 nodes mean each node supports 5 max sessions by default. So 50 X 30 = 250 threads are required. Use JettyThreads\/JettyMaxThreads to increase the thread pool.<\/li>\n<\/ul>\n
Attaching Nodes<\/h3>\n
Once the Hub is started, you can start and attach a node from any machine. All you need is the Hub\u2019s URL.<\/p>\n
Use the below command to register a node.<\/p>\n
\n\n- \n
- <\/li>\n
- <\/li>\n
- <\/li>\n<\/ul>\n<\/div>\n
\r\njava -jar selenium-server-standalone-3.141.59.jar -role node -hub http:\/\/ip-address:4444\/grid\/register\/\r\n<\/pre>\n<\/div>\n
Node Configuration<\/h3>\n
- \n
- Capabilities<\/b> – This is an optional parameter. By default, you will get 5 Chrome, 5 Firefox, 1 Internet Explorer instance. If you want all the 11 instances as Chrome browser, then use the capabilities parameter while creating a node. Example:\n\n\n
- \n
- <\/li>\n
- <\/li>\n
- <\/li>\n<\/ul>\n<\/div>\n
\r\njava -jar selenium-server-standalone-3.141.59.jar -role node -hub http:\/\/ip-address:4444\/grid\/register\/ -capabilities browserName=Chrome, maxInstances=11\r\n<\/pre>\n<\/div>\n<\/li>\n
- NodePolling<\/b> – Hub needs to check whether the registered nodes are alive in a frequent interval. By default, Hub will check the nodes\u2019 availability every 5 seconds. <\/li>\n
- DownPollingLimit<\/b> – Let\u2019s say DownPollingLimit=3. If the node is not responding in three-node polling, then the node will be marked as Down in Hub. The default value for DownPollingLimit is 2 attempts.<\/li>\n
- Register<\/b> – This is a boolean parameter. If the Hub is unavailable, then the nodes will try to re-register with Hub. If register=false, the nodes will never try to re-register.<\/li>\n
- RegisterCycle<\/b> – How often the nodes can try to re-register with Hub is determined using the RegisterCycle parameter. The default value is 5000 milliseconds. Every 5 seconds the nodes will try to re-register if the Hub is unavailable.<\/li>\n
- UnregisterIfStillDownAfter<\/b> – If a node is down for more than 60 seconds, then the node will stop attempting to re-register with Hub. If you would like to increase\/decrease the default 60 seconds, then use the UnregisterIfStillDownAfter parameter.<\/li>\n<\/ul>\n
Grid Console<\/h3>\n
Hub and nodes creation initiated on Command Prompts\/Terminal Windows. Checking the status of Hub and Nodes in the Terminal Window is a cumbersome task. Selenium Grid has a Web GUI to view the registered nodes and Hub configuration. Once the hub has started, you can view the Hub configuration in the following Grid Console URL http:\/\/localhost:4444\/grid\/console.<\/p>\n
VisGrid<\/h3>\n
If you use VisGrid Selenium Grid UI<\/a>, you don\u2019t need to start Hub & Nodes in Command Prompt. Stopping\/Managing Hub & Nodes is easy with VisGrid. As a leading Selenium Testing Services<\/a> provider, we at Codoid created this UI to ease the Selenium Grid setup. However, after using VisGrid internally for a month, we released it as freeware. Now, VisGrid is widely used by the test automation community.<\/p>\n
You can manage multiple nodes in a single window. Moreover, Selenium Browser Drivers come with the VisGrid package.<\/p>\n
Selenium Grid 4<\/h3>\n
As we mentioned before, by using Selenium Server Jar you can setup Standalone Server and Selenium Grid Hub & Node. Hub takes care of the below-mentioned tasks.<\/p>\n
- DownPollingLimit<\/b> – Let\u2019s say DownPollingLimit=3. If the node is not responding in three-node polling, then the node will be marked as Down in Hub. The default value for DownPollingLimit is 2 attempts.<\/li>\n
- Capabilities<\/b> – This is an optional parameter. By default, you will get 5 Chrome, 5 Firefox, 1 Internet Explorer instance. If you want all the 11 instances as Chrome browser, then use the capabilities parameter while creating a node. Example:\n
- CleanUpCycle<\/b> – Hub needs to check & kill the idle sessions at frequent intervals. How often the cleanup needs to be carried out is determined using the CleanUpCycle option. The default value is 5000 milliseconds.<\/li>\n
- Matcher\/CapabilityMatcher<\/b> – Hub has its own logic to select a node to start a WebDriver session. However, you can override this logic using the Matcher option. All you need to do is create a class and write the logic. Refer DefaultCapablityMatcher<\/a> Java class to write a custom matcher.<\/li>\n
- Config<\/b> – If you have the Standalone Server configurations in a Json file, you can use the config option to mention the json file path. If the config option is not used, it will take the default values.<\/li>\n
- BrowserTimeout<\/b> – You can use this option to make the WebDriver Browser Session wait while a WebDriver command is being executed. Let\u2019s say driver.get(url) is being executed with BrowserTimeout=60 secs. The WebDriver Session will wait for 60 secs and quit the session if the command is not complete within the given timeframe. Note: If the BrowserTimeout is not specified when starting the server, then the session will wait indefinitely if a command request does not get a response.<\/li>\n