Locator Strategy Priority

Every time you need to find an element, follow this checklist from top to bottom. Stop at the first one that works.

1. By.id("elementId") — Best option. IDs are unique by HTML spec. Fast.
2. By.cssSelector("[data-testid='loginBtn']") — Gold standard. Designed specifically for testing.
3. By.name("elementName") — Good for form fields. Stable.
4. By.cssSelector("css") — Your go-to for everything else. Fast and flexible.
5. By.xpath("//xpath") — Most powerful but slowest. Use for text matching or parent traversal.
6. By.className("class") — Fragile if classes are shared across elements.
7. By.linkText("Full Text") / By.partialLinkText("Partial") — Only for <a> tags.

The data-testid Strategy

Modern apps add data-testid attributes specifically for automation. They're the gold standard because: (1) they exist only for testing — devs don't touch them during UI changes, (2) they're never auto-generated or dynamic, (3) they survive CSS refactors. Both the Banking and Shopping portals use data-testid extensively.

// data-testid — access via CSS selector
WebElement loginBtn = driver.findElement(
    By.cssSelector("[data-testid='loginBtn']"));

WebElement searchBox = driver.findElement(
    By.cssSelector("[data-testid='search-box']"));

WebElement productName = driver.findElement(
    By.cssSelector("[data-testid='product-name-1']"));

// Same thing with XPath (slightly slower)
WebElement loginBtnXPath = driver.findElement(
    By.xpath("//*[@data-testid='loginBtn']"));