How to Run Tests on Remote Browser in Selenium

To run tests on a remote browser in Selenium, use the RemoteWebDriver class with the URL of the Selenium Grid or remote server and desired browser capabilities. This lets you execute tests on browsers hosted on other machines or cloud services.

Syntax

The basic syntax to run tests on a remote browser involves creating a RemoteWebDriver instance by providing the remote server URL and browser capabilities.

• RemoteWebDriver(URL remoteAddress, Capabilities capabilities): Connects to the remote Selenium server.
• URL remoteAddress: The address of the Selenium Grid or remote WebDriver server.
• Capabilities capabilities: Defines the browser type and options (e.g., Chrome, Firefox).

java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.openqa.selenium.remote.DesiredCapabilities;
import java.net.URL;

URL remoteUrl = new URL("http://remote-server:4444/wd/hub");
DesiredCapabilities capabilities = DesiredCapabilities.chrome();
WebDriver driver = new RemoteWebDriver(remoteUrl, capabilities);

Example

This example shows how to run a simple test on a remote Chrome browser using Selenium Grid. It opens Google, checks the page title, and closes the browser.

java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.openqa.selenium.remote.DesiredCapabilities;
import java.net.URL;

public class RemoteBrowserTest {
    public static void main(String[] args) throws Exception {
        URL remoteUrl = new URL("http://localhost:4444/wd/hub");
        DesiredCapabilities capabilities = DesiredCapabilities.chrome();
        WebDriver driver = new RemoteWebDriver(remoteUrl, capabilities);

        driver.get("https://www.google.com");
        String title = driver.getTitle();
        System.out.println("Page title is: " + title);

        if (!title.toLowerCase().contains("google")) {
            throw new AssertionError("Title does not contain 'Google'");
        }

        driver.quit();
    }
}

Output

Page title is: Google

Common Pitfalls

Common mistakes when running tests on remote browsers include:

• Using incorrect or unreachable remote server URL.
• Not matching browser capabilities with the remote server's available browsers.
• Forgetting to start the Selenium Grid or remote WebDriver server.
• Ignoring network/firewall issues blocking communication.

Always verify the remote server is running and accessible before running tests.

java

/* Wrong: Using local WebDriver instead of RemoteWebDriver for remote tests */
// WebDriver driver = new ChromeDriver(); // This runs locally, not remotely

/* Right: Use RemoteWebDriver with correct URL and capabilities */
URL remoteUrl = new URL("http://remote-server:4444/wd/hub");
DesiredCapabilities capabilities = DesiredCapabilities.firefox();
WebDriver driver = new RemoteWebDriver(remoteUrl, capabilities);

Quick Reference

Tips for running Selenium tests on remote browsers:

• Always use RemoteWebDriver with the remote server URL.
• Set DesiredCapabilities to specify browser type and version.
• Ensure the remote Selenium Grid or server is running and accessible.
• Check network/firewall settings to allow communication.
• Close the driver with driver.quit() to free resources.

Key Takeaways

Use RemoteWebDriver with the remote server URL and browser capabilities to run tests remotely.

Ensure the Selenium Grid or remote server is running and reachable before starting tests.

Match DesiredCapabilities with the browsers available on the remote server.

Always close the remote driver with driver.quit() to release resources.

Check network and firewall settings to avoid connection issues.