Finding Elements in Selenium – Recap & Best Practices

A summary of core concepts, best practices, and common pitfalls when finding elements in Selenium.

Core Concepts Recap

Finding elements is more than just writing a locator. It involves understanding the DOM structure, managing scope, and handling dynamic content.

findElement vs findElements

findElement: Returns the first match. Throws NoSuchElementException if not found.
findElements: Returns a List of all matches. Returns an empty list (size 0) if none are found (no exception!).

Advanced Techniques

Scoping: Call element.findElement(...) to search inside a specific parent, ignoring the rest of the page.
Shadow DOM: Use getShadowRoot() to pierce through encapsulation boundaries.
Active Element: Use driver.switchTo().activeElement() to find where the focus is.

The "Empty List" Trick

To check if an element does NOT exist (e.g., verifying a popup is closed), use findElements(...).isEmpty(). Never use findElement for negative assertions because it throws an exception.

Comprehensive Code Example

This script demonstrates finding a list of products, scoping the search to each product card, and handling the Shadow DOM.

FindingElementsMastery.java

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
// 1. Find all product cards (returns a List)
List<WebElement> products = driver.findElements(By.className("product-card"));

System.out.println("Found " + products.size() + " products.");

for (WebElement product : products) {
    // 2. Scoped Search: Find title INSIDE this specific card
    // Note: The locator starts from 'product', not 'driver'
    WebElement title = product.findElement(By.tagName("h3"));
    System.out.println("Product: " + title.getText());
    
    // 3. Shadow DOM interaction (if the 'Buy' button is in a shadow root)
    WebElement shadowHost = product.findElement(By.cssSelector("custom-buy-button"));
    SearchContext shadowRoot = shadowHost.getShadowRoot();
    
    // Find the actual button inside the shadow root
    WebElement buyBtn = shadowRoot.findElement(By.cssSelector("button.primary"));
    buyBtn.click();
}

Code Breakdown

driver.findElements(...): Retrieves all elements matching the class product-card. If none match, the loop simply doesn't run.
product.findElement(...): Crucial: We call findElement on the product variable. This limits the search to children of that specific card.
getShadowRoot(): Accesses the shadow DOM tree of the custom element, allowing us to find elements that are otherwise invisible to standard global searches.

Pro Tip

Avoid Stale Elements

If the DOM updates (e.g., after a filter is applied), your old WebElement references become "stale". Always re-find elements after a page update.

Use Optimized Locators

Instead of driver.findElement(By.id("a")).findElement(By.className("b")), prefer a single CSS selector: driver.findElement(By.cssSelector("#a .b")). It's faster.

Wait for Elements

findElement fails immediately if the element isn't there. In real tests, combine this with Explicit Waits (covered in future units) to handle loading times.