RemoteWebDriver usage in Selenium Java - Build an Automation Script

Verify login functionality using RemoteWebDriver

Preconditions (3)

Step 1: Open browser session using RemoteWebDriver connected to Selenium Grid hub

Step 2: Navigate to https://example.com/login

Step 3: Enter 'testuser' in the username input field with id 'username'

Step 4: Enter 'Test@123' in the password input field with id 'password'

Step 5: Click the login button with id 'loginBtn'

Step 6: Wait until the URL changes to https://example.com/dashboard

Step 7: Verify that the page contains an element with id 'welcomeMessage' displaying text 'Welcome, testuser!'

✅ Expected Result: User is successfully logged in and redirected to dashboard page with welcome message displayed

Automation Requirements - Selenium WebDriver with Java

Assertions Needed:

Verify current URL is https://example.com/dashboard after login

Verify welcome message text is 'Welcome, testuser!'

Best Practices:

Use RemoteWebDriver to connect to Selenium Grid hub

Use explicit waits to wait for URL change and element visibility

Use By.id locators for elements

Close the browser session after test

Handle exceptions gracefully

Automated Solution

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;

import java.net.URL;
import java.time.Duration;

public class RemoteWebDriverLoginTest {
    public static void main(String[] args) {
        WebDriver driver = null;
        try {
            // Set desired capabilities for browser (Chrome example)
            DesiredCapabilities capabilities = new DesiredCapabilities();
            capabilities.setBrowserName("chrome");

            // Connect to Selenium Grid hub
            driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), capabilities);

            // Navigate to login page
            driver.get("https://example.com/login");

            // Enter username
            WebElement usernameInput = driver.findElement(By.id("username"));
            usernameInput.sendKeys("testuser");

            // Enter password
            WebElement passwordInput = driver.findElement(By.id("password"));
            passwordInput.sendKeys("Test@123");

            // Click login button
            WebElement loginButton = driver.findElement(By.id("loginBtn"));
            loginButton.click();

            // Wait for URL to change to dashboard
            WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
            wait.until(ExpectedConditions.urlToBe("https://example.com/dashboard"));

            // Verify welcome message
            WebElement welcomeMessage = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("welcomeMessage")));
            String messageText = welcomeMessage.getText();

            if ("Welcome, testuser!".equals(messageText)) {
                System.out.println("Test Passed: Welcome message is correct.");
            } else {
                System.out.println("Test Failed: Welcome message is incorrect.");
            }

        } catch (Exception e) {
            System.out.println("Test Failed due to exception: " + e.getMessage());
        } finally {
            if (driver != null) {
                driver.quit();
            }
        }
    }
}

This test script uses RemoteWebDriver to connect to a Selenium Grid hub running at http://localhost:4444/wd/hub. We set the desired browser capabilities to Chrome.

The script navigates to the login page, enters the username and password using By.id locators, and clicks the login button.

We use an explicit wait (WebDriverWait) to wait until the URL changes to the dashboard page, ensuring the login was successful.

Then, we wait for the welcome message element to be visible and verify its text matches the expected greeting.

The test prints a pass or fail message based on the assertion and always closes the browser session in the finally block to clean up resources.

Common Mistakes - 3 Pitfalls

Using Thread.sleep() instead of explicit waits

Hardcoding XPath locators instead of using stable IDs

Not closing the RemoteWebDriver session after test

Bonus Challenge

Now add data-driven testing with 3 different username and password combinations to verify login functionality.

Show Hint

Practice

1. What is the main purpose of using RemoteWebDriver in Selenium?

easy

A. To run browser tests on remote machines or servers

B. To run tests only on the local machine

C. To write tests without a browser

D. To speed up test execution on the local browser

Solution

1. Step 1: Understand RemoteWebDriver's role

   RemoteWebDriver allows running tests on browsers that are not on the local machine but on remote servers or machines.

2. Step 2: Compare options

   Options A, C, and D do not describe remote execution. Only To run browser tests on remote machines or servers correctly states the purpose.

3. Final Answer:

   To run browser tests on remote machines or servers -> Option A

4. Quick Check:

   RemoteWebDriver = remote test execution [OK]

Hint: RemoteWebDriver = tests run on remote machines [OK]

Common Mistakes:

• Thinking RemoteWebDriver runs tests locally
• Confusing RemoteWebDriver with headless testing
• Assuming RemoteWebDriver speeds up local tests

2. Which of the following is the correct way to create a RemoteWebDriver instance in Java?

easy

A. RemoteWebDriver driver = new RemoteWebDriver();

B. RemoteWebDriver driver = new RemoteWebDriver("http://localhost:4444/wd/hub", new ChromeOptions());

C. RemoteWebDriver driver = new RemoteWebDriver(new ChromeOptions(), new URL("http://localhost:4444/wd/hub"));

D. RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), new ChromeOptions());

Solution

1. Step 1: Check RemoteWebDriver constructor parameters

   The constructor requires a URL object for the remote server and browser options as parameters.

2. Step 2: Validate each option

   RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), new ChromeOptions()); correctly uses new URL(...) and new ChromeOptions() in the right order. RemoteWebDriver driver = new RemoteWebDriver("http://localhost:4444/wd/hub", new ChromeOptions()); passes a String instead of URL. RemoteWebDriver driver = new RemoteWebDriver(new ChromeOptions(), new URL("http://localhost:4444/wd/hub")); reverses parameters. RemoteWebDriver driver = new RemoteWebDriver(); uses no parameters, which is invalid.

3. Final Answer:

   RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), new ChromeOptions()); -> Option D

4. Quick Check:

   Constructor needs URL then Options [OK]

Hint: Use new URL(...) first, then browser options [OK]

Common Mistakes:

• Passing String instead of URL object
• Swapping parameters order
• Using default constructor without parameters

3. What will happen if you run this code snippet?

URL url = new URL("http://localhost:4444/wd/hub");
ChromeOptions options = new ChromeOptions();
RemoteWebDriver driver = new RemoteWebDriver(url, options);
driver.get("https://example.com");
System.out.println(driver.getTitle());
driver.quit();

medium

A. It throws a runtime error because getTitle() is not supported

B. It opens Chrome on the remote server, navigates to example.com, prints the page title, then closes the browser

C. It opens Chrome locally and prints the title of the local browser

D. It throws a compile-time error due to wrong constructor usage

Solution

1. Step 1: Analyze RemoteWebDriver usage

   The code creates a RemoteWebDriver with a valid URL and ChromeOptions, then navigates to a website and prints the title.

2. Step 2: Understand execution flow

   The driver runs on the remote server at the URL, opens Chrome, loads the page, prints the title, and quits cleanly. No errors expected.

3. Final Answer:

   It opens Chrome on the remote server, navigates to example.com, prints the page title, then closes the browser -> Option B

4. Quick Check:

   RemoteWebDriver runs remote browser and prints title [OK]

Hint: RemoteWebDriver runs remote browser, prints title, then quits [OK]

Common Mistakes:

• Assuming it runs locally
• Expecting compile or runtime errors
• Thinking getTitle() is unsupported

4. Identify the error in this code snippet:

RemoteWebDriver driver = new RemoteWebDriver("http://localhost:4444/wd/hub", new FirefoxOptions());
driver.get("https://example.com");

medium

A. The URL parameter should be a java.net.URL object, not a String

B. FirefoxOptions cannot be used with RemoteWebDriver

C. driver.get() method is not valid for RemoteWebDriver

D. RemoteWebDriver cannot be instantiated directly

Solution

1. Step 1: Check constructor parameter types

   RemoteWebDriver constructor expects a URL object, not a String. Passing a String causes a compile-time error.

2. Step 2: Verify other options

   FirefoxOptions is valid for RemoteWebDriver. driver.get() is valid. RemoteWebDriver can be instantiated directly.

3. Final Answer:

   The URL parameter should be a java.net.URL object, not a String -> Option A

4. Quick Check:

   Constructor needs URL object, not String [OK]

Hint: Use new URL(...) for remote URL, not plain String [OK]

Common Mistakes:

• Passing String instead of URL object
• Thinking FirefoxOptions is invalid
• Believing driver.get() is unsupported

5. You want to run tests on Chrome and Firefox browsers on a Selenium Grid server at http://grid.example.com:4444/wd/hub. Which code snippet correctly creates two RemoteWebDriver instances for this purpose?

hard

A. RemoteWebDriver chromeDriver = new RemoteWebDriver(new ChromeOptions(), new URL("http://grid.example.com:4444/wd/hub"));
RemoteWebDriver firefoxDriver = new RemoteWebDriver(new FirefoxOptions(), new URL("http://grid.example.com:4444/wd/hub"));

B. RemoteWebDriver chromeDriver = new RemoteWebDriver("http://grid.example.com:4444/wd/hub", new ChromeOptions());
RemoteWebDriver firefoxDriver = new RemoteWebDriver("http://grid.example.com:4444/wd/hub", new FirefoxOptions());

C. RemoteWebDriver chromeDriver = new RemoteWebDriver(new URL("http://grid.example.com:4444/wd/hub"), new ChromeOptions());
RemoteWebDriver firefoxDriver = new RemoteWebDriver(new URL("http://grid.example.com:4444/wd/hub"), new FirefoxOptions());

D. RemoteWebDriver chromeDriver = new RemoteWebDriver();
RemoteWebDriver firefoxDriver = new RemoteWebDriver();

Solution

1. Step 1: Confirm correct constructor usage for both drivers

   Each RemoteWebDriver must be created with a java.net.URL object and the corresponding browser options (ChromeOptions or FirefoxOptions).

2. Step 2: Evaluate each option

   RemoteWebDriver chromeDriver = new RemoteWebDriver(new URL("http://grid.example.com:4444/wd/hub"), new ChromeOptions()); RemoteWebDriver firefoxDriver = new RemoteWebDriver(new URL("http://grid.example.com:4444/wd/hub"), new FirefoxOptions()); correctly uses new URL(...) and proper options for both drivers. RemoteWebDriver chromeDriver = new RemoteWebDriver("http://grid.example.com:4444/wd/hub", new ChromeOptions()); RemoteWebDriver firefoxDriver = new RemoteWebDriver("http://grid.example.com:4444/wd/hub", new FirefoxOptions()); passes String instead of URL. RemoteWebDriver chromeDriver = new RemoteWebDriver(new ChromeOptions(), new URL("http://grid.example.com:4444/wd/hub")); RemoteWebDriver firefoxDriver = new RemoteWebDriver(new FirefoxOptions(), new URL("http://grid.example.com:4444/wd/hub")); swaps parameters. RemoteWebDriver chromeDriver = new RemoteWebDriver(); RemoteWebDriver firefoxDriver = new RemoteWebDriver(); uses no parameters, which is invalid.

3. Final Answer:

   RemoteWebDriver chromeDriver = new RemoteWebDriver(new URL("http://grid.example.com:4444/wd/hub"), new ChromeOptions()); RemoteWebDriver firefoxDriver = new RemoteWebDriver(new URL("http://grid.example.com:4444/wd/hub"), new FirefoxOptions()); -> Option C

4. Quick Check:

   Use URL object first, then browser options for each driver [OK]

Hint: Create each driver with new URL(...) and correct Options [OK]

Common Mistakes:

• Passing String instead of URL
• Swapping constructor parameters
• Trying to instantiate without parameters