RemoteWebDriver usage in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of RemoteWebDriver session creation

What will be the output of the following Java Selenium code snippet when executed successfully?

Selenium Java

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

public class TestRemote {
    public static void main(String[] args) throws Exception {
        DesiredCapabilities caps = new DesiredCapabilities();
        caps.setBrowserName("chrome");
        RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), caps);
        System.out.println(driver.getCapabilities().getBrowserName());
        driver.quit();
    }
}

A firefox

B null

C chrome

D SessionNotCreatedException

💡 Hint

Look at the DesiredCapabilities set before creating the RemoteWebDriver.

The DesiredCapabilities specify the browser as 'chrome'. When the RemoteWebDriver session is created successfully, getCapabilities().getBrowserName() returns 'chrome'.

❓ assertion

intermediate

Correct assertion for page title after navigation

Which assertion correctly verifies that the page title is exactly 'Welcome Page' after navigating using RemoteWebDriver?

Selenium Java

RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), new DesiredCapabilities("chrome", "", null));
driver.get("http://example.com/welcome");
String title = driver.getTitle();

A assertEquals("Welcome Page", title);

B assertTrue(title.contains("Welcome Page"));

C assertNotNull(title);

D assertFalse(title.isEmpty());

💡 Hint

Exact match is required, not just containment or non-null.

assertEquals("Welcome Page", title) checks that the title exactly matches the expected string. Other assertions are less strict or only check partial conditions.

❓ locator

advanced

Best locator strategy for RemoteWebDriver

Which locator strategy is best practice for locating a button with id 'submitBtn' when using RemoteWebDriver?

A driver.findElement(By.id("submitBtn"));

B driver.findElement(By.xpath("//button[@id='submitBtn']"));

C driver.findElement(By.cssSelector("button#submitBtn"));

D driver.findElement(By.className("submitBtn"));

💡 Hint

Id locators are fastest and most reliable if unique.

Using By.id is the fastest and most reliable locator if the id is unique. XPath and CSS selectors work but are slower or more complex. ClassName is incorrect because the id is not a class.

🔧 Debug

advanced

Identify the cause of SessionNotCreatedException

Given the code below, what is the most likely cause of the SessionNotCreatedException?

Selenium Java

DesiredCapabilities caps = new DesiredCapabilities();
caps.setBrowserName("internet explorer");
RemoteWebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), caps);

A RemoteWebDriver constructor requires a WebDriver instance, not DesiredCapabilities.

B The URL for RemoteWebDriver is incorrect.

C DesiredCapabilities does not support setting browserName.

D The Selenium Grid node does not support Internet Explorer browser.

💡 Hint

Check if the browser requested is available on the Selenium Grid node.

SessionNotCreatedException often occurs if the requested browser is not available or not configured on the Selenium Grid node. The URL and DesiredCapabilities usage are correct.

❓ framework

expert

Best practice for RemoteWebDriver test parallelization

Which approach is best for running multiple RemoteWebDriver tests in parallel on a Selenium Grid to maximize resource usage and avoid session conflicts?

A Instantiate RemoteWebDriver once before all tests and reuse it for all tests sequentially.

B Create a new RemoteWebDriver instance in each test method and use thread-safe test runners.

C Use a single RemoteWebDriver instance shared across all test threads.

D Run tests sequentially to avoid any concurrency issues.

💡 Hint

Consider thread safety and independent sessions for parallel tests.

Creating a new RemoteWebDriver instance per test method and using thread-safe test runners allows parallel execution without session conflicts. Sharing one instance across threads causes conflicts. Reusing one instance sequentially is not parallel. Running sequentially wastes parallel capability.