WebDriver APIs and Commands

Both findElement and findElements locate web elements on a page using a By locator strategy, but they differ in return type and error behavior.

findElement(By locator)

• Returns the first matching WebElement on the page.
• If no element is found, throws NoSuchElementException immediately.
• Use when you expect exactly one element and want the test to fail fast if it is missing.

WebElement button = driver.findElement(By.id("submit"));
button.click();

findElements(By locator)

• Returns a List containing all matching elements.
• If no elements are found, returns an empty list — does not throw an exception.
• Use when you need to work with multiple elements (e.g., all rows in a table) or when you want to check if an element exists without risking an exception.

List items = driver.findElements(By.className("menu-item"));
System.out.println("Found: " + items.size());

for (WebElement item : items) {
    System.out.println(item.getText());
}

Checking element existence without exception:

// findElements returns empty list (no exception) if not found
boolean isPresent = !driver.findElements(By.id("optional-banner")).isEmpty();

Key differences:

> Common interview gotcha: findElement does not guarantee it finds the "right" element when there are multiple matches — it returns whichever the browser encounters first in DOM order. Use more specific locators (ID, unique CSS selector) to be precise.

driver.get(url) is the primary method for navigating to a URL in Selenium WebDriver.

What it does:

• Loads the specified URL in the current browser window.
• Waits for the page load to complete before returning control to the test — specifically, it waits until the browser fires the document.readyState === "complete" event (equivalent to the onload event).
• Replaces the current page (does not open a new tab or window).

driver.get("https://www.example.com");
// Control returns here only after the page has fully loaded
WebElement heading = driver.findElement(By.tagName("h1"));

get() vs navigate().to():

Both navigate to a URL, but there is a subtle difference:

In practice, both behave identically for navigation. navigate().to() is preferred when you also need back()/forward() in the same test flow, since they are accessed from the same object.

Common follow-up questions:

• What if the page never fully loads? — The pageLoadTimeout setting determines how long WebDriver waits before throwing a TimeoutException. Default is 300 seconds. Set with driver.manage().timeouts().pageLoadTimeout(Duration.ofSeconds(30)).
• Does get() work for file:// URLs? — Yes, local files can be loaded using file:///path/to/file.html.
• Is get() sufficient for AJAX-heavy SPAs? — Not always. The onload event fires when the initial HTML loads, but dynamic content loaded via AJAX may not be ready. Use explicit waits after get() for SPA content.

close() and quit() both end browser interactions, but they behave differently and are used in different scenarios.

driver.close()

• Closes the currently focused browser window or tab.
• If there are multiple windows or tabs open in the session, only the current one is closed. The WebDriver session remains active.
• Does not end the WebDriver session — the driver object is still valid and can be used to switch to and interact with remaining windows.

// Example: close a popup window and switch back to the main window
String mainHandle = driver.getWindowHandle();
// ... open popup ...
driver.close();  // closes popup
driver.switchTo().window(mainHandle);  // back to main window

driver.quit()

• Closes all browser windows and tabs opened by the WebDriver session.
• Ends the WebDriver session and releases all associated resources (driver process, browser process).
• Should always be called in teardown to prevent browser/driver processes from leaking.

@AfterMethod  // TestNG teardown
public void tearDown() {
    if (driver != null) {
        driver.quit();
    }
}

Key differences:

Common interview gotcha: If you call close() when only one window is open, it closes the browser but the WebDriver session may not be fully cleaned up on some browsers. Always use quit() in @After / tearDown methods. Failing to call quit() causes browser and driver processes to accumulate, consuming memory and potentially causing port conflicts.

The navigate() method returns a WebDriver.Navigation object that provides browser history and URL navigation methods. It is the preferred approach when you need to navigate back, forward, or refresh within a test.

Available methods:

driver.navigate().to("https://example.com");  // Navigate to URL
driver.navigate().back();                      // Go back in history
driver.navigate().forward();                   // Go forward in history
driver.navigate().refresh();                   // Refresh current page

navigate().to() vs driver.get():

Both load a URL. The practical difference:

• driver.get(url) is a shorthand for simple page loads.
• driver.navigate().to(url) is part of the Navigation API, so you can chain with .back()/.forward() without breaking context.
• Both wait for the page load event (document.readyState === "complete") before returning.

navigate().back() and navigate().forward():

These simulate clicking the browser's Back and Forward buttons. They work with the browser's session history:

driver.get("https://page1.com");
driver.get("https://page2.com");
driver.navigate().back();    // returns to page1.com
driver.navigate().forward(); // returns to page2.com

navigate().refresh():

Reloads the current page. Equivalent to pressing F5 in the browser. Useful for testing page state after an action or verifying that data persists after reload.

driver.navigate().refresh();

Practical use in tests:

// Test that a form submission is not re-submitted on refresh (PRG pattern)
driver.findElement(By.id("submit")).click();
String urlAfterSubmit = driver.getCurrentUrl();
driver.navigate().refresh();
// Verify no duplicate submission warning

Common follow-up: After navigate().back() or .refresh(), previously found WebElement references become stale. Re-locate elements after navigation to avoid StaleElementReferenceException.

Selenium WebDriver provides a rich set of APIs for locating and interacting with web elements. The general pattern is: locate → interact → verify.

Locating elements:

WebElement el = driver.findElement(By.id("username"));
WebElement el = driver.findElement(By.name("email"));
WebElement el = driver.findElement(By.cssSelector(".btn-primary"));
WebElement el = driver.findElement(By.xpath("//button[@type='submit']"));
WebElement el = driver.findElement(By.linkText("Sign In"));

Basic interactions on a WebElement:

el.click();                        // Click the element
el.sendKeys("[email protected]"); // Type text (clears nothing — appends)
el.clear();                        // Clear text field content
el.submit();                       // Submit a form (on form elements)
String text   = el.getText();      // Visible text content
String value  = el.getAttribute("value");   // HTML attribute value
String cls    = el.getAttribute("class");
boolean shown = el.isDisplayed();  // Visible on page
boolean enabled = el.isEnabled();  // Not disabled
boolean checked = el.isSelected(); // Checked (checkbox/radio)

Dropdown (select elements):

Select dropdown = new Select(driver.findElement(By.id("country")));
dropdown.selectByVisibleText("United States");
dropdown.selectByValue("us");
dropdown.selectByIndex(2);
List options = dropdown.getOptions();

Complex interactions with Actions class:

Actions actions = new Actions(driver);

// Hover over an element
actions.moveToElement(menuItem).perform();

// Drag and drop
actions.dragAndDrop(source, target).perform();

// Right-click (context menu)
actions.contextClick(element).perform();

// Double-click
actions.doubleClick(element).perform();

// Key chord (e.g., Ctrl+A)
actions.keyDown(Keys.CONTROL).sendKeys("a").keyUp(Keys.CONTROL).perform();

Selenium 4 relative locators:

WebElement emailField = driver.findElement(By.id("email"));
WebElement passwordField = driver.findElement(
    RelativeLocator.with(By.tagName("input")).below(emailField)
);

For elements that don't respond to standard Selenium interactions (e.g., hidden elements, canvas), use JavascriptExecutor as a fallback:

JavascriptExecutor js = (JavascriptExecutor) driver;
js.executeScript("arguments[0].click();", element);