Bird
Raised Fist0
Selenium Pythontesting~15 mins

Grid architecture (hub and node) in Selenium Python - Build an Automation Script

Choose your learning style10 modes available
Verify Google Search on Selenium Grid Hub and Node
Preconditions (3)
Step 1: Open a remote Chrome browser session via Selenium Grid Hub
Step 2: Navigate to https://www.google.com
Step 3: Enter 'Selenium Grid' in the search input field
Step 4: Submit the search form
Step 5: Wait for the search results page to load
Step 6: Verify the page title contains 'Selenium Grid'
✅ Expected Result: The remote browser controlled via Selenium Grid performs a Google search and the page title contains 'Selenium Grid', confirming the test ran on the Grid setup.
Automation Requirements - Selenium WebDriver with Python
Assertions Needed:
Page title contains the search term 'Selenium Grid'
Best Practices:
Use Remote WebDriver to connect to Selenium Grid Hub
Use explicit waits to wait for page elements or title
Use By locators with clear identifiers
Close the browser session after test
Automated Solution
Selenium Python
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.common.keys import Keys
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

# URL of the Selenium Grid Hub
hub_url = 'http://localhost:4444/wd/hub'

# Desired capabilities for Chrome browser
capabilities = {
    'browserName': 'chrome'
}

# Create Remote WebDriver session
with webdriver.Remote(command_executor=hub_url, desired_capabilities=capabilities) as driver:
    wait = WebDriverWait(driver, 10)
    # Step 1: Navigate to Google
    driver.get('https://www.google.com')

    # Step 2: Find the search input field
    search_box = wait.until(EC.presence_of_element_located((By.NAME, 'q')))

    # Step 3: Enter search term and submit
    search_term = 'Selenium Grid'
    search_box.send_keys(search_term + Keys.RETURN)

    # Step 4: Wait for title to contain search term
    wait.until(EC.title_contains(search_term))

    # Step 5: Assert title contains search term
    assert search_term in driver.title, f"Expected '{search_term}' in title but got '{driver.title}'"

    # Browser will close automatically due to 'with' context

This script connects to the Selenium Grid Hub running locally on port 4444 using webdriver.Remote. It requests a Chrome browser session on a registered Node.

We use explicit waits (WebDriverWait) to wait for the Google search input to appear and then for the page title to update after submitting the search.

The assertion checks that the page title contains the search term 'Selenium Grid', confirming the search worked and the test ran on the Grid.

Using the with statement ensures the browser session closes cleanly after the test.

Common Mistakes - 4 Pitfalls
Using local WebDriver instead of Remote WebDriver to connect to Grid
Hardcoding implicit sleeps instead of using explicit waits
Using brittle locators like absolute XPath for search input
Not closing the browser session after test
Bonus Challenge

Now add data-driven testing with 3 different search terms: 'Selenium Grid', 'Python testing', 'WebDriver automation'

Show Hint

Practice

(1/5)
1. What is the main role of the hub in Selenium Grid architecture?
easy
A. To run the browser instances directly
B. To store test results locally
C. To receive test requests and distribute them to the appropriate nodes
D. To act as a database for test data

Solution

  1. Step 1: Understand the hub's function in Selenium Grid

    The hub acts as a central point that receives test requests from clients.
  2. Step 2: Identify how the hub manages nodes

    The hub distributes these requests to the right nodes that have the required browser and platform.
  3. Final Answer:

    To receive test requests and distribute them to the appropriate nodes -> Option C
  4. Quick Check:

    Hub controls nodes [OK]
Hint: Hub directs tests to nodes, it doesn't run browsers itself [OK]
Common Mistakes:
  • Thinking the hub runs browsers directly
  • Confusing hub with node responsibilities
  • Assuming hub stores test data
2. Which of the following is the correct command to start a Selenium Grid hub using the Selenium Server jar file?
easy
A. java -jar selenium-server.jar -role hub
B. java -jar selenium-server.jar -role node
C. java -jar selenium-server.jar -start hub
D. java -jar selenium-server.jar -node start

Solution

  1. Step 1: Recall the command syntax for starting a hub

    The correct command uses '-role hub' to specify the hub role.
  2. Step 2: Compare options with correct syntax

    java -jar selenium-server.jar -role hub matches the correct syntax: 'java -jar selenium-server.jar -role hub'.
  3. Final Answer:

    java -jar selenium-server.jar -role hub -> Option A
  4. Quick Check:

    Hub starts with '-role hub' flag [OK]
Hint: Hub uses '-role hub' flag in command [OK]
Common Mistakes:
  • Using '-role node' instead of '-role hub'
  • Incorrect flag order or spelling
  • Using '-start' or '-node start' which are invalid
3. Given the following Selenium Grid setup code snippet, what will be the output when the test runs?
from selenium import webdriver
from selenium.webdriver.common.desired_capabilities import DesiredCapabilities

hub_url = "http://localhost:4444/wd/hub"
driver = webdriver.Remote(command_executor=hub_url, desired_capabilities=DesiredCapabilities.CHROME)
print(driver.capabilities['browserName'])
driver.quit()
medium
A. safari
B. firefox
C. edge
D. chrome

Solution

  1. Step 1: Analyze the desired capabilities used

    The code requests a Chrome browser by using DesiredCapabilities.CHROME.
  2. Step 2: Understand the output of driver.capabilities['browserName']

    This returns the name of the browser the remote driver is connected to, which should be 'chrome'.
  3. Final Answer:

    chrome -> Option D
  4. Quick Check:

    DesiredCapabilities.CHROME = 'chrome' output [OK]
Hint: DesiredCapabilities.CHROME means browserName is 'chrome' [OK]
Common Mistakes:
  • Assuming default browser is Firefox
  • Confusing capability keys
  • Not quitting driver causing errors
4. You started a Selenium Grid node with the command:
java -jar selenium-server.jar -role node -hub http://localhost:4444/grid/register
But the node is not registering with the hub. What is the most likely cause?
medium
A. The hub URL is incorrect or the hub is not running
B. The node command should use '-role hub' instead of '-role node'
C. The selenium-server.jar file is corrupted
D. The node must be started before the hub

Solution

  1. Step 1: Check the hub URL and hub status

    If the node cannot register, often the hub URL is wrong or the hub is not running.
  2. Step 2: Verify command correctness

    The command uses '-role node' correctly; the jar file corruption or start order is less common causes.
  3. Final Answer:

    The hub URL is incorrect or the hub is not running -> Option A
  4. Quick Check:

    Node needs correct hub URL and running hub [OK]
Hint: Check hub URL and hub running status first [OK]
Common Mistakes:
  • Mixing up node and hub roles in commands
  • Assuming jar file corruption without evidence
  • Starting node before hub is usually okay
5. You want to run tests on multiple browsers simultaneously using Selenium Grid. Which setup correctly describes how the hub and nodes should be configured?
hard
A. Multiple nodes running on the same machine without a hub
B. One hub running on a central machine, multiple nodes registered with different browsers on different machines
C. One node running multiple hubs, each controlling a browser
D. Multiple hubs running on different machines, each with one node registered

Solution

  1. Step 1: Understand Selenium Grid architecture

    The hub acts as a central controller, and nodes register to it with different browsers.
  2. Step 2: Identify correct multi-browser setup

    Multiple nodes on different machines with different browsers register to one hub to run tests in parallel.
  3. Final Answer:

    One hub running on a central machine, multiple nodes registered with different browsers on different machines -> Option B
  4. Quick Check:

    Single hub, multiple nodes with browsers [OK]
Hint: Hub central, nodes distributed with browsers [OK]
Common Mistakes:
  • Thinking multiple hubs are needed for parallel tests
  • Confusing roles of hub and node
  • Running nodes without a hub
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard