Selenium Grid setup in Selenium Java - Framework Patterns

Framework Mode - Selenium Grid setup

Folder Structure for Selenium Grid Project

selenium-grid-project/
├── src/
│   └── test/
│       └── java/
│           ├── config/           # Grid and browser configuration classes
│           ├── pages/            # Page Object Model classes
│           ├── tests/            # Test classes using TestNG or JUnit
│           └── utils/            # Utility classes (e.g., WebDriver factory)
├── resources/
│   ├── grid-config.properties    # Grid hub and node URLs, browser settings
│   └── testdata/                 # Test data files
├── pom.xml                      # Maven dependencies and build config
└── README.md                    # Project overview and setup instructions
  

Test Framework Layers in Selenium Grid Setup

• Configuration Layer: Holds Grid hub URL, node details, browser capabilities in properties or config classes.
• Driver Factory Layer: Creates RemoteWebDriver instances connecting to Selenium Grid with desired capabilities.
• Page Object Layer: Encapsulates web page elements and actions for reusability and readability.
• Test Layer: Contains test classes that use Page Objects and Driver Factory to run tests on Grid nodes.
• Utility Layer: Helper methods for waits, logging, screenshots, and other reusable functions.

Configuration Patterns for Selenium Grid

• Use a grid-config.properties file to store Grid hub URL, browser types, and versions.
• Load configuration in a dedicated Config class to centralize environment setup.
• Use DesiredCapabilities or BrowserOptions to specify browser and platform for each test.
• Support multiple environments (e.g., dev, staging) by having separate config files or profiles.
• Secure sensitive data like credentials using environment variables or encrypted files, not hardcoded.

Test Reporting and CI/CD Integration

• Integrate TestNG or JUnit reports for detailed test execution results.
• Use Allure or ExtentReports for rich, interactive HTML reports with screenshots.
• Configure CI/CD pipelines (Jenkins, GitHub Actions) to trigger tests on code changes.
  • Start Selenium Grid hub and nodes as part of pipeline or use cloud Grid services.
  • Publish test reports as build artifacts for easy access.
• Use logs and screenshots on failure to help debug issues on remote nodes.

Best Practices for Selenium Grid Setup

• Use Page Object Model: Keep UI locators and actions separate from tests for maintainability.
• Implement Explicit Waits: Avoid flaky tests by waiting for elements properly before actions.
• Centralize Configuration: Manage Grid URLs and browser capabilities in one place for easy updates.
• Use RemoteWebDriver Factory: Create WebDriver instances dynamically based on config to support parallel tests.
• Run Tests in Parallel: Leverage Grid to run tests on multiple nodes simultaneously to save time.

Self-Check Question

Where in this folder structure would you add a new Page Object class for the Login page?

Key Result

Use a layered Selenium Grid framework with centralized config, RemoteWebDriver factory, Page Objects, and parallel test execution.

Practice

1. What is the primary role of the Selenium Grid Hub in a test setup?

easy

A. To create test data for automation

B. To execute test scripts locally on the machine

C. To manage and distribute test requests to connected Nodes

D. To store test results and logs

Solution

1. Step 1: Understand the Hub's function

   The Hub acts as a central point that receives test requests and sends them to the appropriate Nodes.

2. Step 2: Differentiate Hub from Nodes

   Nodes are the machines that actually run the tests, while the Hub manages these Nodes and distributes tests.

3. Final Answer:

   To manage and distribute test requests to connected Nodes -> Option C

4. Quick Check:

   Hub manages test distribution = D [OK]

Hint: Hub manages tests; Nodes run tests [OK]

Common Mistakes:

• Confusing Hub with Node
• Thinking Hub runs tests locally
• Assuming Hub stores test data

2. Which of the following is the correct way to start a Selenium Grid Hub using the command line?

easy

A. java -jar selenium-server.jar hub

B. java -jar selenium-server.jar node

C. java -jar selenium-server.jar start

D. java -jar selenium-server.jar run

Solution

1. Step 1: Identify the command to start the Hub

   The command to start the Hub is 'java -jar selenium-server.jar hub'.

2. Step 2: Differentiate Hub and Node commands

   'node' starts a Node, not the Hub. 'start' and 'run' are invalid commands here.

3. Final Answer:

   java -jar selenium-server.jar hub -> Option A

4. Quick Check:

   Hub starts with 'hub' argument = A [OK]

Hint: Use 'hub' to start Hub, 'node' for Nodes [OK]

Common Mistakes:

• Using 'node' instead of 'hub' to start Hub
• Using invalid commands like 'start' or 'run'
• Omitting 'java -jar' part

3. Given the following Java code snippet for Selenium Grid, what will be the output if the Hub URL is incorrect?

RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wrongpath"), new ChromeOptions());
driver.get("https://example.com");

medium

A. SessionNotCreatedException at runtime

B. org.openqa.selenium.WebDriverException: Unable to connect to Grid Hub

C. MalformedURLException at compile time

D. No output, test runs successfully

Solution

1. Step 1: Analyze the URL used for RemoteWebDriver

   The URL "http://localhost:4444/wrongpath" is incorrect for the Grid Hub endpoint.

2. Step 2: Understand the error caused by wrong Hub URL

   RemoteWebDriver will throw a WebDriverException because it cannot connect to the Hub at the wrong URL.

3. Final Answer:

   org.openqa.selenium.WebDriverException: Unable to connect to Grid Hub -> Option B

4. Quick Check:

   Wrong Hub URL causes connection error = B [OK]

Hint: Wrong Hub URL causes connection failure error [OK]

Common Mistakes:

• Expecting compile-time error for URL string
• Confusing SessionNotCreatedException with connection error
• Assuming test runs despite wrong URL

4. Identify the error in the following Selenium Grid Node registration command:

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

medium

A. The port number 5555 is invalid for Nodes

B. The '--hub' URL should not include '/hub' at the end

C. The command is correct and will register the Node successfully

D. The '--role node' option is unnecessary and causes error

Solution

1. Step 1: Review the Node registration command syntax

   The '--role node' option is not required and may cause errors because 'node' is implied by the command.

2. Step 2: Check other parts of the command

   The '--hub' URL including '/hub' is correct, and port 5555 is valid for Nodes.

3. Final Answer:

   The '--role node' option is unnecessary and causes error -> Option D

4. Quick Check:

   '--role node' is redundant and wrong = C [OK]

Hint: Avoid '--role node' when starting Nodes [OK]

Common Mistakes:

• Removing '/hub' from Hub URL incorrectly
• Thinking port 5555 is invalid
• Assuming command is correct without checking options

5. You want to run tests on Chrome and Firefox browsers simultaneously using Selenium Grid. Which setup steps are necessary to achieve this?

hard

A. Start one Hub, register two Nodes each configured for Chrome and Firefox respectively, then use RemoteWebDriver with desired capabilities

B. Start two Hubs, each with one Node for Chrome and Firefox, then run tests separately

C. Start one Node with both Chrome and Firefox drivers, no Hub needed, run tests locally

D. Start one Hub and one Node with only Chrome driver, then switch drivers in test code

Solution

1. Step 1: Understand Grid architecture for multiple browsers

   One Hub manages multiple Nodes. Each Node can be configured to support different browsers like Chrome and Firefox.

2. Step 2: Setup Nodes and test code

   Register two Nodes with the Hub, one for Chrome and one for Firefox. Use RemoteWebDriver with desired capabilities to select browser at runtime.

3. Final Answer:

   Start one Hub, register two Nodes each configured for Chrome and Firefox respectively, then use RemoteWebDriver with desired capabilities -> Option A

4. Quick Check:

   One Hub + multiple Nodes + desired capabilities = A [OK]

Hint: One Hub, multiple Nodes for browsers, use capabilities [OK]

Common Mistakes:

• Starting multiple Hubs unnecessarily
• Skipping Hub and running Node alone
• Using one Node with single browser only