Grid setup and configuration in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Selenium Grid Hub Role

What is the primary role of the Selenium Grid Hub in a grid setup?

A It directly controls browser instances without nodes.

B It manages test scripts and executes them on local browsers only.

C It stores test results and logs for all nodes in the grid.

D It acts as a central point to receive test requests and distribute them to registered nodes.

💡 Hint

Think about how tests are distributed in a grid.

The Hub acts as a central server that receives test requests and routes them to the appropriate nodes based on capabilities.

❓ Predict Output

intermediate

Node Registration Command Output

What will be the output when running this command to register a node to the Selenium Grid Hub?

java -jar selenium-server.jar node --hub http://localhost:4444 --port 5555

Selenium Python

java -jar selenium-server.jar node --hub http://localhost:4444 --port 5555

A Error: Hub URL is missing or incorrect.

B Syntax error: Missing required parameters for node registration.

C Node successfully registered to the hub at http://localhost:4444 on port 5555.

D Node started but failed to register due to port conflict.

💡 Hint

Check if the hub URL and port are correctly specified.

The command correctly specifies the hub URL and node port, so the node will register successfully.

❓ locator

advanced

Best Locator for Node Status in Grid Console

Which locator is best to find the status element of a registered node in the Selenium Grid console HTML page?

A By.id('nodeStatus')

B By.cssSelector('div.node-status')

C By.className('status')

D By.xpath('//span[contains(text(), "Node Status")]')

💡 Hint

Consider specificity and stability of locators in dynamic pages.

Using a CSS selector targeting a specific div with class 'node-status' is precise and less brittle than text-based XPath or generic class names.

❓ assertion

advanced

Correct Assertion for Node Registration Verification

Which assertion correctly verifies that a node is registered and ready in Selenium Grid using Python unittest?

Selenium Python

status = driver.find_element(By.CSS_SELECTOR, 'div.node-status').text

A self.assertIn('Ready', status)

B self.assertTrue(status == 'Ready')

C self.assertEqual(status, 'Ready')

D self.assertIsNotNone(status)

💡 Hint

Check if the status text might contain extra spaces or additional info.

Using assertIn allows matching 'Ready' even if the status text contains extra details or whitespace.

❓ framework

expert

Handling Node Failures in Selenium Grid Tests

In a Selenium Grid setup, which approach best handles unexpected node failures during test execution to ensure test reliability?

A Implement retry logic in the test framework to rerun failed tests on available nodes.

B Ignore node failures and continue tests on the same node without retries.

C Manually restart the node and rerun all tests from the beginning.

D Use fixed node allocation without dynamic rerouting of tests.

💡 Hint

Think about automation and minimizing manual intervention.

Retrying failed tests automatically on available nodes improves reliability and reduces manual effort.

Practice

1. What is the main purpose of Selenium Grid in test automation?

easy

A. To generate test reports automatically

B. To run tests on multiple browsers and machines simultaneously

C. To debug test scripts locally

D. To write test scripts faster

Solution

1. Step 1: Understand Selenium Grid's role

   Selenium Grid allows running tests on different browsers and machines at the same time to save time and increase coverage.

2. Step 2: Compare options with Grid's purpose

   Only To run tests on multiple browsers and machines simultaneously describes running tests on multiple browsers and machines simultaneously, which is the core feature of Selenium Grid.

3. Final Answer:

   To run tests on multiple browsers and machines simultaneously -> Option B

4. Quick Check:

   Selenium Grid = Run tests on many browsers/machines [OK]

Hint: Remember Grid = multiple browsers + machines running tests [OK]

Common Mistakes:

• Confusing Grid with test script writing tools
• Thinking Grid generates reports
• Assuming Grid is for debugging only

2. Which Python code snippet correctly creates a Remote WebDriver to connect to a Selenium Grid hub at 'http://localhost:4444/wd/hub' for Chrome browser?

easy

A. driver = webdriver.Remote(command_executor='http://localhost:4444/wd/hub', desired_capabilities={'browserName': 'chrome'})

B. driver = webdriver.Chrome('http://localhost:4444/wd/hub')

C. driver = webdriver.Remote('chrome', 'http://localhost:4444/wd/hub')

D. driver = webdriver.Remote('http://localhost:4444/wd/hub', browser='chrome')

Solution

1. Step 1: Check Remote WebDriver syntax

   webdriver.Remote requires 'command_executor' URL and 'desired_capabilities' dictionary specifying browser.

2. Step 2: Validate each option

   driver = webdriver.Remote(command_executor='http://localhost:4444/wd/hub', desired_capabilities={'browserName': 'chrome'}) correctly uses command_executor and desired_capabilities with browserName 'chrome'. Others misuse parameters or classes.

3. Final Answer:

   driver = webdriver.Remote(command_executor='http://localhost:4444/wd/hub', desired_capabilities={'browserName': 'chrome'}) -> Option A

4. Quick Check:

   Remote WebDriver needs command_executor + desired_capabilities [OK]

Hint: Use command_executor and desired_capabilities keys for Remote [OK]

Common Mistakes:

• Using webdriver.Chrome instead of webdriver.Remote
• Passing URL as first argument without keyword
• Incorrect parameter names like 'browser' instead of 'desired_capabilities'

3. Given this Python code connecting to Selenium Grid:

from selenium import webdriver
caps = {'browserName': 'firefox'}
driver = webdriver.Remote(command_executor='http://localhost:4444/wd/hub', desired_capabilities=caps)
driver.get('https://example.com')
print(driver.title)

What will be printed if the Grid and node are correctly set up?

medium

A. Empty string

B. An error about missing local browser

C. The title of the page at https://example.com

D. SyntaxError

Solution

1. Step 1: Understand code execution with Grid

   The code uses Remote WebDriver to open Firefox on Grid node and navigates to example.com.

2. Step 2: Predict output of print(driver.title)

   If Grid and node are correct, driver.title returns the page title of example.com, which is a string like 'Example Domain'.

3. Final Answer:

   The title of the page at https://example.com -> Option C

4. Quick Check:

   Remote driver prints page title when setup is correct [OK]

Hint: Correct Grid setup means driver.title shows page title [OK]

Common Mistakes:

• Expecting local browser errors when Grid is correct
• Thinking driver.title returns empty string by default
• Confusing syntax errors with runtime behavior

4. You wrote this code to connect to Selenium Grid but get a connection error:

driver = webdriver.Remote('http://localhost:4444/wd/hub', {'browserName': 'chrome'})

What is the likely cause and how to fix it?

medium

A. Missing keyword arguments; use command_executor and desired_capabilities keywords

B. Wrong URL; should be 'http://localhost:5555/wd/hub'

C. Browser name must be uppercase 'Chrome'

D. webdriver.Remote does not support Chrome browser

Solution

1. Step 1: Identify correct webdriver.Remote syntax

   webdriver.Remote requires keyword arguments: command_executor for URL and desired_capabilities for browser info.

2. Step 2: Analyze given code

   Code passes URL and capabilities as positional arguments without keywords, causing connection error.

3. Final Answer:

   Missing keyword arguments; use command_executor and desired_capabilities keywords -> Option A

4. Quick Check:

   webdriver.Remote needs command_executor and desired_capabilities keywords [OK]

Hint: Always use command_executor and desired_capabilities keywords [OK]

Common Mistakes:

• Passing URL and capabilities as positional args
• Changing URL port without reason
• Incorrect browser name casing

5. You want to run tests on both Chrome and Firefox browsers using Selenium Grid. Which approach correctly sets up the test to run on both browsers sequentially using Python?

hard

A. Create one Remote WebDriver with both browser names in desired_capabilities at once

B. Start two Grid hubs, one for Chrome and one for Firefox, and connect separately

C. Run tests locally on Chrome and Firefox without Grid

D. Use a loop over a list of desired capabilities and create a Remote WebDriver for each browser inside the loop

Solution

1. Step 1: Understand how to run tests on multiple browsers with Grid

   Each Remote WebDriver instance connects to one browser session. To test multiple browsers, create separate instances.

2. Step 2: Evaluate options

   Use a loop over a list of desired capabilities and create a Remote WebDriver for each browser inside the loop correctly uses a loop to create Remote WebDriver for each browser sequentially. Create one Remote WebDriver with both browser names in desired_capabilities at once is invalid because desired_capabilities cannot hold multiple browsers at once.

3. Final Answer:

   Use a loop over a list of desired capabilities and create a Remote WebDriver for each browser inside the loop -> Option D

4. Quick Check:

   Loop over browsers, create Remote driver each time [OK]

Hint: Loop browsers, create Remote driver per browser session [OK]

Common Mistakes:

• Trying to set multiple browsers in one desired_capabilities dict
• Running tests locally instead of using Grid
• Starting multiple hubs unnecessarily