Everything depends on the capabilities of node, below json file shows the seleniumProtocol values and based on that it reflects the RCs and Webdrivers on grid.
"capabilities":
[
{
"browserName": "*firefox",
"maxInstances": 2,
"seleniumProtocol": "Selenium"
},
{
"browserName": "*googlechrome",
"maxInstances": 2,
"seleniumProtocol": "Selenium"
},
{
"browserName": "*iexplore",
"maxInstances": 1,
"seleniumProtocol": "Selenium"
},
{
"browserName": "firefox",
"maxInstances": 5,
"seleniumProtocol": "WebDriver"
},
{
"browserName": "chrome",
"maxInstances": 5,
"seleniumProtocol": "WebDriver"
},
{
"browserName": "internet explorer",
"maxInstances": 1,
"seleniumProtocol": "WebDriver"
}
Always shows both RC
and webdriver
instances on grid whether we given node or webdriver
on command line
-role webdriver
parameter is required from version 3.8 I believe onwards; if you just used the standalone server as a hub+node. The difference is that a-role hub
can connect your client, to any of multiple nodes, (-role node
which must register or point to the-role hub
machine) it then becomes a grid or farm. This all changes in Selenium 4 where things get less "hard-coded" to manage multiple nodes. selenium.dev/documentation/en/grid – Milwaukee