WebDriver setup (ChromeDriver) in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium WebDriver setup code?

Consider the following Java code snippet for setting up ChromeDriver. What will be the result when this code runs?

Selenium Java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;

public class TestSetup {
    public static void main(String[] args) {
        System.setProperty("webdriver.chrome.driver", "/path/to/chromedriver");
        WebDriver driver = new ChromeDriver();
        driver.get("https://example.com");
        System.out.println(driver.getTitle());
        driver.quit();
    }
}

A Prints the title of https://example.com and closes the browser without errors

B Throws IllegalStateException because the driver path is not set correctly

C Throws NullPointerException when calling getTitle()

D Prints an empty string and leaves the browser open

💡 Hint

Check if the driver path is set and the driver instance is created properly.

The code sets the system property for ChromeDriver, creates a new ChromeDriver instance, navigates to the URL, prints the page title, and then quits the browser cleanly.

❓ assertion

intermediate

Which assertion correctly verifies the page title after ChromeDriver navigation?

You want to check that after navigating to "https://example.com", the page title is exactly "Example Domain". Which assertion is correct in Java with JUnit?

Selenium Java

WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
// Which assertion below is correct?

A assertTrue(driver.getTitle() == "Example Domain");

B assertNull(driver.getTitle());

C assertFalse(driver.getTitle().equals("Example Domain"));

D assertEquals("Example Domain", driver.getTitle());

💡 Hint

Use the proper method to compare strings in Java assertions.

assertEquals compares the expected string with the actual title correctly. Using '==' compares references and is incorrect for strings.

❓ locator

advanced

Which locator strategy is best for finding a button with id 'submitBtn' in Selenium?

You want to locate a button element with the id attribute 'submitBtn'. Which locator is the best practice in Selenium WebDriver Java?

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

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

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

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

💡 Hint

Id is unique and fastest locator.

Using By.id is the fastest and most reliable way to locate an element by its unique id attribute.

🔧 Debug

advanced

Why does this ChromeDriver setup code throw an exception?

Review the code below. It throws an IllegalStateException at runtime. What is the cause?

Selenium Java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;

public class Test {
    public static void main(String[] args) {
        WebDriver driver = new ChromeDriver();
        driver.get("https://example.com");
        driver.quit();
    }
}

A ChromeDriver constructor is deprecated and cannot be used directly

B System property 'webdriver.chrome.driver' is not set with the path to chromedriver executable

C driver.get() is called before driver initialization

D driver.quit() is called before driver.get()

💡 Hint

Check if the driver executable path is configured before creating ChromeDriver.

Without setting the system property 'webdriver.chrome.driver' to the chromedriver executable path, ChromeDriver cannot start and throws IllegalStateException.

❓ framework

expert

Which setup method correctly initializes ChromeDriver for parallel test execution in JUnit 5?

You want to run Selenium tests in parallel using JUnit 5. Which setup method ensures each test gets its own ChromeDriver instance safely?

A

@BeforeEach
void setup() {
    System.setProperty("webdriver.chrome.driver", "/path/to/chromedriver");
    driver = new ChromeDriver();
}

B

@BeforeAll
static void setup() {
    System.setProperty("webdriver.chrome.driver", "/path/to/chromedriver");
    driver = new ChromeDriver();
}

C

@BeforeEach
void setup() {
    driver = new ChromeDriver();
}

D

@BeforeAll
static void setup() {
    driver = new ChromeDriver();
}

💡 Hint

Each test needs its own driver instance to avoid conflicts in parallel runs.

@BeforeEach creates a new ChromeDriver instance before every test method, ensuring thread safety. @BeforeAll runs once for all tests, causing shared driver issues.